• All
  • Country
  • Product
Save as pdf

UUID Mapping

Prior to configuring the mapping process, both sides need to agree on the following:

  • Who will initiate the UUID mapping (Adform side/client side/both sides)?
  • Who will store the UUID mapping tables (Adform side/client side/both sides)?
  • What UUIDs will be provided in the data files for import (Adform UUIDs/client UUIDs)?

 

According the questions above, there are 5 scenarios how S2S integration might be configured.

Scenario No.  Mapping Initiation Mapping Table Storage
Scenario 1 Partner initiates the call Partner stores the mapping table
Scenario 2  Partner initiates the call Adform stores the mapping table
Scenario 3 Both sides initiate the call  Both sides store the mapping table
Scenario 4 Adform initiates the call Partner stores the mapping table
Scenario 5  Adform initiates the call Adform stores the mapping table

 

  • Scenario 1
    Partner initiates the call Partner stores the mapping table
    From partner From Adform
    SSL and non-SSL compliant empty endpoint pixel with a dedicated parameter for sending Adform UUID Configured endpoint pixel

    S2s 1 1

     

     

     

     

     

     

     

    Standard browser cookie mapping pixel (endpoint) :

    • http(s)://dmp.adform.net/serving/cookie/match/?party={adf_partner_id}&cid={partner_UUID}
      Each DMP account seat has a unique partner ID "adf_partner_id", which is identified in the mapping pixel.
    • http(s)://dmp.adform.net/serving/cookie/match/?party={adf_partner_id}&aid={Advertising_ID}
      Mobile Device ID pixel (no need for additional mapping, since Adform automatically converts Ad Id into Adform UUID).

     

    Adform endpoint may receive partner's UUID additionally if required and send back to partner's endpoint. 

     

  • Scenario 2
    Partner initiates the call Adform stores the mapping table
    From partner From Adform
    Adform endpoint pixel implementation Required endpoint with a dedicated parameter for receiving partner UUID

    This scenario is recommended by Adform due to the following reasons:

    • It includes a single call to an endpoint – quick and efficient;
    • Partners can make data imports using their own UUID values - UUID conversion is made on Adform side.

        S2s 2 (4)

    Standard browser cookie mapping pixel (endpoint) :

    http(s)://dmp.adform.net/serving/cookie/match/?party={adf_partner_id}&cid={partner_UUID}
    Each DMP account seat has a unique partner ID "adf_partner_id", which is identified in the mapping pixel.

    Mobile Device ID pixel (no need for additional mapping, since Adform automatically converts Ad Id into Adform UUID): http(s)://dmp.adform.net/serving/cookie/match/?party={adf_partner_id}&aid={Advertising_ID}

     

  • Scenario 3
    Both initiates the call Both store the mapping table
    From partner From Adform
    SSL and non-SSL compliant empty endpoint pixel with a dedicated parameter for sending Adform UUID Endpoint with a dedicated parameter for receiving partner UUID, configured partner's endpoint pixel
  • Scenario 4
    Adform initiates the call Partner stores the mapping table
    From partner From Adform
    SSL and non-SSL compliant empty endpoint pixel with a dedicated parameter for sending Adform UUID Mapping pixel; configured partner's endpoint pixel
  • Scenario 5
    Adform initiates the call Adform stores the mapping table
    From partner From Adform
    SSL and non-SSL compliant empty endpoint pixel with a dedicated parameter for sending Adform UUID Endpoint with a dedicated parameter for receiving partner UUID