Set up Zeotap
Zeotap is an analytics partner integrated with Adjust. Our integration lets Zeotap receive data measured in Adjust through automated callbacks. Use this data with the partners' tools for analytics and insights.
In this article, learn how to set up measurement with Zeotap for your app. This includes activating the integration and choosing what data Adjust can share with Zeotap.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Zeotap 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
Write Key(s)
- For help finding your credentials, contact your Zeotap representative.
Select Zeotap and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Zeotap. 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 Zeotap.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Zeotap. To enable data sharing:
- Enter your Write Key(s).
Once you enable data sharing with Zeotap, Adjust automatically sends Zeotap the following data, by default:
- install
- reattribution
- 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 Zeotap by default:
- install
- reattribution
- rejectedInstall
- rejectedReattribution
Send additional data
Choose the amount and type of data that you want to share with Zeotap through callbacks. Zeotap may use this information to optimize performance.
To send additional data, you can review and customize the following:
Ad revenue (from ad views)
Ad revenue sharing lets Zeotap receive user ad revenue data. This lets Zeotap use ad revenue data to optimize your user targeting and campaigns.
This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.
To share ad revenue to Zeotap, select one or more Ad Revenue Sources.
- If you leave this field empty, we send ad revenue data from all integrated mediation sources.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Zeotap will receive your app’s session activity.
Uninstalls or reinstalls
Sharing uninstalls or reinstalls lets Zeotap receive your app’s uninstall and/or reinstall data measured by Adjust.
For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Zeotap receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Enable Zeotap 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 Zeotap 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.
Partner specific setup instructions
Additional information about the activation fields
- Region: Select either EU or US, depending on the region where your Zeotap account is hosted.
- Default Country Code: Select the country code to use when a user's country cannot be determined. For a complete list of supported country names and codes, see our Help Center article.
- Write Key: Enter the Write Key provided by Zeotap to enable the module and activate the default install and reattribution callbacks. To share additional events with Zeotap, you must also provide the corresponding event-specific Write Key. For example, to send session data, enter a Session Write Key.
List of all parameters forwarded to Zeotap
Zeotap 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 |
{device_name} | Device model number |
{device_type} | Device type |
{environment} | Current Adjust SDK environment setting |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{ip_address} | Device IP address |
{isp} | Device internet service provider |
{language} | Device two-character language code |
{match_type} | Attribution method |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{postal_code} | Device postal code of IP address |
{region} | Device region code |
{sdk_version} | Adjust SDK version (per app) |
{search_term} | Google organic search term |
{tracking_enabled} | 1 if tracking is enabled, 0 if not |
{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 |
{app_version_short} | App version number (Android), release-version-number for the bundle (iOS) |
{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 |
{created_at_milli} | Activity timestamp with millisecond placeholders |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{device_manufacturer} | Device manufacturer name |
{engagement_time} | Engagement timestamp |
{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 |
{network_type} | Network type |
{reattributed_at} | Reattribution timestamp |
{reinstalled_at} | Reinstall timestamp |
{store} | Target store of click |
{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 |
{uninstalled_at} | Uninstall timestamp (estimation based on last session time) |
{proxy_ip_address} | IP address of user's proxy |
{device_model} | Device model number |
{platform} | Indicates if the activity happened on mobile or web |
{store_type} | Store type |