User profiles import
Use this feature to UPSERT or DELETE user profiles in your datamart.
How-to
Use the bulk import endpoints to create a document import with theUSER_PROFILE
document type and APPLICATION_X_NDJSON
mime type. Only ndjson
data is supported for user profiles.
Then, create an execution with your user profile import commands formatted in ndjson
.
User profile import command
Each line in the uploaded file can have the following properties:
field | type | description |
operation | Enum | Either |
compartment_id | String (Optional) | The Compartment ID, acting as a user identifier in correlation with |
user_account_id | String (Optional) | The User Account ID, acting as an identifier in correlation with |
email_hash | String (Optional) | The Email Hash, acting as an identifier |
user_agent_id | String (Optional) | The User Agent ID, acting as an identifier |
force_replace | Boolean (Optional) | Mandatory when the operation is |
merge_objects | Boolean (Optional) | Only considered if Manage the comportement between two objects with a same property. If false (default value), the new object overrides the existing one. If true the new object is merged in deep to the existing one (see example). |
user_profile | JSON Object (Optional) | Mandatory when operation == UPSERT. JSON Object representing the User Profile. Please refer to the user profile object for more information. |
Example
You can, of course, upload multiple user profiles at once. Note 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
When importing profiles 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.
More details on merge_objects
behavior :
Last updated