What is Neustar?

Neustar is a marketing and identity resolution platform that enables brands to connect and activate customer data across channels. It offers solutions for audience segmentation, personalization, and attribution by linking offline and online identifiers. Neustar's identity graph powers data-driven marketing and analytics strategies by providing persistent IDs and enriching them with demographic and behavioral attributes. This helps advertisers improve targeting, measurement, and customer experience.

Product Type: Identity Resolution

Integration Type: Starter Kit & ID Sync

Capabilities

• Captures fabrickId from a REST API response and stores it in first-party cookies.
• Syncs additional identifiers (apiFields) such as tuid, a, and b if included in the response.
• Sends hashed email and/or 1pd (partner/advertiser’s first-party ID) as inputs during the identify call to enhance match accuracy.
• Supports reSync functionality, updating identifiers when a user logs in or identity changes.
• Adds identifiers to server-side event payloads for attribution and user identity resolution.

Considerations

• The fabrickId and any optional apiFields returned vary depending on the API key configuration; contact Neustar to determine which fields are available.
• Setting the cookie TTL to 0 will cause the sync to fire on every load.
• This sync re-fires when an analytics.identify call is made with new identity data (e.g., email or pd).

Sync Details

• IDs:

  • fabrickId – A persistent identifier returned by Neustar used to unify user identity across platforms.
  • tuid, a, b – Optional identity fields returned when requested via apiFields and supported by the configured API key.

• Description:

  • The sync captures fabrickId and optional fields like tuid, a, and b from a GET request to Neustar's endpoint.
  • Each value is stored in first-party storage for a user-defined duration (default is 365 days).
  • Values are refreshed when new identity data (e.g., email or pd) is passed via identify calls.
  • The identifiers are added to server-side event payloads for audience resolution and targeting.

• Response Example:

  JSON

  {
    "fabrickId": "E1:dZrFmv1B4ikw69tIsEWklRty123eknoGadkaIXeGBaytz1e-MZIHD0NT3gl_WPuIGxRlw6WsG3mWDUt-Gglu7AsbcFNA5kPGEUuJHmR5ou85U5J9Q-vZxHsJJLWkK54eW",
    "a": "000",
    "b": [""]
  }
  
  

• Server-side Event Payload:
  Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

  JSON

  {
    "neustar": {
      "apiFields": "apiFieldsValues",
      "fabrickId": "String"
    }
  }
  
  

• Cookie Name:

  • Cookie: _meta_neustar_fabrickId, _meta_neustar_fabrickId_failure
  • IndexedDB: [your storage prefix]_neustar_fabrickId, [your storage prefix]_neustar_fabrickId_failure
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

To configure the Neustar sync, you’ll need the following credentials:

• API Key: Provided by Neustar. Contact Neustar support if you don’t have access.

2. Add a Neustar Sync in MetaRouter

To gather the fabrickId, and optionally tuid, a, b, you must add a Neustar sync.

1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
2. In the Identity Syncs section, select the Neustar sync.
3. Fill out the following fields:
   1. API Key – Your Neustar-issued API key. (e.g., "5451521")
   2. Cookie Lifetime (in days) – The number of days to persist the cookie (e.g., 30). Set to 0 to re-fire every load.
   3. API Timeout (in milliseconds) – Time allowed for the sync to respond (e.g., 5000).
   4. API Fields – Optional array of additional identifiers to capture (e.g., ["tuid", "a", "b"]).
   5. Fire On ReSync – Set to true to enable syncing on identify calls.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.