Set up Remoby

Remoby is an ad network integrated with Adjust. Our integration lets Remoby receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with Remoby for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Remoby.

Before you begin


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

Select Remoby and your app in Campaign Lab

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

Enable data sharing

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

  1. Turn on Enabled

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

  • install
  • session
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution

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 Remoby by default.

  • install
  • session
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution

Send additional data

Choose the amount and type of data that you want to share with Remoby through callbacks. Remoby may use this information to optimize performance.

  1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Remoby:
  • Data from all attribution sources
  • Only data attributed to Remoby

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Remoby receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.


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

Map events

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

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Remoby.
  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 Remoby will receive in-app event data for each of your linked events.

Configure your link and settings

You have the option to set your:

Create your link and share it with Remoby

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
  • Link structure parameters
  • User destinations
  • Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Remoby.

Once you’ve created your link, share it with Remoby for placement in campaigns.

List of all parameters forwarded to Remoby

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

{event_name}Event name, as set in the Dashboard
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{revenue}Revenue, as sent from Adjust SDK in cents
{session_count}Number of sessions recorded by current Adjust SDK
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{conversion_duration}Time between click and install or reattribution in seconds
{installed_at}Install (i.e., first app open) timestamp
{last_session_time}Last session timestamp
{network_name}Network name, as taken from the tracker
{reattributed_at}Reattribution timestamp
{rejection_reason}Reason for a rejected attribution