Languages 

Set up Media Pi

Media Pi is a network and Adjust module partner. Our integration lets Media Pi receive attribution and in-app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Media Pi. Then, use our advanced setup instructions to customize what information Media Pi receives.

Advanced setup

Choose which data Media Pi receives from Adjust by customizing your setup.

Forward clicks

Adjust does not automatically send click callbacks due to the high volume of clicks.

To forward click data to Media Pi, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Media Pi
  3. Turn on Send Clicks

Now Media Pi will receive all of your app’s click data.

Forward in-app revenue

In-app revenue forwarding lets Media Pi receive revenue amounts along with your revenue event data.

To forward in-app revenue to Media Pi, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Media Pi
  3. Turn on In-App Revenue Forwarding

Now Media Pi will receive the revenue amount for every tracked transaction.

Note: Link at least one [revenue event] to Media Pi before turning on In-App Revenue Forwarding.

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to Media Pi, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Media Pi
  3. Turn on Session Forwarding

Now Media Pi will receive your app’s session activity.

Forward custom data

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Media Pi.

Note: Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To forward partner parameters to Media Pi, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > Media Pi
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding Media Pi name.
  7. Select Save

Now Media Pi will receive custom event details for each of your linked events.

Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.

Forward in-app events

Event linking lets Media Pi receive in-app event data. You can link every in-app event in Adjust to a preset Media Pi name or a custom event name.

To forward in-app events to Media Pi, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Media Pi > Event Linking
  3. Find the event you want to link and update the field with a Media Pi event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now Media Pi will receive in-app event data for each of your linked events.

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