Set up Appier

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

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

Before you begin

Requirements

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

Select Appier and your app in Campaign Lab

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

Enable data sharing

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

  1. Turn on Enabled

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

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

  • install
  • session
  • uninstall
  • reinstall
  • reattribution
  • event

Send additional data

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

In-app revenue (from in-app purchases)

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

Ad revenue (from ad views)

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

Growth solution:

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

To share ad revenue to Appier, 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 Appier will receive your app’s session activity.

Map parameters

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

Map events

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

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

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

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

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

Partner specific setup instructions

Appier FMP only receives data on filtered Facebook traffic. This is designed so that you can manage your Appier MFP Facebook traffic separately from other Facebook campaigns that you might be running.

Only Facebook campaigns that are named to include the keyword appier will be transmitted to Appier FMP. That is, you must include the keyword in the campaign name of each campaign that you want to manage with Appier FMP. Campaigns that do not include the keyword will not be transmitted to Appier FMP.

List of all parameters forwarded to Appier

Appier 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
{deeplink}Deeplink URL appended to click URL
{event_name}Event name, as set in the Dashboard
{idfa||gps_adid}IDFA, or GPS ADID if IDFA is empty
{idfv}Uppercase iOS ID for vendors
{inactive_user_definition}Inactivity period required for reattribution (hours)
{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
{label}Value of the Adjust "label" parameter sent on click
{match_type}Attribution method
{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.
{nonce}Random lowercase alphanumeric string (unique per callback)
{os_name}Device operating system
{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)
{revenue}Revenue, as sent from Adjust SDK in cents
{sdk_version}Adjust SDK version (per app)
{timezone}Device time zone
{tracking_limited}1 if tracking is limited, 0 if not
{activity_kind}Type of user activity
{adgroup_name}Adgroup name, as taken from the tracker
{app_id}Store App ID or Google Play Store
{app_version_short}App version number (Android), release-version-number for the bundle (iOS)
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{click_time}Attributed click timestamp
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{device_manufacturer}Device manufacturer name
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression 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
{is_organic}1 if organic traffic, 0 if non-organic
{reattributed_at}Reattribution timestamp
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{rejection_reason}Reason for a rejected attribution
{time_to_reinstall}Time between latest app uninstall and subsequent reinstall in seconds
{time_to_uninstall}Time between app install (or latest reinstall) and subsequent uninstall in seconds
{tracker_name}Current tracker name
{is_s2s}1 if server to server engagement, 0 if not
{is_s2s_engagement_based}1 if attributed to a server to server engagement, 0 if not