Set up SpinApp

SpinApp is an Adjust module partner. Our integration lets SpinApp receive attribution and app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to SpinApp. Then, use our advanced setup instructions to customize what information SpinApp receives.

Basic setup

To turn on Adjust’s integration with SpinApp, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select Add (+icon) next to SpinApp
  4. Enter your SPINAPP APP ID, SECURITY TOKEN and ENDPOINT DOMAIN (contact your SpinApp representative for help finding these)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. SpinApp will receive callbacks for these activities:

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

Advanced setup

Choose which data SpinApp receives from Adjust by customizing your setup.

Forward in-app revenue

Revenue forwarding lets SpinApp receive revenue amounts along with your revenue event data.

To forward in-app revenue to SpinApp, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > SpinApp
  3. Turn on In-App Revenue Forwarding

Now SpinApp will receive the revenue amount for every tracked transaction.

 

Note: Link at least one revenue event to SpinApp before turning on Revenue Forwarding

 

Forward uninstalls / reinstalls

To forward uninstalls and/or reinstalls to SpinApp, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > SpinApp
  3. Turn on Uninstall / Reinstall Forwarding

Now SpinApp will receive all of your app's uninstall and/or reinstall data

 

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to SpinApp, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > SpinApp
  3. Turn on Session Forwarding

Now SpinApp will receive your app’s session activity.

 

Forward custom data

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to SpinApp.

Note: Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To forward partner parameters to SpinApp, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > SpinApp
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding SpinApp name.
  7. Select Save

Now SpinApp will receive custom event details for each of your linked events.

 

Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.

 

Forward app events

Event linking lets SpinApp receive app event data. You can link every app event in Adjust to a preset SpinApp name or a custom event name.

To forward app events to SpinApp, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup >SpinApp > Event Linking
  3. Find the event you want to link and update the field with a SpinApp event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now SpinApp will receive app event data for each of your linked events.

List of all parameters forwarded to SpinApp

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

Placeholder Information
{activity_kind} Type of user activity
{adgroup_name} Adgroup name, as taken from the tracker
{adid} Adjust device ID (all platforms)
{app_id} Store App ID or Google Play Store
{app_version} App version number (Android), build
{attribution_updated_at} Updated attribution timestamp
{campaign_name} Campaign name, as taken from the tracker
{city} Device city
{click_attribution_window} Attribution window settings for device matching (hours)
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{country_subdivision} Device subdivision of country, e.g., state
{country} Device two
{created_at} Activity timestamp
{currency} Original ISO 4217 currency code sent from Adjust SDK
{deeplink} Deeplink URL appended to click URL
{device_name} Device model number
{engagement_time} Engagement timestamp
{environment} Current Adjust SDK environment setting
{first_tracker} 6
{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)
{impression_based} 1 if impression
{impression_time} Attributed impression timestamp
{inactive_user_definition} Inactivity period required for reattribution (hours)
{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
{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
{last_session_time} Last session timestamp
{last_time_spent} Length of user's last session, in seconds
{last_tracker_name} A reattributed user's previous tracker name
{last_tracker} 6
{lifetime_session_count} Number of sessions recorded across entire user lifetime
{match_type} Attribution method
{mcc} Mobile country code: three
{mnc} Mobile network code: two
{network_name} Network name, as taken from the tracker
{os_name} Device operating system
{os_version} Operating system version number
{outdated_tracker} 6
{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
{reattributed_at} Reattribution timestamp
{reattribution_attribution_window} Attribution window settings for reattribution (hours)
{referral_time} User landed on app Play Store page timestamp (Android and Google Play Store only)
{referrer} Google Play Store referrer (Android only)
{reftag} Random device reference tag
{reinstalled_at} Reinstall timestamp
{rejection_reason} Reason for a rejected attribution
{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
{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
{timezone} Device time zone
{tracker} 6
{tracking_enabled} 1 if tracking is enabled, 0 if not
{uninstalled_at} Uninstall timestamp (estimation based on last session time)
{user_agent} Incoming raw user agent