Set up mFilterIT AdFraud Service
mFilterIT AdFraud Service is an analytics partner integrated with Adjust. Our integration lets mFilterIT AdFraud Service receive data measured in Adjust through automated callbacks. Use this data with the partners' tools for analytics and insights.
In this article, learn how to set up measurement with mFilterIT AdFraud Service for your app. This includes activating the integration and choosing what data Adjust can share with mFilterIT AdFraud Service.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to mFilterIT AdFraud Service parameters. Follow the guides linked below to use this feature.
iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona
Credentials
CUSTOMER ID
- For help finding your credentials, contact your mFilterIT AdFraud Service representative.
Select mFilterIT AdFraud Service and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > mFilterIT AdFraud Service. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with mFilterIT AdFraud Service.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with mFilterIT AdFraud Service. To enable data sharing:
- Enter your CUSTOMER ID.
Adjust does not automatically send click callbacks due to the high volume of clicks. To send clicks to mFilterIT AdFraud Service, enable the Send clicks toggle.
Once you enable data sharing with mFilterIT AdFraud Service, Adjust automatically sends mFilterIT AdFraud Service the following data, by default:
- click
- install
- 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:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- 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 mFilterIT AdFraud Service by default:
- click
- install
- reattribution
- event
Send additional data
Choose the amount and type of data that you want to share with mFilterIT AdFraud Service through callbacks. mFilterIT AdFraud Service may use this information to optimize performance.
To send additional data, you can review and customize the following:
Map events
Map events that you want to share to the values that mFilterIT AdFraud Service can receive. Data for unmapped events is not shared with mFilterIT AdFraud Service.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with mFilterIT AdFraud Service. 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 mFilterIT AdFraud Service.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with mFilterIT AdFraud Service.
- Under Partner event, you need to select the mFilterIT AdFraud Service event that corresponds to the Adjust event.
- 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.
- In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
- 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 Apply.
Now mFilterIT AdFraud Service will receive in-app event data for each of your linked events.
Map all events
If mFilterIT AdFraud Service supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now mFilterIT AdFraud Service will receive in-app event data for all your linked events.
Enable mFilterIT AdFraud Service for your app
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
Select Enable partner to enable mFilterIT AdFraud Service for your app. Analytics partners don't work with links for campaigns. Once enabled, our integration sends attribution and in-app event data via automated callbacks.
List of all parameters forwarded to mFilterIT AdFraud Service
mFilterIT AdFraud Service requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{android_id} | Android ID (Android only) |
{api_level} | API level (Android only) |
{country_subdivision} | Device subdivision of country, e.g., state |
{country} | Device two-character country code |
{deeplink} | Deeplink URL appended to click URL |
{device_name} | Device model number |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{ip_address} | Device IP address |
{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. |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{postal_code} | Device postal code of IP address |
{random_user_id} | Random user ID (per device) |
{referrer} | Google Play Store referrer (Android only) |
{reftag} | Random device reference tag |
{region} | Device region code |
{sdk_version} | Adjust SDK version (per app) |
{timezone} | Device time zone |
{user_agent} | Incoming raw user agent |
{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_referer} | Referrer header from click |
{click_time} | Attributed click timestamp |
{connection_type} | Internet connection type |
{conversion_duration} | Time between click and install or reattribution in seconds |
{cpu_type} | CPU type |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{device_manufacturer} | Device manufacturer name |
{hardware_name} | Hardware name |
{impression_based} | 1 if impression-based engagement, 0 if not |
{install_begin_time} | App download began timestamp (Android and Google Play Store only) |
{installed_at} | Install (i.e., first app open) timestamp |
{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) |
{tracker} | 6-character Adjust tracker token |