Set up Carty DSP

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

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

Before you begin

Requirements

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

Credentials

Domain

  • For help finding your credentials, contact your Carty DSP representative.

Select Carty DSP and your app in Campaign Lab

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

Enable data sharing

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

  1. Enter your Domain.

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

  • install
  • session
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution
  • ad revenue

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 Carty DSP by default.

  • install
  • session
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution
  • ad revenue

Send additional data

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

Ad revenue (from ad views)

Ad revenue sharing lets Carty DSP receive user ad revenue data. This lets Carty DSP use ad revenue data to optimize your user targeting and campaigns.

Growth solution:

This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.

To share ad revenue to Carty DSP, select one or more Ad Revenue Sources.

  • If you leave this field empty, we send ad revenue data from all integrated mediation sources.

Sessions

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

In-app revenue (from in-app purchases)

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

Map events

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

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Carty DSP. This lets you:

  • Set individual events to manage campaign strategies for each platform.
  • Customize data sharing per platform.

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Carty DSP.
  3. Under Partner event, you need to select the Carty DSP event that corresponds to the Adjust event.
    1. For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
      • Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
      • Select Use global mapping to map the same events for all platforms.
    2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
  4. Select Apply.

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

Map all events

If Carty DSP supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Carty DSP will receive in-app event data for all your linked events.

Configure your link and settings

You have the option to set your:

Create your link and share it with Carty DSP

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 Carty DSP.

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

List of all parameters forwarded to Carty DSP

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{language}Device two-character language code
{os_name}Device operating system
{os_version}Operating system version number
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{revenue_usd}Revenue, in US dollars
{user_agent}Incoming raw user agent
{app_id}Store App ID or Google Play Store
{app_name}Name of the app
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{conversion_duration}Time between click and install or reattribution in seconds
{created_at}Activity timestamp
{network_name}Network name, as taken from the tracker
{rejection_reason}Reason for a rejected attribution
{is_redownload}Indicates whether this app activity is the first one recorded after the app was redownloaded (1 = yes