This is a multi-step guide for setting up your Digital Turbine campaign with Kochava.
Step 1. Creating a Campaign and Tracker
Step 2. Setting Up Partner Configuration
Step 3. Setting Up Install Postbacks
Step 4. Setting Up Lookback Windows
Step 5. Setting Up Cost Tracking
Step 1. Creating a Campaign and Tracker
- Navigate from the homepage to Apps & Assets→All Apps, click the ⋮ icon next to your app, and select Campaign Manager from the drop-down menu.
- Click Add a Tracker.
- Select Campaign and Segment from the drop-dow menu.
Note
In Kochava, trackers must be linked to both a campaign and a segment. This is automatically defaulted by the platform.
- Now that you have reached the campaign window, type your Tracker Name.
Tip
Enter Digital Turbine here or follow your naming convention for trackers.
- From the Tracker Type drop-down, select Acquisition.
- Next step depends on the platform you are setting up for:
From the Media Partner drop-down, select Digital Turbine – Android.
From the Media Partner drop-down, select Digital Turbine – iOS.
Note
iOS campaigns where probabilistic matching is desired require specific privacy settings:
- Go to Apps & Assets→Privacy Profiles.
The Privacy Profiles section opens.
- Add (A) or edit (B) a privacy profile.
The privacy profile settings section opens.
- Set the Collect toggle for IP Address and User Agent to
YES
. - Set the attribution of IP Address and User Agent to
Paid & Owned Media
. - Click Save.
For more information, read about Kochava’s Privacy Profiles or contact your Digital Turbine representative.
- Check the SHARE WITH PUBLISHER checkbox.
- Leave Destination URL settings as default. Click Save.
- Copy the Click URL and Impression URL and send them to your Digital Turbine representative.
Step 2. Setting Up Partner Configuration
- Go to Apps & Assets→All Apps, click the ⋮ icon for your app, and select Partner Configuration from the drop-down menu.
- Click Add a Configuration.
- From the Media Partner drop-down, select Digital Turbine - Android and click Go.
Step 3. Setting Up Install Postbacks
- Click the ⋮ icon for the Install event Postback, and select Edit from the drop-down menu.
- For the App Store ID, enter your app’s bundle ID/package name. Leave the Digital Turbine App ID blank.
- Configure the settings as shown below and click Save.
Settings | Value |
---|---|
Delivery Delay | Realtime Delivery |
Retry Attempts | 3 Attempts |
Deliver Method | All |
- Configure Post-Install event postbacks.
- Required Events:
- SessionBegin
- Any event used for a KPI or optimization (ex: purchase, level, reached, first delivery).
- Recommended Events:
- Any event used for secondary KPIs.
- Any event used for upper funnel metrics that are leading indicators of primary KPIs (ex.: registration, tutorial complete, add to cart).
- Locate the desired post-install event, click the ⋮ icon, and select Create from the drop-down menu.
- For the App Store ID, enter your app’s bundle ID/package name. Leave the Digital Turbine App ID blank.
- If there is a ROAS target, check the Send Revenue Data checkbox for events with a revenue value (ex.: purchase, adview, checkout).
- From the Event Type drop-down, select the corresponding standard event name.
Note
Digital Turbine machine learning algorithms rely on standard event names to improve ad targeting, optimization, measurement, and insights. For best results, use these names for event mapping:
- app_open
- purchase
- level_achieved
- ad_click
- ad_view
- login
- add_payment_info
- add_to_cart
- add_to_wishlist
- checkout_initiated
- complete_registration
- complete_tutorial
- reservation
- update
- subscribe
- search
- view_content
- credits_spent
- achievement_unlocked
- app_rated
- tutorial_complete
- social_share
If there's no suitable name on this list for an event, you can add an arbitrary event name. However, make sure there are no spaces and special characters in it other than the underscore ( _ ).
- Select the following settings:
Settings | Value |
---|---|
Delivery Delay | Realtime Delivery |
Retry Attempts | 3 Attempts |
Deliver Method | All |
- Click Save. Repeat Steps 6-10 for any additional post-install events that you need to send to Digital Turbine.
Step 4. Setting Up Lookback Windows
For proper attribution, ensure that you set up lookback windows.
- Go to Apps & Assets→Partner Configuration, click the ⋮ icon for your app, and select Reconciliation from the drop-down menu.
- Set the reconciliation settings as follows:
Note
For details about specific settings, refer to Kochava's Partner Reconciliation Settings documentation.
Parameter | Value | Comment |
---|---|---|
Impression Reconciliation | ||
Device Lookback | 24 hours | Device Lookback determines how far back, from the time of install, to consider engagements for attribution on a standard device match. |
Modeled Lookback | 24 hours | Modeled Lookback determines how far back, from the time of install, to consider engagements for attribution on a Modeled based match. |
IP Lookback | Disabled | IP Lookback determines how far back, from the time of install, to consider engagements for attribution on an IP based match. |
Partial IP Lookback | Disabled | Partial IP Lookback determines how far back, from the time of install, to consider engagements for attribution on an Partial IP based match. |
Device Attribution Behavior | Standard | Device Attribution Behavior determines whether modeled matching will be attempted if a Device ID is present on click. The Standard setting will not attempt modeled attribution if a Device ID is present on click. The Inclusive setting will attempt modeled attribution on all clicks. |
Click Reconciliation | ||
Device Lookback | 30 days | Device Lookback determines how far back, from the time of install, to consider engagements for attribution on a standard device match. |
Modeled Lookback | 30 days | Modeled Lookback determines how far back, from the time of install, to consider engagements for attribution on a Modeled based match. |
IP and Partial IP Lookback | Disabled | IP and Partial IP Lookback determines how far back, from the time of install, to consider engagements for attribution on an IP or Partial IP based match. |
Device Attribution Behavior | Standard | Device Attribution Behavior determines whether modeled matching will be attempted if a Device ID is present on click. The Standard setting will not attempt modeled attribution if a Device ID is present on click. The Inclusive setting will attempt modeled attribution on all clicks. |
Modeled Attribution Tier | Standard | Modeled Attribution Tier determines the Modeled validation configuration. The Standard setting validates based on a combination of IP Address and User Agent. The Full IP Address setting validates based on IP Address regardless of User Agent. The Partial IP Address setting validates based on the first three stanzas of the IP Address. |
Step 5. Setting Up Cost Tracking
- Go to Cost→Configuration.
- Click Add a Media Partner in the top, right corner.
- Search and select Digital Turbine as the Media Partner.
- Enter the required values below:
Parmater | Value |
---|---|
Configuration Name | Recommended value is Digital Turbine. |
Client ID | Value provided by your Digital Turbine representative. |
Client Secret | Value provided by your Digital Turbine representative. |
Product -dtgrowth | 'dtgrowth' Product must be written in lowercase. |
Timezone | Select desired reporting timezone. |
Currency | Select desired reporting currency. |
Add an email(s) | For notifications regarding cost. |
- Switch on the Active toggle.
- Click Save.