Set up Datavisor

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

Before you begin

Requirements

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

Credentials

CLIENT ID

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

Select Datavisor and your app in Campaign Lab

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

Enable data sharing

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

  1. Enter your CLIENT ID.

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

  • click
  • install
  • session
  • reattribution
  • event
  • rejectedInstall

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

  • click
  • install
  • session
  • reattribution
  • event
  • rejectedInstall

Send additional data

Choose the amount and type of data that you want to share with Datavisor through callbacks. Datavisor 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 Datavisor 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 Datavisor will receive your app’s session activity.

Map parameters

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

Map events

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

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

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

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{api_level}API level (Android only)
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{country}Device two-character country code
{deeplink}Deeplink URL appended to click URL
{device_name}Device model number
{device_type}Device type
{environment}Current Adjust SDK environment setting
{gps_adid}Google Play Store advertising ID
{idfa||android_id}IDFA, or Android ID if IDFA is empty
{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
{isp}Device internet service provider
{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
{match_type}Attribution method
{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
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{referrer}Google Play Store referrer (Android only)
{reftag}Random device reference tag
{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
{sdk_version}Adjust SDK version (per app)
{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
{win_adid}Windows advertising identifier
{win_udid}Windows Phone unique device ID
{activity_kind}Type of user activity
{adgroup_name}Adgroup name, as taken from the tracker
{campaign_name}Campaign name, as taken from the tracker
{click_referer}Referrer header from click
{click_time}Attributed click timestamp
{connection_type}Internet connection type
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{engagement_time}Engagement timestamp
{impression_based}1 if impression-based engagement, 0 if not
{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
{is_organic}1 if organic traffic, 0 if non-organic
{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
{reattributed_at}Reattribution timestamp
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{rejection_reason}Reason for a rejected attribution
{store}Target store of click
{tracker_name}Current tracker name
{tracker}6-character Adjust tracker token