Set up Cusper

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

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

Before you begin

Requirements

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

Select Cusper and your app in Campaign Lab

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

Enable data sharing

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

  1. Turn on Enabled

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

  • install
  • session
  • reattribution
  • event

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

  • install
  • session
  • reattribution
  • event

Send additional data

Choose the amount and type of data that you want to share with Cusper through callbacks. Cusper 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 Cusper:
  • Data from all attribution sources
  • Only data attributed to Cusper

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Cusper 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 Cusper will receive your app’s session activity.

Map parameters

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

Map events

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

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

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

Configure your link and settings

You have the option to set your:

Create your link and share it with Cusper

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 Cusper.

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

List of all parameters forwarded to Cusper

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

PlaceholderInformation
{android_id}Android ID (Android only)
{currency}Original ISO 4217 currency code sent from Adjust SDK
{deeplink}Deeplink URL appended to click URL
{device_name}Device model number
{event}Event token
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{is_reattributed}1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
{language}Device two-character language code
{last_time_spent}Length of user's last session, in seconds
{lifetime_session_count}Number of sessions recorded across entire user lifetime
{match_type}Attribution method
{os_name}Device operating system
{revenue_usd}Revenue, in US dollars
{revenue}Revenue, as sent from Adjust SDK in cents
{session_count}Number of sessions recorded by current Adjust SDK
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{click_time}Attributed click timestamp
{conversion_duration}Time between click and install or reattribution in seconds
{cpu_type}CPU type
{created_at}Activity timestamp
{device_manufacturer}Device manufacturer name
{engagement_time}Engagement timestamp
{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
{last_session_time}Last session timestamp
{last_tracker_name}A reattributed user's previous tracker name
{reattributed_at}Reattribution timestamp
{reinstalled_at}Reinstall timestamp
{tracker_name}Current tracker name
{oaid}OAID device ID