Set up Mobivity
Mobivity is an ad network integrated with Adjust. Our integration lets Mobivity receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Mobivity for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Mobivity.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Mobivity 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
Select Mobivity and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Mobivity. 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 Mobivity.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Mobivity. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with Mobivity, Adjust automatically sends Mobivity the following data, by default:
- install
- session
- reattribution
- 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 Mobivity by default.
- install
- session
- reattribution
- event
- rejectedInstall
Send additional data
Choose the amount and type of data that you want to share with Mobivity through callbacks. Mobivity 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 Mobivity:
- Data from all attribution sources
- Only data attributed to Mobivity
Ad spend
Ad spend sharing lets Mobivity receive user ad spend data. This lets Mobivity use ad spend data to optimize your campaigns.
Adjust sends Mobivity the ad spend data received through callbacks only. This data comes from the following solutions that you’ve set up, as applicable for Mobivity:
If Mobivity wants complete ad spend data, then you can set up Ad spend third-party storage exports for Mobivity.
This feature is available with Adjust’s SpendWorks package. To purchase our SpendWorks package, contact your sales representative.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Mobivity will receive your app’s session activity.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Mobivity 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 Mobivity can receive. Data for unmapped events is not shared with Mobivity.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Mobivity. 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 Mobivity.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Mobivity.
- Under Partner event, you need to select the Mobivity 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 Mobivity will receive in-app event data for each of your linked events.
Map all events
If Mobivity supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Mobivity will receive in-app event data for all your linked events.
Configure your link and settings
You have the option to set your:
Create your link and share it with Mobivity
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 Mobivity.
Once you’ve created your link, share it with Mobivity for placement in campaigns.
List of all parameters forwarded to Mobivity
Mobivity requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{click_attribution_window} | Attribution window settings for device matching (hours) |
{cost_amount} | Cost of the user engagement (available for ad spend tracking only) |
{cost_currency} | ISO 4217 currency code of the cost data (available for ad spend tracking only) |
{cost_type} | The campaign pricing model (available for ad spend tracking only) |
{event_name} | Event name, as set in the Dashboard |
{idfa||gps_adid} | IDFA, or GPS ADID if IDFA is empty |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{ip_address} | Device IP address |
{match_type} | Attribution method |
{postal_code} | Device postal code of IP address |
{revenue_usd} | Revenue, in US dollars |
{tracking_enabled} | 1 if tracking is enabled, 0 if not |
{tracking_limited} | 1 if tracking is limited, 0 if not |
{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_dashboard} | Name of the app in the Adjust Dashboard |
{app_name} | Name of the app |
{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_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 |
{installed_at} | Install (i.e., first app open) timestamp |
{rejection_reason} | Reason for a rejected attribution |