Cookie matching

Table of contents

 

For matched users, both SSP UID and DSP UID will be sent in the fields bidRequest.user.id and bidRequest.user.buyeruid (find more here). If user is new, there only SSP UID (bidRequest.user.id) will send.

There’re 4 possible scenarios for cookie matching:

MGID initiate and MGID (both) store table

For this scenario MGID expect from Partner sync url and user id in MGID redirect url

Link example:

[https://partnerURL.com/sync?gdpr={GDPR}&gdpr_consent={GDPR_CONSENT}&us_privacy={CCPA_CONSENT}&redirect_url=https://cm.mgid.com/m?cdsp=123456&c={user.id}]

 

MGID initiate sync Partner store table

MGID will expect only partner sync url with user.id parameter

Link example:

[https://partnerURL.com/sync?user_id={muidn}&gdpr={GDPR}&gdpr_consent={GDPR_CONSENT}&us_privacy={CCPA_CONSENT}]

 

Partner initiate sync MGID (both) store table

MGID will expect call of MGID sync url with changed user macro

Link example:
[https://cm.mgid.com/m?cdsp=123456&c={user.id}&gdpr={GDPR}&gdpr_consent={GDPR_consent_string}&us_privacy={CCPA_consent_string}&adu=https://partnerRedirectUR.com/sync?user_id={muidn}]

 

Partner initiate and Partner (both) store table

MGID will expect call of MGID sync url with changed user.id macro and partner redirect url with user.id parameter

Link example:

[https://cm.mgid.com/m?cdsp=123456&gdpr={GDPR}&gdpr_consent={GDPR_consent_string}&us_privacy={CCPA_consent_string}&adu=https://partnerRedirectUR.com/sync?user_id={muidn}]

where:

  • {GDPR} - 0 - indicates that the user is not located in the country under the GDPR regulations. 1 - indicates that the user is located in the country under the GDPR regulations
  • {GDPR_consent_string} - IAB consent string provided when the request is subject to GDPR
  • {CCPA_consent_string} - consent string provided when the request is subject to US Privacy zone
  • {user.id} - platform specified user identifier
  • {muidn} - MGID specified user identifier