Set up STADIA
STADIA is an analytics network integrated with Adjust. Our integration lets STADIA receive attribution and in-app event data through automated callbacks. Use this data with the partners' tools for analytics and insights.
In this article, learn how to set up measurement with STADIA for your app. This includes activating the integration and choosing what data Adjust can share with STADIA.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to STADIA 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
TABLEID
- For help finding your credentials, contact your STADIA representative.
Select STADIA and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > STADIA. 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 STADIA.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with STADIA. To enable data sharing:
- Enter your TABLEID.
Once you enable data sharing with STADIA, Adjust automatically sends STADIA the following data, by default:
- click
- install
- session
- uninstall
- reinstall
- reattributionReinstall
- reattribution
- event
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 STADIA by default:
- click
- install
- session
- uninstall
- reinstall
- reattributionReinstall
- reattribution
- event
Send additional data
Choose the amount and type of data that you want to share with STADIA through callbacks. STADIA may use this information to optimize performance.
To send additional data, you can review and customize the following:
In-app revenue (from in-app purchases)
Sharing in-app revenue lets STADIA receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means STADIA will receive your app’s session activity.
Map parameters
You usually need to map parameters to share custom data with STADIA.
Map events
Map events that you want to share to the values that STADIA can receive. Data for unmapped events is not shared with STADIA.
Under Map events, follow these steps to choose the in-app events you want to directly send to STADIA.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with STADIA.
- In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to. You might have to map an event to several values.
- Select Apply.
Now STADIA will receive in-app event data for each of your linked events.
Map parameters
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to STADIA. This lets STADIA 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 STADIA, follow these steps.
- Set up partner parameters within the Adjust SDK: iOS, Android
- Check the Parameters data sharing checkbox.
- Map your events.
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.
Enable STADIA for your app
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
Select Enable partner to enable STADIA for your app. Analytics partners don't work with links for campaigns. Once enabled, our integration sends attribution and in-app event data via automated callbacks.
List of all parameters forwarded to STADIA
STADIA requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{android_id} | Android ID (Android only) |
{city} | Device city |
{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_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 |
{deeplink} | Deeplink URL appended to click URL |
{device_name} | Device model number |
{device_type} | Device type |
{fire_adid} | Fire OS advertising identifier |
{gps_adid} | Google Play Store advertising ID |
{idfa_md5_hex} | IDFA hex MD5 hash |
{idfa_upper} | Uppercase IDFA |
{idfa} | ID for advertisers (iOS only) |
{ip_address} | Device IP address |
{isp} | Device internet service provider |
{label} | Value of the Adjust "label" parameter sent on click |
{lifetime_session_count} | Number of sessions recorded across entire user lifetime |
{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 |
{random_user_id} | Random user ID (per device) |
{revenue_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{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 |
{tracking_limited} | 1 if tracking is limited, 0 if not |
{user_agent} | Incoming raw user agent |
{win_adid} | Windows advertising identifier |
{win_udid} | Windows Phone unique device ID |
{activity_kind} | Type of user activity |
{adgroup_name} | Adgroup name, as taken from the tracker |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{campaign_name} | Campaign name, as taken from the tracker |
{click_referer} | Referrer header from click |
{click_time} | Attributed click timestamp |
{connection_type} | Internet connection type |
{conversion_duration} | Time between click and install or reattribution in seconds |
{created_at} | Activity timestamp |
{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_tracker_name} | A reattributed user's previous tracker name |
{network_name} | Network name, as taken from the tracker |
{reattributed_at} | Reattribution timestamp |
{reinstalled_at} | Reinstall timestamp |
{rejection_reason} | Reason for a rejected attribution |
{time_to_reinstall} | Time between latest app uninstall and subsequent reinstall in seconds |
{time_to_uninstall} | Time between app install (or latest reinstall) and subsequent uninstall in seconds |
{tracker_name} | Current tracker name |