Set up Appreciate DSP by Digital Turbine
Appreciate DSP by Digital Turbine is an ad network integrated with Adjust. Our integration lets Appreciate DSP by Digital Turbine receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Appreciate DSP by Digital Turbine for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Appreciate DSP by Digital Turbine.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Appreciate DSP by Digital Turbine parameters. Follow the guides linked below to use this feature.
iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona
Credentials
APPRECIATE YID
- For help finding your credentials, contact your Appreciate DSP by Digital Turbine representative.
Select Appreciate DSP by Digital Turbine and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Appreciate DSP by Digital Turbine. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Appreciate DSP by Digital Turbine.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Appreciate DSP by Digital Turbine. To enable data sharing:
- Enter your APPRECIATE YID.
Once you enable data sharing with Appreciate DSP by Digital Turbine, Adjust automatically sends Appreciate DSP by Digital Turbine the following data, by default:
- install
- session
- event
- rejectedInstall
Set your data sharing options
If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- Set the same data sharing settings for multiple platforms by selecting Use global settings.
Now, under What will be shared by default?, review the activities that Adjust shares with Appreciate DSP by Digital Turbine by default.
- install
- session
- event
- rejectedInstall
Send additional data
Choose the amount and type of data that you want to share with Appreciate DSP by Digital Turbine through callbacks. Appreciate DSP by Digital Turbine may use this information to optimize performance.
- Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Appreciate DSP by Digital Turbine:
- Data from all attribution sources
- Only data attributed to Appreciate DSP by Digital Turbine
Ad spend
Ad spend sharing lets Appreciate DSP by Digital Turbine receive user ad spend data. This lets Appreciate DSP by Digital Turbine use ad spend data to optimize your campaigns.
Adjust sends Appreciate DSP by Digital Turbine the ad spend data received through callbacks only. This data comes from the following solutions that you’ve set up, as applicable for Appreciate DSP by Digital Turbine:
If Appreciate DSP by Digital Turbine wants complete ad spend data, then you can set up Ad spend third-party storage exports for Appreciate DSP by Digital Turbine.
This feature is available with Adjust’s SpendWorks package. To purchase our SpendWorks package, contact your sales representative.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Appreciate DSP by Digital Turbine will receive your app’s session activity.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Appreciate DSP by Digital Turbine receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Map events
Map events that you want to share to the values that Appreciate DSP by Digital Turbine can receive. Data for unmapped events is not shared with Appreciate DSP by Digital Turbine.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Appreciate DSP by Digital Turbine. This lets you:
- Set individual events to manage campaign strategies for each platform.
- Customize data sharing per platform.
Under Map events, follow these steps to choose the in-app events you want to directly send to Appreciate DSP by Digital Turbine.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Appreciate DSP by Digital Turbine.
- Under Partner event, you need to select the Appreciate DSP by Digital Turbine event that corresponds to the Adjust event.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
- Select Use global mapping to map the same events for all platforms.
- In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Apply.
Now Appreciate DSP by Digital Turbine will receive in-app event data for each of your linked events.
Map all events
If Appreciate DSP by Digital Turbine supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Appreciate DSP by Digital Turbine will receive in-app event data for all your linked events.
Map parameters
You usually need to map parameters to share custom data with Appreciate DSP by Digital Turbine.
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Appreciate DSP by Digital Turbine. This lets Appreciate DSP by Digital Turbine receive custom event details for each of your linked events.
Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.
To share partner parameters to Appreciate DSP by Digital Turbine, follow these steps.
- Set up partner parameters within the Adjust SDK.
- Check Before you begin for all SDK development platform links.
- Under Set your data sharing options, select Parameters.
- Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
- Select Map parameter.
- In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
- In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.
Configure your link and settings
You have the option to set your:
Create your link and share it with Appreciate DSP by Digital Turbine
In the Setup review screen, you can review your choices. You can also go back and make changes to:
- Your selected app
- Data sharing options
- Link structure parameters
- User destinations
- Attribution settings
Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Appreciate DSP by Digital Turbine.
Once you’ve created your link, share it with Appreciate DSP by Digital Turbine for placement in campaigns.
Partner specific setup instructions
Appreciate DSP receives detailed campaign level information for campaigns data that is attributed to Appreciate DSP only.
List of all parameters forwarded to Appreciate DSP by Digital Turbine
Appreciate DSP by Digital Turbine requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{api_level} | API level (Android only) |
{city} | Device city |
{click_attribution_window} | Attribution window settings for device matching (hours) |
{cost_amount} | Cost of the user engagement (available for ad spend tracking only) |
{cost_currency} | ISO 4217 currency code of the cost data (available for ad spend tracking only) |
{cost_id_md5} | An MD5 hash of the cost ID provided by a network using our ad spend API (available for ad spend tracking only) |
{cost_type} | The campaign pricing model (available for ad spend tracking only) |
{country_subdivision} | Device subdivision of country, e.g., state |
{country} | Device two-character country code |
{currency} | Original ISO 4217 currency code sent from Adjust SDK |
{deeplink} | Deeplink URL appended to click URL |
{device_name} | Device model number |
{device_type} | Device type |
{idfa||gps_adid} | IDFA, or GPS ADID if IDFA is empty |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{ip_address} | Device IP address |
{is_reattributed} | 1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed |
{isp} | Device internet service provider |
{label} | Value of the Adjust "label" parameter sent on click |
{language} | Device two-character language code |
{last_time_spent} | Length of user's last session, in seconds |
{lifetime_session_count} | Number of sessions recorded across entire user lifetime |
{match_type} | Attribution method |
{mcc} | Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier. |
{mnc} | Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier. |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{partner_parameters} | Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks |
{postal_code} | Device postal code of IP address |
{reattribution_attribution_window} | Attribution window settings for reattribution (hours) |
{reftag} | Random device reference tag |
{region} | Device region code |
{revenue_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{revenue_usd_cents} | Revenue, in US cents |
{sdk_version} | Adjust SDK version (per app) |
{session_count} | Number of sessions recorded by current Adjust SDK |
{time_spent} | Length of user's current session, in seconds |
{timezone} | Device time zone |
{tracking_limited} | 1 if tracking is limited, 0 if not |
{user_agent} | Incoming raw user agent |
{win_adid} | Windows advertising identifier |
{activity_kind} | Type of user activity |
{adgroup_name} | Adgroup name, as taken from the tracker |
{app_id} | Store App ID or Google Play Store |
{campaign_name} | Campaign name, as taken from the tracker |
{click_time} | Attributed click timestamp |
{connection_type} | Internet connection type |
{conversion_duration} | Time between click and install or reattribution in seconds |
{creative_name} | Creative name, as taken from the tracker |
{engagement_time} | Engagement timestamp |
{impression_based} | 1 if impression-based engagement, 0 if not |
{impression_time} | Attributed impression timestamp |
{installed_at} | Install (i.e., first app open) timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{last_session_time} | Last session timestamp |
{last_tracker} | 6-character Adjust tracker token of a reattributed user's previous tracker |
{network_name} | Network name, as taken from the tracker |
{reattributed_at} | Reattribution timestamp |
{rejection_reason} | Reason for a rejected attribution |
{tracker} | 6-character Adjust tracker token |