Set up StackAdapt
StackAdapt is an ad network integrated with Adjust. Our integration lets StackAdapt receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with StackAdapt for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with StackAdapt.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to StackAdapt 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
Select StackAdapt and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > StackAdapt. 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 StackAdapt.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with StackAdapt. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with StackAdapt, Adjust automatically sends StackAdapt the following data, by default:
- install
- session
- reattribution
- event
- rejectedInstall
- rejectedReattribution
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 StackAdapt by default.
- install
- session
- reattribution
- event
- rejectedInstall
- rejectedReattribution
Send additional data
Choose the amount and type of data that you want to share with StackAdapt through callbacks. StackAdapt 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 StackAdapt:
- Data from all attribution sources
- Only data attributed to StackAdapt
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means StackAdapt will receive your app’s session activity.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets StackAdapt receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Configure your link and settings
You have the option to set your:
Create your link and share it with StackAdapt
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 StackAdapt.
Once you’ve created your link, share it with StackAdapt for placement in campaigns.
List of all parameters forwarded to StackAdapt
StackAdapt requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{android_id} | Android ID (Android only) |
{event} | Event token |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{ip_address} | Device IP address |
{lifetime_session_count} | Number of sessions recorded across entire user lifetime |
{revenue_usd} | Revenue, in US dollars |
{session_count} | Number of sessions recorded by current Adjust SDK |
{user_agent} | Incoming raw user agent |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{conversion_duration} | Time between click and install or reattribution in seconds |
{impression_based} | 1 if impression-based engagement, 0 if not |
{installed_at} | Install (i.e., first app open) timestamp |
{last_session_time} | Last session timestamp |
{reattributed_at} | Reattribution timestamp |
{rejection_reason} | Reason for a rejected attribution |
{oaid} | OAID device ID |