DDM Integration for Third-Party App Tracking

The following end-to-end flow describes both advertiser setup and third-party implementation required in order to run a campaign on DoubleClick buy-side products using a third-party app tracking solution. For more information about DoubleClick Digital Marketing in general as well as an overview of in-app attribution functionality, please see the DoubleClick Digital Marketing background page.

  1. Advertiser sets up Conversion event in DDM to represent the install/conversion (Bid Manager only - conversion pixel) (Campaign Manager - Floodlight activity).
  2. Advertiser "links" DDM conversion event in the third-party interface and provides key variables that identify an advertiser and conversion activity group.

    • src is the advertiser ID that is the source of the Floodlight activity.
    • cat is the activity tag string, which Floodlight servers use to identify the activity group to which the activity belongs.
    • type is the group tag string, which identifies the activity group with which the Floodlight activity is associated.
    • u1, u2, ... (if available) are the custom Floodlight variable key-values.
  3. In addition, the advertiser needs to provide third parties with its specific authorization token: token is an advertiser-specific alphanumeric string that must be passed along with each server request to DDM.

  4. Advertiser runs in-app ad campaign with ad tags served by DBM on real-time bidding exchanges or served by DCM on direct-bought media.

  5. End user sees and/or clicks on ads, which are logged by DDM.

  6. When end user installs the app and/or completes a conversion event ("game play", etc.), thid-party servers "ping" DDM on every app activity

    https://ad.doubleclick.net/ddm/s2s/appactivity/src=1234567;cat=fghij456;type=abcde123;u1=[friendlyname1];ord=1312312312
    

    where:

    • src is the advertiser ID that is the source of the Floodlight activity.
    • cat is the activity tag string, which Floodlight servers use to identify the activity group to which the activity belongs.
    • type is the group tag string, which identifies the activity group with which the Floodlight activity is associated.
    • ord is a random number that is used to make the Floodlight tag unique.
    • u1, u2, ... (if available) are the custom Floodlight variable key-values.

    with additional parameters sent via JSON payload in an HTTP POST:

    {
      "app": {
        "bundle": "com.rovio.angrybirds"
      },
      "device": {
        "ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25",
        "ip": "108.176.57.230",
        "didmd5": "A2D2DA47AC2DE1BCA16883BD5CAA6F2F",
        "lmt": 1
      }
    }
    

    and the advertiser authorization token is passed in the HTTP Authorization Header:

    Authorization: Token token="[advertiser authorization token string]"
    

    where:

    • app (if available) is the JSON object representing the app where the conversion activity took place.
    • bundle (if available) is the app object field containing a string value of the Play Store bundle name or App Store ID.
    • device is the JSON object representing the device on which the conversion activity took place.
    • ua is the device object field representing the user agent string of the app where an activity was recorded. This parameter is required.
    • ip (if available) is the device IPv4 address assigned to the device. This parameter is required.
    • didmd5 is the MD5-hash string of the uppercased IDFA or Google Play Advertising ID value.
    • lmt is an integer, with a value of 1 if the user has enabled the "Limit Ad Tracking" option with IDFA/AdID, or 0, if not set.

    DDM will respond with a JSON response of whether the conversion event is attributed to a view or click served by DCM, and if "YES", additional information about the event (last view or click):

    - Ad ID
    - Site ID
    - Placement ID
    - Creative ID
    - Timestamp
    

    An example JSON response might look like:

    {"attributed": 1,  // Whether or not conversion can be attributed to DCM event.
     "last_impression_ad_id":283641088,
     "last_impression_site_id":1408067,
     "last_impression_placement_id":107616368,
     "last_impression_creative_id":60162352,
     "last_impression_timestamp":1415647607,
     "last_click_ad_id":283641088,
     "last_click_site_id":1408067,
     "last_click_placement_id":107616368,
     "last_click_creative_id":60162352,
     "last_click_timestamp":1415647657,
     "last_click_exclid":"CKm0nLKhyssCFceH2wod8l4I4A"}
    

    where:

    • attributed is value 1 (if the conversion can be attributed to an impression or click) or 0 (if not attributable).
    • last_impression_ad_id (if attributed = 1) is the ad ID for the last impression.
    • last_impression_site_id (if attributed = 1) is the site ID for the last impression.
    • last_impression_placement_id (if attributed = 1) is the placement ID for the last impression.
    • last_impression_creative_id (if attributed = 1) is the creative ID for the last impression.
    • last_click_ad_id (if attributed = 1 and a click was attributed) is the ad ID for the last click.
    • last_click_site_id (if attributed = 1 and a click was attributed) is the site ID for the last click.
    • last_click_placement_id (if attributed = 1 and a click was attributed) is the placement ID for the last click.
    • last_click_creative_id (if attributed = 1 and a click was attributed) is the creative ID for the last click.
    • last_click_exclid corresponds to a unique click ID populated via the %eiid! macro

    with HTTP error codes, for the following scenarios:

    • HTTP 401 if the authorization token is invalid.
    • HTTP 204 if the request quota has been exceeded.
    • HTTP 404 for any bad requests.

    Advertiser will be able to see campaign reports in your system; advertiser will also be able to see conversion reports in DCM with same parameters as above.

Enviar comentarios sobre…

Third-Party Apps Conversion Tracking
Third-Party Apps Conversion Tracking