File requirements
Select the type of data to be uploaded:
CRM data
|
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 client entry (multiple anonymous IDs can be found for one string). Entry fields are separated by commas. Field values can be hashed (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 is no longer supported. To upload new data, use SHA‑256. The entry must contain at least one of these fields:
Example of an entry without hashed values
SHA-256 hashing example
|
||||||
|
Minimum number of entries |
100 |
Mobile device IDs
|
Expansion |
CSV or TXT |
|
Maximum size |
1 GB |
|
Encoding |
UTF-8 or Windows-1251 |
|
Entry separator |
Comma
Line break
Tab
|
|
Entry format |
Android (GAID)Lowercase alphanumeric string separated by hyphens.
iOS (IDFA)Uppercase alphanumeric string separated by hyphens.
Data in your file can be hashed (SHA-256). In this case, each entry must be hashed separately. Warning Starting January 2025, uploading new MD5 hashes is no longer supported. To upload new data, use SHA‑256. SHA-256 hashing example
|
|
Minimum number of entries |
100 |
Still have questions?
Alert
Customer service specialists can advise you only on the ad campaigns linked to the login you are using to contact them. You can see your login in the upper-right corner of the screen. The specialist will get access to your data only when processing your request.


