Set up Media Pi

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

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

Before you begin

Requirements

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

Select Media Pi and your app in Campaign Lab

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

Enable data sharing

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

  1. Turn on Enabled

Adjust does not automatically send click callbacks due to the high volume of clicks. To send clicks to Media Pi, enable the Send clicks toggle.

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

  • click
  • install
  • session
  • reattribution
  • event
  • 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 Media Pi by default.

  • click
  • install
  • session
  • reattribution
  • event
  • rejectedReattribution

Send additional data

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

In-app revenue (from in-app purchases)

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

Map parameters

You usually need to map parameters to share custom data with Media Pi.

Map events

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

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

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

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 Media Pi.

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

List of all parameters forwarded to Media Pi

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{android_id}Android ID (Android only)
{api_level}API level (Android only)
{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
{device_name}Device model number
{device_type}Device type
{event}Event token
{fire_adid}Fire OS advertising identifier
{gps_adid}Google Play Store advertising ID
{impression_attribution_window}Attribution window settings for impression matching (hours)
{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
{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
{mac_md5}Uppercase MAC MD5 hash
{mac_sha1}Uppercase MAC SHA-1 hash
{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
{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
{postal_code}Device postal code of IP address
{random}Random number (unique per callback)
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{referrer}Google Play Store referrer (Android only)
{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
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{tracking_enabled}1 if tracking is enabled, 0 if not
{tracking_limited}1 if tracking is limited, 0 if not
{user_agent}Incoming raw user agent
{win_adid}Windows advertising identifier
{win_hwid}Windows Store hardware ID
{win_naid}Windows Store network adapter ID
{win_udid}Windows Phone unique device ID
{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_name}Name of the app
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{click_referer}Referrer header from click
{click_time}Attributed click timestamp
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{device_manufacturer}Device manufacturer name
{engagement_time}Engagement timestamp
{fingerprint_attribution_window}Attribution window settings for device fingerprinting (hours)
{hardware_name}Hardware name
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{last_session_time}Last session timestamp
{network_name}Network name, as taken from the tracker
{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
{store}Target store of click
{tracker_name}Current tracker name