Mapping Users to Panelists

Before using the API, you need to establish a link between your user base and Cint's Panelists. To do this you need to be able to identify your own users with a unique custom ID and map those IDs to our panelist IDs.

Once the link is established, you can query the API by sending a list of your user IDs to retrieve profiling data for panelists that have opted in to sharing their data.

Mapping options

Cint provides several ways of synchronizing external users to panelists. Either through an ad-hoc setup with you as a partner, by using known identifiers (such as Mobile Ad IDs), or by using a tag on an online web page that you have access to.

Online Tag

The online tag setup is based on the assumption that you (in a browser session) have access to a unique ID that identifies the user that you want to sync to our panelist base.

The mapping from your user ID to our panelist is done by placing an html tag on a commonly accessed web page. The tag is basically just a way of triggering a web request to Cint with your user ID as a parameter.

When a user visits this page, a web request is sent to our systems and if the request originates from a user that also is a panelist, we will be able to identify him or her and store a link between your Id and our panelist.

URL format

The URL used for mapping should look like the following example (where strings within brackets should be replaced according to instructions below):

https://c.cintnetworks.com/identity?a={accountId}&id={type:id} 

The accountId is a number that identifies you as a customer. You should have received this when you were given an API key.

The type parameter is a name that specifies which ID you want to sync. You might have several types of IDs that you want to map, see below.

The id is the actual user ID that identifies your user and that should be unique for each person accessing the web page.

Note: The following characters are considered safe for use in query string parameters: Alphanumeric characters (a-z, 0-9), dashes (-), dots (.), underscores (_), tildes (~).

Example

If you as a customer have accountId 12345, and you have a user database called MyDSP and you display a page to a customer having Id 9342423 in the database, the Url request should be:

https://c.cintnetworks.com/identity?a=12345&id=MyDsp:9342423

Different types of IDs

When using the mapping tag URL you need to specify both the type of ID and the unique ID itself. This allows you to separate between multiple types of user IDs in the same system (e.g. one from your advertising system and one from your content management system). The only requirement is that each ID identifies a single user. The type can be any logical name identifying the source of your IDs. For example, you may have both internal IDs and mobile ad IDs mapped to your users.

The type of ID is part of the request, and you will also need to specify this when accessing the profiling data API.

Multiple IDs in single request

You can append multiple identifiers in one request:

https://c.cintnetworks.com/identity?a=12345&id=MyDsp:9342423&id=idfa:20f529e3-d6ff-4f49-8245-13558a393af1