LIVE ID Graph

The LIVE ID Graph enables the association of additional identifiers to a person’s record in ZMP. These Identifiers can be used to update and target users, and to merge disparate records into a single cohesive profile.

If you’d like to enable the LIVE ID Graph for your account, please reach out to your Zeta Account Representative for details and pricing.

The LIVE ID Graph enables additional identifiers to be associated with a profile, these will be treated as unique identifiers much the same as ZMP’s own user_id. You also have the option of passing an identifier and having ZMP generate a user_id for you.

Configuring Identifiers

The identifiers you wish to add must be pre-configured by Zeta to be ingested, once configured you can add these via several of ZMP’s REST APIs or by loading a JSONL file, or by loading them via a CSV file with a prefix of unique_client_id_.

APIs

We currently support identifiers to be added when creating or updating a profile using our Identify a User API, or associating events to a profile with our Track an Event API, additionally identifiers can be deleted using the Delete Identifiers API.

Identify a User API Usage

1. You can associate an identifier or identifier to a record using the unique_client_ids object inside the existing subscriber object.

2. If a record already has identifiers associated with its profile, you may identify that person using only the unique_client_ids object.

3. If you have opted for the generation of user_id, you can pass a previously unknown record into ZMP with only a non-user_id identifier and ZMP will generate a user_id for you.

4. If a call is made using both a user_id and unique_client_ids where those identifiers resolve to different profiles in ZMP, we will merge them using the user_id identified profile as the core and merging the unique_client_ids profile as the duplicate.

Sample API body for a user_id 100001 and where person_id: A1234

CODE

{
	"subscriber":{
		"user_id":"100001",
		"unique_client_ids":[{
			"name":"person_id",
			"value":"A1234"
		}]
	}
}

Events API Usage

You may track an event using an identifier in place of a user_id using the unique_client_id object.

Note: The track an event API is not intended to create or update a profile using an additional identifier, therefore the recommendation is to ensure that the profile already exists before attempting to use an identifier other than user_id to associate events to a person.

CODE

{
    "activity":{
			"subscriber":{
				"unique_client_id":{
					"name":"person_id",
					"value":"A1234"
				}
			},
			"event":"test_event",
			"properties": {
				"property_name":"test"
			}
		}
}

Delete an Identifier

You may use the delete identifier API to remove unwanted IDs from a given profile. This can be useful if the identifier was added incorrectly, or if there has been a change and the identifier should be reassigned to a different profile and you don’t want to merge them.

CODE

{
  "request_type": "delete_identifier",
  "user": {
    "uid": "100001"
  },
  "remove_identifiers": {
    "name": "person_id",
    "value": "A1234"
  }
}

Campaigns

We currently support using these additional identifiers in file-based campaigns as an alternate key to identify customers, or in content using a liquid tag to populate the identifiers associated with the profile.

File-Based Campaigns

Note: There is an additional configuration needed to use this functionality, please be sure to let your Zeta Account Representative know that you’d like to use this feature.

When using file-based campaigns, typically a file contains a user_id and can contain an email contact, but when using another identifier in place of user_id you can ensure that source systems do not have to resolve their ID to the ZMP user_id so long as you’ve already associated those to your profiles. You may utilize any configured identifier to replace the user_id but must prefix it with unique_client_id_ to let ZMP know that this is now the key for your file.

For example

If your identifier is named person_id your column header should be named: unique_client_id_person_id

Content

You may also use the identifiers in content, or in content rules, by using the tag: {{unique_client_ids}} which will output a list of objects with the names and values of all the identifiers associated with the profile.

Sample result

CODE

{"name"=>"person_id", "value"=>"A1234"}{"name"=>"person_id", "value"=>"B1234"}