Data onboarding Setup

Initial data parsing setup

Publishers store user data in many different ways, so we need to translate the structure of the CRM data into the digitalAudience tagging system. For this purpose, digitalAudience will need a sample data set from the publisher’s CRM system, a CSV export, to study the content and prepare the translation set for the publisher. If the CRM data uses lookup tables for grouping, the sample set should have a codebook explaining the coding used in the dataset.

Once the translation is ready, a publisher specifies a location - S3, SFTP or FTPS. Then the digitalAudience team sets it up and provides the credentials so that a publisher uploads a full export of their CRM data.

We recommend updating user data regularly to have the new opt-ins included in our database and the opt-outs processed on time. Publishers will use this storage connection to send the updated files to digitalAudience.

It is advisable to upload the hashed versions of email addresses and phone numbers in SHA256 hashing format. However, the publishers can upload plain email addresses and phone numbers. digitalAudience will hash the data and remove the uploaded file from our servers.

Please follow the formatting convention carefully to make sure that the email addresses and phone numbers get connected to the cookies that digitalAudience generates.

Emails

Put the email addresses in one separate column. Make sure that there is only one email address in each row. Lowercase the email address and remove the white spaces. Then, hash it using SHA256 algorithm.

Examples:

[email protected] > [email protected] >
A7DF77A9DB89B44110C704B680A24978579A3069B419DB95CBDA84541094ADBA

[email protected] > [email protected] >
A7DF77A9DB89B44110C704B680A24978579A3069B419DB95CBDA84541094ADBA

Phone numbers

Put the phone numbers in one separate column. Make sure there is only one phone number in each row. First remove the special characters like plus(+), backslash(/), dash(-), brackets(()), space( ). Reformat the number to conform the 31XXYYYYYYY format, where XX is the carrier code like 20 or 61 and YYYYYYY is the 7-digit phone number. In total it becomes an 11-digit number. Then, hash it using SHA256 algorithm.

Examples:

[phone] > 31614123456 >
5253828BF4B74309F76C1B1B3FC379584D9DC139874764D5D134E6C0FC7235AA

0-10-123 4567 > 31101234567 >
649C4E17CAB8316FA164573FCD76B945793FBAFC8FCF1AD89F9FBCA9B29F51EB