Set up RevX

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

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

Basic setup

To turn on Adjust’s integration with RevX, 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 RevX
  4. Enter your PIXEL ID, CLIENT ID and BUSINESS VERTICAL (contact your RevX representative for help finding these)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to RevX to launch your campaign.

RevX will receive callbacks for these activities:

  • install
  • rejected install
  • session
  • event
  • reattribution
  • rejected reattribution

Advanced setup

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

Forward in-app revenue

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

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

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

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

 

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

 

Forward sessions

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

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

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

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

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

Now RevX 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 RevX receive app event data. You can link every app event in Adjust to a preset RevX name or a custom event name.

To forward app events to RevX, follow these steps.

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

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

List of all parameters forwarded to RevX

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

Placeholder Information
{activity_kind} Type of user activity
{android_id} Android ID (Android only)
{click_attribution_window} Attribution window settings for device matching (hours)
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{created_at} Activity timestamp
{idfa||gps_adid} IDFA, or GPS ADID if IDFA is empty
{impression_attribution_window} Attribution window settings for impression matching (hours)
{impression_based} 1 if impression
{inactive_user_definition} Inactivity period required for reattribution (hours)
{installed_at} Install (i.e., first app open) timestamp
{is_organic} 1 if organic traffic, 0 if non
{last_session_time} Last session timestamp
{os_name} Device operating system
{reattributed_at} Reattribution timestamp
{reattribution_attribution_window} Attribution window settings for reattribution (hours)
{rejection_reason} Reason for a rejected attribution