Set up Appier FMP
Appier FMP is an Adjust module partner. Our integration lets Appier FMP receive attribution and app event data for the following self-attributing networks:
Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Appier FMP. Then, use our advanced setup instructions to customize what information Appier FMP receives.
Advanced setup
Choose which data Appier FMP receives from Adjust by customizing your setup.
Forward in-app revenue
In-app revenue forwarding lets Appier FMP receive revenue amounts along with your revenue event data.
To forward in-app revenue to Appier FMP, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Appier FMP
- Turn on In-App Revenue Forwarding
Now Appier FMP will receive the revenue amount for every tracked transaction.
Note: Link at least one revenue event to Appier FMP before turning on In-App Revenue Forwarding.
Forward ad revenue
Ad revenue forwarding lets Appier FMP receive user ad revenue data. This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.
To forward ad revenue to Appier FMP, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Appier FMP
- Turn on Ad Revenue Forwarding
- Optional: Select one or more Ad Revenue Sources.
- If you leave this field empty, we send Ad Revenue Data from all integrated mediation sources.
- Select Save
Now Appier FMP can use ad revenue data to optimize your user targeting and campaigns.
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 Appier FMP.
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 Appier FMP, follow these steps.
- Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
- In the Adjust dashboard, find your app and select your app options caret (^)
- Select Partner Setup > Appier FMP
- Turn on Parameter Forwarding
- Select Partner Parameter Mapping
- 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 Appier FMP name.
- Select Save
Now Appier FMP 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 Appier FMP receive in-app event data. You can link every in-app event in Adjust to a preset Appier FMP name or a custom event name.
To forward in-app events to Appier FMP, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Appier FMP > Event Linking
- Find the event you want to link and update the field with a Appier FMP event or your own custom name
- When you finish linking events, select OK
- Select Save
Now Appier FMP will receive in-app event data for each of your linked events.
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 FMP
Appier FMP requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{country} | Device two-character country code |
{currency} | Original ISO 4217 currency code sent from Adjust SDK |
{device_name} | Device model number |
{fb_adgroup_id} | Facebook ad ID |
{fb_adgroup_name} | Facebook ad name |
{fb_campaign_group_id} | Facebook campaign ID |
{fb_campaign_group_name} | Facebook campaign name |
{fb_campaign_id} | Facebook ad set ID |
{fb_campaign_name} | Facebook ad set name |
{language} | Device two-character language code |
{match_type} | Attribution method |
{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_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{sdk_version} | Adjust SDK version (per app) |
{timezone} | Device time zone |
{user_agent} | Incoming raw user agent |
{app_id} | Store App ID or Google Play Store |
{app_version_short} | App version number (Android), release-version-number for the bundle (iOS) |
{click_time_hour} | Attributed click timestamp, rounded to the nearest hour |
{connection_type} | Internet connection type |
{created_at_hour} | Activity timestamp, rounded down to the nearest hour |
{impression_based} | 1 if impression-based engagement, 0 if not |
{impression_time_hour} | Attributed impression timestamp, rounded to the nearest hour |
{installed_at_hour} | Install (i.e., first app open) timestamp rounded to the nearest hour |