Set up Rockerbox
Rockerbox is an analytics network integrated with Adjust. Our integration lets Rockerbox 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 Rockerbox for your app. This includes activating the integration and choosing what data Adjust can share with Rockerbox.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Rockerbox 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
Advertiser ID
- For help finding your credentials, contact your Rockerbox representative.
Select Rockerbox and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Rockerbox. 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 Rockerbox.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Rockerbox. To enable data sharing:
- Enter your Advertiser ID.
Once you enable data sharing with Rockerbox, Adjust automatically sends Rockerbox the following data, by default:
- install
- session
- 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 Rockerbox by default:
- install
- session
- event
Send additional data
Choose the amount and type of data that you want to share with Rockerbox through callbacks. Rockerbox 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 Rockerbox 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 Rockerbox will receive your app’s session activity.
Map parameters
You usually need to map parameters to share custom data with Rockerbox.
Map events
Map events that you want to share to the values that Rockerbox can receive. Data for unmapped events is not shared with Rockerbox.
Under Map events, follow these steps to choose the in-app events you want to directly send to Rockerbox.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Rockerbox.
- 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 Rockerbox 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 Rockerbox. This lets Rockerbox 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 Rockerbox, 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 Rockerbox 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 Rockerbox 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 Rockerbox
Rockerbox 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 |
{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 |
{environment} | Current Adjust SDK environment setting |
{event_name} | Event name, as set in the Dashboard |
{fire_adid} | Fire OS advertising identifier |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{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 |
{language} | Device two-character language code |
{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 |
{postal_code} | Device postal code of IP address |
{publisher_parameters} | Custom publisher parameters collected by the Adjust SDK (never displayed in Adjust Dashboard) |
{random_user_id} | Random user ID (per device) |
{random} | Random number (unique per callback) |
{region} | Device region code |
{reporting_currency} | Dashboard reporting ISO 4217 currency code |
{reporting_revenue} | Revenue, as reported in the Adjust Dashboard, in whole currency units |
{revenue_usd} | Revenue, in US dollars |
{revenue} | Revenue, as sent from Adjust SDK in 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 |
{user_agent} | Incoming raw user agent |
{win_adid} | Windows advertising identifier |
{win_udid} | Windows Phone unique device ID |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{app_version} | App version number (Android), build-version-number for the bundle (iOS) |
{attribution_updated_at} | Updated attribution timestamp |
{click_time} | Attributed click timestamp |
{connection_type} | Internet connection type |
{conversion_duration} | Time between click and install or reattribution in seconds |
{cpu_type} | CPU type |
{created_at_milli} | Activity timestamp with millisecond placeholders |
{device_manufacturer} | Device manufacturer name |
{engagement_time} | Engagement timestamp |
{hardware_name} | Hardware name |
{impression_based} | 1 if impression-based engagement, 0 if not |
{impression_time} | Attributed impression timestamp |
{install_finish_time} | App download completion 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 |
{network_name} | Network name, as taken from the tracker |
{network_type} | Network type |
{reattributed_at} | Reattribution timestamp |
{referral_time} | User landed on app Play Store page timestamp (Android and Google Play Store only) |
{store} | Target store of click |
{ad_impressions_count} | Number of mobile ads served to end users |
{ad_revenue_network} | Ad network that displayed the ad |
{ad_revenue_unit} | Ad unit that generated the revenue |
{ad_revenue_placement} | User placement, as defined on the platform |
{oaid} | OAID device ID |
{is_s2s} | 1 if server to server engagement, 0 if not |
{is_s2s_engagement_based} | 1 if attributed to a server to server engagement, 0 if not |
{proxy_ip_address} | IP address of user's proxy |
{ad_mediation_platform} | Mediation platform name |
{ad_revenue_payload} | Impression-level revenue data (ILRD) as a JSON |