Set up imobile
imobile is an ad network integrated with Adjust. Our integration lets imobile receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with imobile for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with imobile.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to imobile 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
INTEGRATION ID
- For help finding your credentials, contact your imobile representative.
Select imobile and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > imobile. 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 imobile.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with imobile. To enable data sharing:
- Enter your INTEGRATION ID.
Once you enable data sharing with imobile, Adjust automatically sends imobile the following data, by default:
- install
- session
- 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 imobile by default.
- install
- session
- reattribution
- event
Send additional data
Choose the amount and type of data that you want to share with imobile through callbacks. imobile 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 imobile:
- Data from all attribution sources
- Only data attributed to imobile
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means imobile will receive your app’s session activity.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets imobile 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 imobile can receive. Data for unmapped events is not shared with imobile.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with imobile. 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 imobile.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with imobile.
- Under Partner event, you need to select the imobile 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 imobile will receive in-app event data for each of your linked events.
Map all events
If imobile supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now imobile 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 imobile
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 imobile.
Once you’ve created your link, share it with imobile for placement in campaigns.
List of all parameters forwarded to imobile
imobile requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{country} | Device two-character country code |
{device_name} | Device model number |
{device_type} | Device type |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{ip_address} | Device IP address |
{language} | Device two-character language code |
{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 |
{referrer} | Google Play Store referrer (Android only) |
{revenue_usd} | Revenue, in US dollars |
{timezone} | Device time zone |
{user_agent} | Incoming raw user agent |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{app_version_raw} | App version number (Android), build-version-number for the bundle (iOS) |
{created_at} | Activity timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{rejection_reason} | Reason for a rejected attribution |
{tracker_name} | Current tracker name |