Languages 

Set up Datavisor

Datavisor is a network and Adjust module partner. Our integration lets Datavisor receive attribution and in-app event data through automated callbacks.

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

Basic setup

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

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select the add (+) icon next to Datavisor
  4. Enter your CLIENT ID (for help finding this, contact your Datavisor representative)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

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

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

Advanced setup

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

Forward in-app revenue

In-app revenue forwarding lets Datavisor receive revenue amounts along with your revenue event data.

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

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

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

Note: Link at least one [revenue event] to Datavisor before turning on In-App Revenue Forwarding.

Forward sessions

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

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

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

Now Datavisor 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 Datavisor.

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 Datavisor, 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 > Datavisor
  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 Datavisor name.
  7. Select Save

Now Datavisor 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 in-app events

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

To forward in-app events to Datavisor, follow these steps.

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

Now Datavisor will receive in-app event data for each of your linked events.

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