Set up Adpacker

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

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

Before you begin

Requirements

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

Select Adpacker and your app in Campaign Lab

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

Enable data sharing

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

  1. Turn on Enabled

Once you enable data sharing with Adpacker, Adjust automatically sends Adpacker 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 Adpacker by default.

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

Send additional data

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

Sessions

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

In-app revenue (from in-app purchases)

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

Map parameters

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

Map events

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

Map individual events

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

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

Map all events

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

Now Adpacker will receive in-app event data for all 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 Adpacker. This lets Adpacker 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 Adpacker, 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 Adpacker

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

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

List of all parameters forwarded to Adpacker

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

PlaceholderInformation
{city}Device city
{deeplink}Deeplink URL appended to click URL
{device_name}Device model number
{device_type}Device type
{event_name}Event name, as set in the Dashboard
{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
{isp}Device internet service provider
{language}Device two-character language code
{mcc}Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier.
{mnc}Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier.
{os_name}Device operating system
{os_version}Operating system version number
{partner_parameters}Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{random_user_id}Random user ID (per device)
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{region}Device region code
{reporting_currency}Dashboard reporting ISO 4217 currency code
{reporting_revenue}Revenue, as reported in the Adjust Dashboard, in whole currency units
{sdk_version}Adjust SDK version (per app)
{user_agent}Incoming raw user agent
{app_name}Name of the app
{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
{engagement_time}Engagement timestamp
{impression_time}Attributed impression timestamp
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{reattributed_at}Reattribution timestamp
{rejection_reason}Reason for a rejected attribution
{store}Target store of click