Data requirements

Select the type of data to be uploaded:

Mobile device IDs

Expansion	CSV or TXT
Maximum size	1 GB
Encoding	UTF-8 or Windows-1251
Entry separator	Comma `aaaaaaaa-bbbb-cccc-1111-222222222200,aaaaaaaa-bbbb-cccc-1111-222222222201` Line break `aaaaaaaa-bbbb-cccc-1111-222222222200 aaaaaaaa-bbbb-cccc-1111-222222222201` Tab `aaaaaaaa-bbbb-cccc-1111-222222222200 aaaaaaaa-bbbb-cccc-1111-222222222201`
Entry format	Android (GAID) Lowercase alphanumeric string separated by hyphens. `aaaaaaaa-bbbb-cccc-1111-222222222200` iOS (IDFA) Uppercase alphanumeric string separated by hyphens. `AAAAAAAAA-BBBB-CCCC-1111-222222220000` `aaaaAAAAABBBBCCCC1111222222220000` Data in your file can be hashed (md5). In this case, each entry must be hashed separately. `a31259d185ad013e0a663437c60b5d0 78ee6d68f49d2c90397d9fbffc3814d1 702e8494aeb560dff987e623e71bccf8`
Minimum number of entries	100

MAC addresses

Expansion	CSV or TXT
Maximum size	1 GB
Encoding	UTF-8 or Windows-1251
Entry separator	Comma `AE123456D0A1,AE123456D0A0` Line break `AE123456D0A1 AE123456D0A0` Tab `AE123456D0A1 AE123456D0A0`
Entry format	A string in hex format. The MAC address can be hashed or unhashed. An unhashed MAC address is not case-sensitive. The MAC address is also not case-sensitive before hashing on the client side. The characters `. , : -` are not allowed. Unhashed MAC address — `AE123456D0A1`, hashed MAC address — `C5C32C30C07ABBB7580A0925D995FEE4` `5c:26:0a:6e:b5:bf` To hash a MAC address: convert the hex string to a byte string (two characters in hex is one byte) and extract the MD5 hash from it. Test pair for checking: mac — AE123456D0A1, mac_hash — C5C32C30C07ABBB7580A0925D995FEE4.
Minimum number of entries	100

Data from CRM

Expansion

CSV

Maximum size

1 GB

Encoding

UTF-8 or Windows-1251

Entry format

The first data string should list the field names, separated by commas. Each data string is a separate entry on a client. Entry fields are separated by commas.

Field values can be hashed (using MD5 or SHA-256). To make sure that values are processed correctly, when creating a segment, enable the Hashed data option and select the appropriate hashing algorithm.

Warning

Starting January 2025, uploading new MD5 hashes will no longer be supported. Please use SHA256 to upload data.

The data string must contain at least either the phone or email field. The remaining fields are optional.

`phone`	Phone number. A string of numbers that contains the mobile phone number and country code. You cannot insert spaces or use additional symbols. `79995551111` `7 (999) 555-11-11`
`email`	Email address. A string of Latin characters, including the @ symbol and the domain name. You cannot use uppercase letters. `mail@yandex.ru` `Mail@yandex.ru`
`external_id`	The client ID in the CRM. Alphanumeric string without spaces or extra characters.
	There are other fields that contain information about the client, such as the client's gender or date of birth.

Example of an entry without hashed values

external_id,phone,email,gender,birthdate
1,79876543210,mail@yandex.ru,M,01.01.1970
2,79012345678,example2@yandex.ru,F,01.01.1980

Example of sending data with MD5 hashing

external_id,phone,email,gender,birthdate
1,a31259d185ad013e0a663437c605d056,78ee6d68f49d2c90397d9ff77fc3814d1,M,01.01.1970
2,702e8494aeb560dff987eh623e71ccf8,f5ge43thaeb67df89875777e71bccf88i,F,01.01.1980

Example of sending data with SHA-256 hashing

external_id,phone,email,gender,birthdate
1,90f42df8309cc6c1dfd430a3f4ea7d6bfaa19f1853c6d16ec5ca30b40006476a,b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9,M,01.01.1970
2,d5579c46dfcc7f18207013e65b44e4cb4e2c2298f4ac457ba8f82743f31e930b,d3920c46dfcc7f18207013e65b44e4cb4e2c2298f4ac457ba8f23482f31e327b,F,01.01.1980

Minimum number of entries

100

Hashing (MD5 + SHA-256)

Data strings in your file can be hashed using MD5 or SHA-256. In this case, each entry must be hashed separately.

Correct format:

MD5 — a31259d185ad013e0a663437c60b5d0, 78ee6d68f49d2c90397d9fbffc3814d1, 702e8494aeb560dff987e623e71bccf8;
SHA256 — 90f42df8309cc6c1dfd430a3f4ea7d6bfaa19f1853c6d16ec5ca30b40006476a, b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9, d5579c46dfcc7f18207013e65b44e4cb4e2c2298f4ac457ba8f82743f31e930b.

Was the article helpful?

API versions

Error descriptions