Customer data format

Required columns:

• uniq_id: Customer ID. For example, the customer ID in the CRM. An arbitrary string.

Optional columns:

You can change any data.

• name: Customer name. An arbitrary string.
• create_date_time: Date and time of contact creation in the tag's time zone.More information
• update_date_time: Date and time of contact update in the tag's time zone.More information
• client_ids: List of ClientIDs. For more information, see Preparing data to be linked to sessions.
• emails: List of client's email addresses. A string in Latin including the @ symbol and domain name. You can't use uppercase letters. Example: mail@yandex.ru.
• phones: List of client's phone numbers. A numeric string containing a mobile phone number with a country code. You can't use spaces or extra characters. Example: 79995551111.
• emails_md5: List of client's email addresses that are md5 hashed. You can use the email address mail@yandex.ru to test your hashing algorithm. The expected hash for this address is 3c56ff8fef0f6c65b36b2d25720fe276.
• phones_md5: List of client's phone numbers that are md5 hashed. You can use the number 79995551111 to test your hashing algorithm. The expected hash for this number is f09f2c3d48f31e2a802944ade2e5aec5.

You can also transmit additional information about customers, such as the type of customer (individual or business). To do this:

1. Create an attribute that will match your additional parameter using the POST /cdp/api/v1/counter/{counterId}/schema/attributes method.
2. Pass this attribute along with other customer data using the POST /cdp/api/v1/counter/{counterId}/data/contacts method (CSV or JSON). When using JSON, you can use the attribute_values array for convenience.

Learn more

• Order data format
• Date and time format