Set up Adikteev Churn Prediction

Adikteev Churn Prediction is an analytics network integrated with Adjust. Our integration lets Adikteev Churn Prediction 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 Adikteev Churn Prediction for your app. This includes activating the integration and choosing what data Adjust can share with Adikteev Churn Prediction.

Before you begin

Requirements

iOS / Android / Windows / Unity / React Native / Flutter / Adobe Air / Cordova / Marmalade / Xamarin / Cocos2d-x / Titanium / Corona

Select Adikteev Churn Prediction and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > Adikteev Churn Prediction. Select Next to move to the next screen.
  3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Adikteev Churn Prediction.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with Adikteev Churn Prediction. To enable data sharing:

  1. Turn on Enabled

Once you enable data sharing with Adikteev Churn Prediction, Adjust automatically sends Adikteev Churn Prediction the following data, by default:

  • install
  • session
  • reattribution
  • event
  • ad revenue

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

  1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
  2. 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 Adikteev Churn Prediction by default:

  • install
  • session
  • reattribution
  • event
  • ad revenue

Send additional data

Choose the amount and type of data that you want to share with Adikteev Churn Prediction through callbacks. Adikteev Churn Prediction 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 Adikteev Churn Prediction receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.

Ad revenue (from ad views)

Ad revenue sharing lets Adikteev Churn Prediction receive user ad revenue data. This lets Adikteev Churn Prediction use ad revenue data to optimize your user targeting and campaigns.

Growth solution:

This feature is available with Adjust’s RevWorks package. To purchase our RevWorks package, contact your sales representative.

To share ad revenue to Adikteev Churn Prediction, 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 Adikteev Churn Prediction will receive your app’s session activity.

Map parameters

You usually need to map parameters to share custom data with Adikteev Churn Prediction.

Map events

Map events that you want to share to the values that Adikteev Churn Prediction can receive. Data for unmapped events is not shared with Adikteev Churn Prediction.

Under Map events, follow these steps to choose the in-app events you want to directly send to Adikteev Churn Prediction.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Adikteev Churn Prediction.
  3. 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.
  4. Select Apply.

Now Adikteev Churn Prediction 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 Adikteev Churn Prediction. This lets Adikteev Churn Prediction 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 Adikteev Churn Prediction, follow these steps.

  1. Set up partner parameters within the Adjust SDK: iOS, Android
  2. Check the Parameters data sharing checkbox.
  3. Map your events.
Note:

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 Adikteev Churn Prediction 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 Adikteev Churn Prediction 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 Adikteev Churn Prediction

Adikteev Churn Prediction requires Adjust to send the following parameters (data points) with your callbacks:

PlaceholderInformation
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{country}Device two-character country code
{device_name}Device model number
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{impression_attribution_window}Attribution window settings for impression matching (hours)
{inactive_user_definition}Inactivity period required for reattribution (hours)
{isp}Device internet service provider
{language}Device two-character language code
{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)
{revenue_usd}Revenue, in US dollars
{app_id}Store App ID or Google Play Store
{app_version_short}App version number (Android), release-version-number for the bundle (iOS)
{connection_type}Internet connection type
{device_manufacturer}Device manufacturer name
{engagement_time}Engagement timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{network_type}Network type