Set up MAAS
MAAS is an ad network integrated with Adjust. Our integration lets MAAS receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with MAAS for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with MAAS.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to MAAS 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
INSTALL_EVENT_NAME
- For help finding your credentials, contact your MAAS representative.
Select MAAS and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > MAAS. 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 MAAS.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with MAAS. To enable data sharing:
- Enter your INSTALL_EVENT_NAME.
Once you enable data sharing with MAAS, Adjust automatically sends MAAS the following data, by default:
- install
- event
- rejectedInstall
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 MAAS by default.
- install
- event
- rejectedInstall
Send additional data
Choose the amount and type of data that you want to share with MAAS through callbacks. MAAS may use this information to optimize performance.
- Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with MAAS:
- Data from all attribution sources
- Only data attributed to MAAS
In-app revenue (from in-app purchases)
Sharing in-app revenue lets MAAS receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Map events
Map events that you want to share to the values that MAAS can receive. Data for unmapped events is not shared with MAAS.
Under Map events, follow these steps to choose the in-app events you want to directly send to MAAS.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with MAAS.
- 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.
- Select Apply.
Now MAAS will receive in-app event data for each of your linked events.
Configure your link and settings
You have the option to set your:
Create your link and share it with MAAS
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 MAAS.
Once you’ve created your link, share it with MAAS for placement in campaigns.
List of all parameters forwarded to MAAS
MAAS requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{android_id} | Android ID (Android only) |
{city} | Device city |
{device_name} | Device model number |
{idfa||gps_adid||fire_adid} | IDFA, or GPS ADID if IDFA is empty, or Fire ADID if IDFA and GPS ADID are empty |
{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 |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{revenue_usd} | Revenue, in US dollars |
{sdk_version} | Adjust SDK version (per app) |
{tracking_limited} | 1 if tracking is limited, 0 if not |
{user_agent} | Incoming raw user agent |
{app_id} | Store App ID or Google Play Store |
{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 |
{connection_type} | Internet connection type |
{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 |
{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 |
{network_name} | Network name, as taken from the tracker |
{rejection_reason} | Reason for a rejected attribution |
{is_s2s} | 1 if server to server engagement, 0 if not |