User choices import
Last updated
Was this helpful?
Last updated
Was this helpful?
Use this feature to UPSERT or DELETE in your datamart.
Use the endpoints to create a with theUSER_CHOICE
document type and APPLICATION_X_NDJSON
mime type. Only ndjson
data is supported for user choices.
Then, create anwith your user choice import commands formatted in ndjson
.
Each line in the uploaded file can have the following properties:
field
type
description
operation
Enum
Either UPSERT
or DELETE
compartment_id
String (Optional)
user_account_id
String (Optional)
email_hash
String (Optional)
user_agent_id
String (Optional)
force_replace
Boolean (Optional)
Mandatory when the operation is UPSERT
.
If true, then the User Choice will be completely replaced by the object passed in the user_choice
field.
If false, the object passed in the user_choice
field will be merged with the existing User Choice of the User Point.
user_choice
JSON Object (Optional)
Mandatory when operation is UPSERT.
This is a JSON Object representing the User Choice.
information.
Note that the $processing_id
field is always mandatory, and $choice_ts
is mandatory when operation is UPSERT
.
You can, of course, upload multiple user choices at once. Note the uploaded data is in ndjson
format and not json
. That means the different choices are not separated by commas, but by a line separator \n
When importing choices with identifiers, only one identifier is allowed per line. For example, you shouldn't specify the user agent ID if the Email Hash is already used in a line.
The Compartment ID, acting as a user in correlation with user_account_id
The User Account ID, acting as an in correlation with compartment_id
The Email Hash, acting as an
The User Agent ID, acting as an
Please refer to the for more