Set up BidSlash

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

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

Before you begin

Requirements

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

Credentials

API Key

  • For help finding your credentials, contact your BidSlash representative.

Select BidSlash and your app in Campaign Lab

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

Enable data sharing

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

  1. Enter your API Key.

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

  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • 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 BidSlash by default.

  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution

Send additional data

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

Sessions

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

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets BidSlash receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets BidSlash 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 BidSlash can receive. Data for unmapped events is not shared with BidSlash.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with BidSlash. 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 BidSlash.

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

Map all events

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

Now BidSlash 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 BidSlash

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

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

List of all parameters forwarded to BidSlash

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

PlaceholderInformation
{city}Device city
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{device_type}Device type
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{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
{match_type}Attribution method
{nonce}Random lowercase alphanumeric string (unique per callback)
{os_version}Operating system version number
{random}Random number (unique per callback)
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{revenue_usd}Revenue, in US dollars
{session_count}Number of sessions recorded by current Adjust SDK
{time_spent}Length of user's current session, in seconds
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{app_name}Name of the app
{conversion_duration}Time between click and install or reattribution in seconds
{created_at}Activity timestamp
{impression_based}1 if impression-based engagement, 0 if not
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic