Segments import
Last updated
Was this helpful?
Last updated
Was this helpful?
Use this feature to add or remove from .
Use the endpoints to create a with theUSER_SEGMENT
document type and APPLICATION_X_NDJSON
or TEXT_CSV
mime type.
Create anwith your user segment commands formatted in ndjson
or csv
depending on the mime type you chose.
Each line in the uploaded file can have the following properties:
field
type
description
operation
Enum (Mandatory)
Either UPDATE
or DELETE
compartment_id
String (Optional)
user_account_id
String (Optional)
email_hash
String (Optional)
user_agent_id
String (Optional)
segment_id
String (Optional)
The Id of the segment in which the User is inserted/deleted.
segment_technical_name
String (Optional)
The technical name of the segment in which the User is inserted/deleted.
expiration_duration
Integer (Mandatory)
The number of minutes before the user will be removed from the segment. 0 means that the User will never leave the segment
expiration_ts
Number (Optional)
The timestamp of the expiration date of the User in the segment. A value of 0 means that the user will never leave the segment
data_bag
Escaped JSON String (Optional)
The data bag associated with the user/segment relationship
You can have UPDATE and DELETE operations in the same file upload.
Please note, if not using csv
, that the uploaded data is in ndjson
and not json
. That means the different profiles are not separated by commas, but by a line separator \n
The Compartment ID acting as a in correlation with the user account ID
The User Account ID acting as a in correlation with the user account ID.
The Email Hash acting as a .
The User Agent ID acting as a .