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:
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:
Connecting cookies to CRM data
CRM data is most valuable when the records are connected to a cookie, making the onboarded data available in various digital data marketplaces. The connection is created between the user’s email addresses and the cookies that digitalAudience drops in the user’s browsers. There are two different pixels used to create this connection.
Email pixel
It is injected at the key locations where an email address is available, for example email templates for newsletters. The pixel calls the digitalAudience cookie server for a cookie request and carries over the user’s email address (hashed version, if possible). Place this pixel in every newsletter the users receive, preferably at the beginning of the email.
This pixel will ensure that the data provided with the email addresses, and the CRM records connected to them, can be carried over to the data marketplaces.
Privacy Clause
digitalAudience requires publishers to include its privacy clause in their privacy statements. The clause is available in English and Dutch. Please see details below.
English
Dutch
Publishers need to make sure that digitalAudience (Vendor ID 133) is listed in the Vendors list in the CMP. This is required for the website script to function.
Website script
digitalAudience offers a website script designed to help publishers, on the one hand, make their traffic interoperable and, on the other hand, create segments and increase segment volumes in the data marketplaces.
Below are the instructions on how and where to place the script on all website pages.
The contents of the script may vary, depending on the publisher's use case. For example, they do not use a data management platform or need categorization or email addresses.
Add the following script to the end of the <body>
, close to the closing of the body tag </body>
;
partner
Data Management Platform (DMP) identifier provided by digitalAudience when applicable
parcid
User identifier provided by the DMP
publisher
Publisher's identifier provided by digitalAudience
category
If categorization is applied to the site structure and the category is available in the data layer, a single selected category (id) or an array [a,b,c] can be passed along
Hashed email address when available, for instance on a login page
syncs
consent
dpixel
Pixel id to generate dashboard data for this website
Privacy Clause
In case the publisher hasn't implemented a CMP yet, digitalAudience requires publishers to include its privacy clause into their cookie banners. The clause is available in English and Dutch. Please see details below.
English
Dutch
Last updated