Difference between revisions of "Cookie matching"

From Service Manual Kadam.net
Jump to: navigation, search
(Created page with "== Integration SSP == {| class="wikitable" style="width: 85%;" |- | style="width: 10%"|'''Initiator''' | style="width: 10%"|'''Keeper''' | style="width: 20%"|'''Kadam's link'...")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
The ad networks install third-party cookies on each user's DMP domain so that to recognize it when they interact with it again. The Cookie Matching setting will allow you to avoid showing ads to a user repeatedly, and can be used in predicting his interests, as well as retargeting.
 +
 +
Cookie Matching is needed to match your cookie - the user id (according to your version) who has browsed your website with the corresponding user id according to Kadam's version. In order for this matching to happen, the SSP or DSP needs to be proactive and show the DMP pixel to the partner. The purpose of showing the partner pixel is to tell the partner the user id of your version and keep the link in the mapping table.
 +
 +
The custodians can be: SSP, DSP, both. You can see the different integration schemes below.
 
== Integration SSP ==
 
== Integration SSP ==
  
Line 11: Line 16:
 
|SSP
 
|SSP
 
|SSP
 
|SSP
|<nowiki>https://d.uuidksinc.net/match/{dspid}/?remote_uid={dsp-userid}</nowiki>
+
|<nowiki>https://s.uuidksinc.net/match/{dspid}/?remote_uid={ssp-userid}</nowiki>
 
|callback url
 
|callback url
 
|1. Kadam send pixel to SSP.
 
|1. Kadam send pixel to SSP.

Latest revision as of 10:23, 30 September 2022

The ad networks install third-party cookies on each user's DMP domain so that to recognize it when they interact with it again. The Cookie Matching setting will allow you to avoid showing ads to a user repeatedly, and can be used in predicting his interests, as well as retargeting.

Cookie Matching is needed to match your cookie - the user id (according to your version) who has browsed your website with the corresponding user id according to Kadam's version. In order for this matching to happen, the SSP or DSP needs to be proactive and show the DMP pixel to the partner. The purpose of showing the partner pixel is to tell the partner the user id of your version and keep the link in the mapping table.

The custodians can be: SSP, DSP, both. You can see the different integration schemes below.

Integration SSP

Initiator Keeper Kadam's link SSP's link Cookie matching launch checklist
SSP SSP https://s.uuidksinc.net/match/{dspid}/?remote_uid={ssp-userid} callback url 1. Kadam send pixel to SSP.

2. SSP makes settings to set the pixel.

3. SSP provides a link to the callback url.

4. Kadam performs a redirect setting on the callback url.

5. In the bid request SSP sends the buyeruid - user ID in the Kadam system.

SSP DSP https://s.uuidksinc.net/match/{sspid}/?remote_uid={ssp-userid} - 1. Kadam send pixel to SSP.

2. SSP makes settings to set the pixel (SSP version ID should be substituted for {ssp-userid} in the pixel url).

SSP Both https://s.uuidksinc.net/match/{sspid}/?remote_uid={ssp-userid} callback url 1. Kadam send pixel to SSP.

2. SSP makes settings to set the pixel (SSP version ID should be substituted for {ssp-userid} in the pixel url).

3. SSP provides a link to the callback url.

4. Kadam performs a redirect setting on the callback url.

5. In the bid request SSP sends the buyeruid - user ID in the Kadam system.

DSP SSP - callback url 1. SSP provides a link to the callback url.

2. Kadam performs a redirect setting on the callback url.

3. Kadam makes settings to set the pixel.

4. In the bid request SSP sends the buyeruid - user ID in the Kadam system.

DSP DSP https://s.uuidksinc.net/match/{sspid}/?remote_uid={ssp-userid} pixel 1. Kadam send a link to the callback url to SSP.

2. SSP performs a redirect setting (SSP version ID should be substituted for {ssp-userid} in the pixel url).

3. SSP provides pixel.

4. Kadam makes settings to set the pixel.

DSP Both https://s.uuidksinc.net/match/{sspid}/?remote_uid={ssp-userid} pixel 1. Kadam send a link to the callback url to SSP.

2. SSP performs a redirect setting (SSP version ID should be substituted for {ssp-userid} in the pixel url).

3. SSP provides pixel.

4. Kadam makes settings to set the pixel.

5. In the bid request SSP sends:

  • user.id - SSP version ID;
  • buyeruid - user ID in the Kadam system.

Integration DSP

Initiator Keeper Kadam's link DSP's link Cookie matching launch checklist
DSP DSP https://d.uuidksinc.net/match/{dspid}/?remote_uid={dsp-userid} callback url 1. Kadam send pixel to DSP.

2. DSP makes settings to set the pixel (DSP version ID should be substituted for {dsp-userid} in the pixel url).

3. DSP provides a link to the callback url.

4. Kadam performs a redirect settings.

5. In the bid request Kadam sends the user.id.

DSP Kadam https://d.uuidksinc.net/match/{dspid}/?remote_uid={dsp-userid} - 1. Kadam send pixel to DSP.

2. DSP makes settings to set the pixel (DSP version ID should be substituted for {dsp-userid} in the pixel url).

3. In the bid request Kadam sends user.id and buyeruid.

DSP Both https://d.uuidksinc.net/match/{dspid}/?remote_uid={dsp-userid} callback url 1. Kadam send pixel to DSP.

2. DSP makes settings to set the pixel (DSP version ID should be substituted for {dsp-userid} in the pixel url).

3. DSP send a link to the callback url.

4. Kadam performs a redirect settings.

5. In the bid request Kadam sends user.id and buyeruid.

Kadam DSP - pixel 1. DSP provides pixel.

2. Kadam makes settings to set the pixel and performs a redirect settings.

3. In the bid request Kadam sends the user.id.

Kadam Kadam https://d.uuidksinc.net/match/{dspid}/?remote_uid={dsp-userid} pixel 1. DSP provides pixel.

2. Kadam makes settings to set the pixel.

3. Kadam provides a link to the callback url.

4. DSP performs a redirect settings (DSP version ID should be substituted for {dsp-userid} in the pixel url).

5. In the bid request Kadam sends user.id and buyeruid.

Kadam Both https://d.uuidksinc.net/match/{dspid}/?remote_uid={dsp-userid} pixel 1. DSP provides pixel.

2. Kadam makes settings to set the pixel.

3. Kadam provides a link to the callback url.

4. DSP performs a redirect settings (DSP version ID should be substituted for {dsp-userid} in the pixel url).

5. In the bid request Kadam sends the user.id.