User identifiers association
This document import allows you to merge user points by associating their user identifiers. Each line in the document represents a different user identifiers association
This is only supported for datamarts using a user point system version of v201812
or later.
How-to
Use the bulk import endpoints to create a document import with the
USER_IDENTIFIERS_ASSOCIATION_DECLARATIONS
document type andAPPLICATION_X_NDJSON
mime type. Onlyndjson
data is supported for user activities.Create an execution with your commands formatted in
ndjson
.
User identifiers association command
Each line will create/merge a user point that has all the specified identifiers
field | type | description |
identifiers | UserIdentifierResource[] | An array of User Identifier Resource of any type |
User identifier resource can be of three shapes. Either email or user agent or user account id. They correspond with the different types of user identifiers.
Email
field | type | description |
type | "USER_EMAIL" | The type of the identifier. |
hash | String | A hash of the email. The hashing function should be unique per datamart. |
String (optional) | the email address |
User Agent
field | type | description |
type | "USER_AGENT" | The type of the identifier. |
user_agent_id | String | The user agent ID |
User Account
field | type | description |
type | "USER_ACCOUNT" | The type of the identifier. |
user_account_id | String | The User Account ID |
compartment_id | String (optional) | The Compartment ID. If you don't input the compartment id it will fall back on the default one |
Example
You can, of course, add different identifier types at the same time. Please note that the uploaded data is in ndjson
and not json
. That means the different additions are not separated by commas, but by a line separator \n
Last updated