DMPs are used by our customers to aggregate, classify & score their visitors into different segments.
Why Connecting a DMP with AB Tasty?
We are doing partnership programs with DMPs to have access to these segment information and their attributes. Thanks to the connectors, our clients can run more powerful personalizations & tests with advanced targetings based on DMP data.
To make it work, we have two requirements:
- In the client’s website, we must be able to get the segment information of the visitor, to verify if he is validating the test’s targeting.
- In the AB Tasty interface, we must be able to get the exhaustive segments list of an account. Thanks to that, the customer will be able to target his test on a specific segment.
DMP Type 1 : Cookie matching
DMPs deposit a file on our server.
- Regularly, DMP is sending us a csv file with a batch of data.
- Every file contains new userId with their userSegments associated.
- We’re parsing them before inserting them into the database.
How to send segments to AB Tasty ?
- You will have to send the segment to an S3 Bucket.
- We will provide you an
- You will have to upload your file in a
- The format of the file should be
Inside the file, we should have every visitorID and the segments they belong to.
Once data is in our database, we are able to answer the 2 following requirements:
- The exhaustive list of segments is recovered by reading the database and parsing them by name => Set up the targeting.
- The segments of the user are sent back on the DCInfos request which is loaded at the first page seen of every session => Apply the targeting.
On AB Tasty’s interface
DMP Type 2 : Browser access
Group A: JS variable / datalayer / cookie
- The tag reads what is inside the variable js / datalayer / cookie.
- If the segments corresponds to the targeting, we apply the test.
Group B: Ajax Call
- The tag calls an AJAX request to the DMP server on the customer’s website.
- The AJAX request is answering the segment of the current visitor and we store them into the sessionStorage under a specific variable (example: ABDMPName).
Thanks to the browser informations, we get one of the two requirements:
- This type permits to get all the segments of the user during his navigation.
The second requirement (recover the exhaustive list of all segments) needs another mechanism:
- The DMP has to give us an endpoint to call to get all these information (by passing the account id into parameters for example).