Skip to content

Output values

Preview

This feature is not subject to our service terms. Pre-GA features are available as is and might have limited support.

The Modigie Job Engine provides different kinds of enrichment depending on the job type and the existing attributes.

Kinds of enrichment performed by Modigie

Kinds of enrichment performed by Modigie

The Modigie Job Engine enriches either existing attributes of leads/contacts, or the leads/contacts themselves, or any combination of the two:

  • The engine can enrich an existing attribute of a lead/contact that you provide (e.g., an existing phone number) and return the attribute with syntax (and intelligence) information.
  • The engine can also use existing attributes to enrich the lead/contact by appending new attributes—e.g., adding a missing LinkedIn user URL or mobile phone number—and return them to you. Modigie typically provides syntax and intelligence data along with an appended attribute. For some attribute types and job types, Modigie provides a combination of these features.

The Modigie Job Engine's data model supports two layers for most attributes and performs different work on them:

  • Syntax validation: Checks that an attribute is technically correct. This typically encompasses whether an attribute, like an email address or phone number, complies with relevant technical standards (e.g. ISO, RFC, and ITU). Validation usually also provides the attribute in different formats useful for different purposes. An attribute's validation is usually self-contained and unlikely to change over time. For example, whether a phone number is possible or impossible in a given country isn't influenced by the person the phone number belongs to.

  • Intelligence verification: Checks that an attribute is suitable in a certain context. Usually, before verification can happen, the syntax must also be validated. Then the valid attributes are contextualized and evaluated. An attribute's intelligence data usually only makes sense in a given context (e.g., the rating score of a phone number belonging to one person cannot be applied to the same phone number belonging to a different person) and this information is likely to change over time (e.g., a person changes the employer a few months later).

Info

Feature availability depends on factors such as the integration endpoint, job type, the individual request, and your active subscription or configuration.

Email address

See Rich email address for more details.

Syntax and validation of email addresses

  • Syntax: The address complies with RFC 882 (email standards).
  • Deliverability: A DNS record of type MX (mail exchange) exists for the email domain. This is the minimum requirement for deliverability. However, delivery might still fail due to issues with the local part of the address, sender reputation, spam score, or missing DMARC/SPF/DKIM records.
  • Formats: Modigie provides the email address in multiple formats:
    • User format (as provided)
    • RFC 882 format (meant for delivery; only the domain part of local@domain is in lowercase)
    • Normalized format (similar to RFC 882, but with both local and domain parts in lowercase to improve duplicate detection)

Warning

If an email address is syntactically invalid, other features are unavailable.

Intelligence and verification of email addresses

  • Relations: Indicates the presumed relationship of the email address to the person (business, personal, or other).

Warning

Intelligence is unavailable for invalid email addresses.

LinkedIn user URL

See Rich URL for more details.

Syntax and validation of LinkedIn user URLs

  • Syntax: The URL complies with RFC 3986.
  • Remote: The URL resolves to a remote host with a public IP address, not a local host like localhost or 192.168.1.1.
  • Formats: Modigie provides the URL in multiple formats:
    • User format (as provided)
    • RFC 3986 format (with components like schema, authority, and path)
    • Normalized format (with normalized schema, domain, and path)

Intelligence and verification of LinkedIn user URLs

  • Relations: Indicates whether the URL is a valid LinkedIn user URL.

Phone number

See Rich phone number for more details.

Syntax and validation of phone numbers

  • Possible: The phone number is possible (e.g., it has the correct number of digits), but not necessarily valid. For example, +120012301 is not possible because it has too few digits for numbers in the North American Numbering Plan (NANP).
  • Valid: The phone number is both possible (e.g., it has the correct number of digits) and valid (e.g., it is in an assigned exchange). For example, +120012301 is possible but not valid because the numbering plan area 200 does not exist in the North American Numbering Plan (NANP). +19722319930, on the other hand, is both possible and valid because 972 is an assigned NANP exchange.
  • Formats: Modigie provides the phone number in multiple formats:
    • User format (as provided)
    • E.164 (used in phone networks and by dialers)
    • International format: Conventional format with country code, following the conventions used in the country the number belongs to. For example, +1 809-123-4560 (United States) or +49 8374 93081 (Germany).
    • National format: Conventional format without country code, following the conventions used in the country the number belongs to. For example, (809) 123-4560 (United States) or (08374) 93081 (Germany).
  • ITU country code: The international prefix of the number's country (e.g., 1 for the U.S. or any NANP member, 49 for Germany).
  • Country: The country of the phone number, represented by its ISO 3166-1 alpha-2, alpha-3, and numeric-3 codes, as well as its common and official names.

Warning

If a phone number is invalid, other features are unavailable.

Intelligence and verification of phone numbers

  • Phone type: The type of phone subscription (mobile, voip, landline, or unknown).
  • Rating: A score between 0 (low) and 100 (high) indicating the quality of the phone number, along with component scores for activity and/or name match.
  • Relations: The presumed relationship of the phone number to the subscriber (business, personal, or other).
  • Compliance: Whether the number is on the US Do Not Call registry or associated with TCPA litigation.
  • SMS email addresses: Email addresses that can be used to send SMS messages to the phone number.

Warning

Intelligence is unavailable for invalid phone numbers. Some features are limited to mobile or VoIP numbers. The ITU country and compliance status might restrict available intelligence.

Employment

See Current employment for more details.

Intelligence and verification of employment

  • Current employer: The company where the person is currently employed. This might be unavailable for various reasons, such as retirement, unemployment, or privacy concerns.
  • Job title: The person's role at their current employer.
  • Employment end date: The month and year the person left a previous employer, if applicable. This is provided in multiple formats.

Geographic signals

Depending on the job type, Modigie may also provide a list of all current locations and countries discovered for the person in this job.

See Locations and Countries for more details.

Tags

The list of custom job tags that your application can attach to each job request for analytical or operational purposes.

See Job tags for more details.