Integrations

There are several steps to integrate you as a Data Provider to Admixer.

Taxonomy

First, you must provide a taxonomy of IDs and User Segments Names in .csv format.

Expand the taxonomy example
ID,SegmentName
1,Segment1 
2,Segment2
3,Segment3

Cookie-matching

Next, cookie-matching must be set up. There are 2 ways how it can be done.

Method 1: You as a Data Provider store user identifiers in cookies and keep the matching table on your side (preferable).

You then provide us with a matching pixel.

Expand the matching pixel example
https://provider_url.com?t=[VisitorKey]

Method 2: We store user identifiers in cookies and keep the matching table on our side. 

In this case, the cookie-matching URL will have the following look.

Expand the cookie-matching URL example
https://provider_url.com?t=[VisitorKey]&rurl=https://inv-nets.admixer.net/adxcm.aspx?ssp=E11111A8-B111-11DEZ1BE-1111F08BF111&uid=[data-provider-uid]

where

[VisitorKey] - passes visitor id
rURL parameter should be able to accept Admixer redirect URL 
[data-provider-uid] - passes Data Provider’s user ID

Data import

We expect that Data Provider will give us an HTTP/FTP endpoint which will provide us with raw data in .csv format with 2 required fields.

  • In case when Data Provider matches the ids on its side and keeps the data, we will receive the following.
Expand the ID array example
Admixer-uid,segments
e332bab1762a4c49bb100bc5fe41cf85,1,2,3
c66ca0443d9d4f008bc75bdd9c5d4912,3
354967c74cdd4a3db14b942f29cfba96,1,3
  • In case Admixer matches the ids on its side and keeps the data, we will receive the following.
Expand an example of stored IDs array
data-provider-uid,segments
e332bab1-762a-4c49-bb10-0bc5fe41cf85,1,2,3  
c66ca044-3d9d-4f00-8bc7-5bdd9c5d4912,3
354967c7-4cdd-4a3d-b14b-942f29cfba96,1,3

If you are unable to provide an HTTP/FTP endpoint, we can provide you with the keys so you will be able to upload the data on our server (azure blob) by yourself.

Updated on January 11, 2023