Set up SpinApp

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

Before you begin

Requirements

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

Credentials

SPINAPP APP ID, SECURITY TOKEN, and ENDPOINT DOMAIN

  • For help finding your credentials, contact your SpinApp representative.

Select SpinApp and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > SpinApp. 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 SpinApp.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with SpinApp. To enable data sharing:

  1. Enter your SPINAPP APP ID, SECURITY TOKEN, and ENDPOINT DOMAIN.

Once you enable data sharing with SpinApp, Adjust automatically sends SpinApp the following data, by default:

  • 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:

  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 SpinApp by default:

  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • reattribution
  • event

Send additional data

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

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets SpinApp receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.

Sessions

Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means SpinApp will receive your app’s session activity.

Map parameters

You usually need to map parameters to share custom data with SpinApp.

Map events

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

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with SpinApp.
  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 SpinApp 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 SpinApp. This lets SpinApp 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 SpinApp, 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 SpinApp 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 SpinApp 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 SpinApp

SpinApp requires Adjust to send the following parameters (data points) with your callbacks:

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{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
{environment}Current Adjust SDK environment setting
{gps_adid}Google Play Store advertising ID
{iad_conversion_type}Download status: first or subsequent app download
{iad_creative_set_id}Apple Search Ads creative set ID
{iad_creative_set_name}Apple Search Ads creative set name
{iad_keyword_matchtype}Apple Search keyword matchtype
{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)
{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
{label}Value of the Adjust "label" parameter sent on click
{language}Device two-character language code
{last_time_spent}Length of user's last session, in seconds
{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
{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)
{referrer}Google Play Store referrer (Android only)
{reftag}Random device reference tag
{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
{timezone}Device time zone
{tracking_enabled}1 if tracking is enabled, 0 if not
{user_agent}Incoming raw user agent
{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_version}App version number (Android), build-version-number for the bundle (iOS)
{attribution_updated_at}Updated attribution timestamp
{campaign_name}Campaign name, as taken from the tracker
{click_time}Attributed click timestamp
{connection_type}Internet connection type
{created_at}Activity timestamp
{engagement_time}Engagement timestamp
{first_tracker}6-character Adjust tracker token for a user's first attribution source
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{install_begin_time}App download began timestamp (Android and Google Play Store only)
{install_finish_time}App download completion timestamp
{installed_at}Install (i.e., first app open) timestamp
{last_session_time}Last session timestamp
{last_tracker_name}A reattributed user's previous tracker name
{last_tracker}6-character Adjust tracker token of a reattributed user's previous tracker
{network_name}Network name, as taken from the tracker
{outdated_tracker}6-character Adjust tracker token for outdated trackers in updated attributions
{reattributed_at}Reattribution timestamp
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{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}6-character Adjust tracker token
{uninstalled_at}Uninstall timestamp (estimation based on last session time)