Deal ID Implementation

Overview

The dealID workflow has three significant phases:

• Inventory identification
• Audience delivery
• Deal activation

Inventory Identification

The vast majority of the work required to enable Deal IDs overlaps with the enabling generic RampID workflows. You must be able to go from a source of inventory (cookieable, mobile device, cookieless/ATS) to an identity Envelope. LiveRamp’s APIs or mapping files can be used for this purpose. The Sidecar accepts identity envelopes as an input.

But unlike a traditional programmatic workflow, your Sidecar will additionally be instantiated with a key for your own RampID. This decrypted RampID is essential to perform an audience lookup.

Before activating deal ID functionality, you may have queried the Sidecar with an Envelope and seen output for:

{
  "ttd": "Xi3022CxsryScO961hgy7Wv7z6H8fO4UZAEoUokyBg2wxLgt6TGleZlntpNJM_XUoYsebx",
  "criteo": "Xi1350AKEhNPrm_y49wWV0hW49_erVLMFKES7OgcEg5CoWzibxYiTdpzLQWWqvt_dUIjrI"
}

Once LiveRamp has provisioned an additional RampID key for you, the same query would produce:

{
  "ttd": "Xi3022CxsryScO961hgy7Wv7z6H8fO4UZAEoUokyBg2wxLgt6TGleZlntpNJM_XUoYsebx",
  "criteo": "Xi1350AKEhNPrm_y49wWV0hW49_erVLMFKES7OgcEg5CoWzibxYiTdpzLQWWqvt_dUIjrI",
  "you": "Xi9999BQRhNPrm_y49wWV0hW49_erVLMFKES7OgcEg5CoWzibxYiTdpzLQWWqvt_dUJfVG"
}

With the ability to go from an impression to an RampID, you now need to perform a lookup to see if your RampID matches with any marketer audiences.

Audience Delivery

You will need to accept audience files (containing either first or third-party data) tied to your RampID. Most platforms chose to receive data and taxonomy files delivered in batch to an S3 or SFTP endpoint.

XY9999tQk-hsKmFhahNe5nhYtgjaC1dfA4tPmkIF6r8Pw_jqk	123456
XY9999kMarGSUxAXpKw0cwE894VwfuhqJ2ri4E_umqKGkrK3p	123456,678901
Xi9999Lbrteki15uEaWPRK-ot5OZjUw6vAosEXlv8hba9XVt6PaCI69v5cvpKWViTS8EsY	678901
XY9999NzOUz_47uouv9v1mdRdOUrpQ6poN_1-cpFe92ahYCGF	123456,678901
Xi9999jjcwdp0mn9rnyYXhNjVW23G4_UuSoOZ-LDeyRJtgf2TS_r-3JJhOHfHxXd8H4ccD	123456
XY9999XFpEQMn3i7pOYJlVP9OQZ20pAmfR3hSK_eMydCU8RMl	123456
XY999928wrTAqRkByX5Y-BYVK1u7OCXm2aTbvfbl32jrlor8N	678901
XY9999vqDPZ75J3wULs5OqGKQ_-iielQC10izGfvqcRlLRfdF	123456,678901
XY9999BUvYq3cmqd3sDY_B_mlNymvHNZpYbuKq7uW_z0aqMDF	123456,678901
Xi9999OIL5xr5hNMHRAVbA-k6cUZ_e5Ozvx1A21PIoRfxHGe8PvTMWkLayv7lp9idRsNWD	678901

Segment ID,Field Name,Value Name
123456,Likes Dogs,TRUE
678901,Likes Cats,TRUE

See full integration documentation here for more information about file naming, file refresh cadence and additional delivery options.

📘

Onboarding Data via API

Accepting advertiser data directly via the Identity Retrieval API is also an option. You would be able to resell first party data onboarding and leverage the API to build a UI for your clients.

Deal ID Activation

The final step brings together the two described above to flag an impression of interest to your buyer(s). As you decode envelopes, you will output your RampID. Using your RampID, you will perform a lookup against audience data.

If a matching audience and deal is found, add one or more Deal objects to the Pmp object in the outgoing bid request.

{
  "pmp": {
    "private_auction": 0,
    "deals": [
      {
        "id": "mydeal1"
      }
    ]
  }
}