Neustar: Neustar Fabrick API

Identity Resolution

Description:

Company Overview:

Neustar is an information services and technology company and a leader in identity resolution providing the data and technology that enable trusted connections between companies and people at the moments that matter most.

We use best-in-class data science to create a unified identity graph – across offline and online datapoints and identity fragments – to resolve all types of consumer data for the best, most complete view of your customer. Each consumer and household in our graph – real people in the real world – has a persistent Neustar ID for use in identification, as well as activation.

Neustar Fabrick API:

Using Neustar’s Fabrick API, customers can leverage our identity graph to connect unauthenticated visitors on their owned & operated digital properties to their CRM records.

Customers can pass a variety of non-cookie digital signals – such as email, phone & IP address – to Neustar in the API call. Neustar can match the users identifiers in the API call in real-time to our Identity Graph, and return the corresponding Individual and/or Household level persistent IDs in the API response. Customers can use these persistent Indvidual/Household IDs for a variety of downstream use cases, including user-level analytics and reach/frequency management.

How the Fabrick API works:

API Request
In order to call the Fabrick API endpoint, two key things are needed:

(1) a valid API key and,

(2) at least one supported identifier (ex. hashed email address) must be passed.

Requesting the API Key:

Please reach out to [email protected] to request an API key. The API Key is unique for each advertiser/publisher.

Supported Identifiers:
• e = Hashed email address (SHA-1, SHA-256 or MD5)
• p = E.164 standard hashed phone number (SHA-1, SHA-256 or MD5). All four components of a phone number are required as specified by the E.164 standard (i.e. plus sign, country code, area code and phone number). E.164 standard removes any leading ‘0’s from the number and aside from the ‘+’, all following characters must be numeric. Phone number must exclude spaces and should be hashed (MD5, SHA-1, SHA-256).
• i4 = IPv4 Address (raw)
• i6 = IPv6 Address (raw)
• m = Mobile Advertising ID (IDFA/AAID; raw or SHA-1, SHA-256 or MD5 hashed)
• ia = Identifier for Advertising (IFA; raw or SHA-1, SHA-256 or MD5 hashed; see details below)
• iv = Identifier for Vendors (IFV; raw or SHA-1, SHA-256 or MD5 hashed)
• 1pd = partner or advertiser’s 1st party user ID (e.g. a Customer ID/CUSTID)

Support for Identifier for Advertising (IFA):

We offer support for passing IFA and related parameters per IAB’s Guidelines for IFA on CTV/OTT platforms. The IFA can be passed via the “ia” parameter, per details above. If “ia” is being populated, the following two additional parameters are required to be passed:

• ifa_type = [string] to denote the source of the IFA.
• lmt = [boolean] to indicate whether the user can be tracked or not. Possible values are “0” or ‘1”. A value of “1” indicates that a user has requested that ad tracking and measurement be disabled. If a value of “1” is being passed, the real IFA must not be sent via the “ia” parameter – a “synthetic” or “session” IFA can be sent.

Please refer to IAB’s Guidelines for IFA on CTV/OTT platforms for additional details.

Request & Response Formats:

Sample Request Format
https://fid.agkn.com/f?apiKey={apiKey}&e={hashedEmail}&i4={IPv4Address}

Sample Request
https://fid.agkn.com/f?apiKey=222222222&e= 31c5543c1734d25c7206f5fd591525d0295bec6fe84ff82f946a34fe970a1e66&i4=1A021AB6494D9CF855C0593A6A04B4B84C93701F

Frequency
Call the API once every seven days per user.

Sample Response
After calling the Fabrick API and passing your API key and identifiers, the API returns a unique Fabrick ID:
{“fabrickId”: “E1:t7d-m2abHP3fKX4VbdthXDUnDVMU_Yw91bv2XKtHgS1_2E7g5pSOnYnIxKm9LPswYE9sgrtm9_EQAoMROtE_1Ed0RMmzF-OQrlVdcOP1-s0”}
The Fabrick ID will have a variable length between 44-255 characters.

Getting Neustar Identity from Fabrick API

Neustar uses both deterministic and probabilistic data signals to construct & maintain an identity graph that resolves these data signals to both Individuals and Households. There are four levels of Neustar identity:

• Level 0 (L0) – Neustar Individual ID based on both deterministic and probabilistic identifiers
• Level 1 (L1) – Neustar Household ID based on both deterministic and probabilistic identifiers
• Level 2 (L2) – Neustar Individual ID based on deterministic identifiers (Note: this is a subset of Level 0 identity)
• Level 3 (L3) – Neustar Household ID based on deterministic identifiers (Note: this is a subset of Level 1 identity)

When you pass any of our Supported Identifiers in the Fabrick API call, we can look up the corresponding Neustar ID(s) from our identity graph and return that ID(s) in the API response in real time. The Fabrick API response can be configured to return any or all of the four aforementioned IDs.

Sample Response
Following is the API response if the Fabrick API is configured to return all four levels of Neustar Identity:

{“fabrickId”: “E1:uIfyqirJozv6%2BOio3h5F0DfH5iaHVDqrVfcRuCpT6or8JDVf%2Ft%2F1YlPkn0QrN%2F1bqEACKs4%2F%2FY4%3D”,”L0″:”02960c4fa664507a94c9f33daa8ed2128df51ee5″, “L1″:”dcd568e424293acf6b2c0c9e1b94853c4191fb94”, “L2″:”02960c4fa664507a94c9f33daa8ed2128df51ee5”, “L3″:”dcd568e424293acf6b2c0c9e1b94853c4191fb94”}

The API response will include all parameters (L0, L1, L2 and/or L3) that are configured for the specific API Key. For example, if your API key is configured to return all four levels of identity, then the API response will always include all four parameters (L0, L1, L2, L3). If the identifiers you pass in the API call cannot be resolved to one or more of the parameters, then the corresponding parameters will have an empty string. Following is a sample response where the identifiers passed in the API call cannot be resolved to any of the four levels of Neustar identity:

{“fabrickId”: “E1:uIfyqirJozv6%2BOio3h5F0DfH5iaHVDqrVfcRuCpT6or8JDVf%2Ft%2F1YlPkn0QrN%2F1bqEACKs4%2F%2FY4%3D”, “L0″:””, “L1″:””, “L2″:””, “L3″:””}

Next Steps:

1) Please reach out to Neustar via the ‘Request’ button on this listing
2) A Neustar representative will reach out to discuss how we can configure this solution to suit your business needs and discuss the associated terms & conditions
3) Thereafter, we will provide you with an API key that you can use to call the Fabrick API
4) Please refer to the listing for sample SQL queries (Note: Listing to be Updated Shortly with this Info)

About the Provider:

Neustar is an information services and technology company and a leader in identity resolution providing the data and technology that enable trusted connections between companies and people at the moments that matter most. Neustar offers industry-leading solutions in marketing, risk, communications, and security that responsibly connect data on people, devices and locations, continuously corroborated through billions of transactions. Neustar serves more than 8,000 clients worldwide, including 60 of the Fortune 100. Learn how your company can benefit from the power of trusted connections here: home.neustar.

Visit the provider’s website for more information

Get access to the Neustar: Neustar Fabrick API Listing in Snowflake

Sign up for a Snowflake free Trial

Already a Snowflake customer?
Access this listing directly from your Snowflake account.

Login