TheTradeDesk In-App Events Connector Setup Guide

TheTradeDesk In-App Events Connector Setup Guide

by 4 weeks ago (31 Views)

With The Trade Desk, buyers can value each impression like traders value stocks, using first and third party data to decide which impression to buy and how much to pay. This article describes how to set up the theTradeDesk In-App Events connector in your Universal Data Hub account.

Table of Contents Placeholder

Connector Actions

Action Name AudienceStream EventStream
Send In-App Event

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Advertiser ID (adv): This represents your Advertiser ID on The Trade Desk.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send In-App Event

Parameters

Parameter Description
TTD Event Tracker ID (upid)
  • TTD Event Tracker ID (upid)
Mobile App Event (ref)
  • This should be the same as the name of the event. Same as the value that you have configured on The Trade Desk configuration page for this specific event (ref)
Mobile Client IP Address (client_ip)
  • Mobile Client IP Address (client_ip)
Mobile IDFA for iOS (idfa)
  • IDFA is the iOS ID for Advertisers (idfa)
Mobile GPS ADID for Android (gps_adid)
  • GPS ADID is the Google Play Advertiser ID (gps_adid)
Mobile NAID for Windows (win_naid)
  • Windows NAID is the Windows Phone Device ID (win_naid)
Revenue Tracking Value (v)
  • Revenue tracking parameters (v & vf) will only be sent if the UI was enabled
    • Note that ISO 4217 currency codes are used for vf field
    • Floating point numbers are expected for the v field (ex: 0.99, 3.99, etc)
Revenue Tracking Currency (vf)
  • Revenue tracking parameters (v & vf) will only be sent if the UI was enabled
    • Note that ISO 4217 currency codes are used for vf field
    • Floating point numbers are expected for the v field (ex: 0.99, 3.99, etc)
Additional Query Data
  • Provide any additional url query parameter data if needed