Set up Nativex
Nativex is an ad network integrated with Adjust. Our integration lets Nativex receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Nativex for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Nativex.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Nativex 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 Nativex and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Nativex. 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 Nativex.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Nativex. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with Nativex, Adjust automatically sends Nativex the following data, by default:
- install
- session
- uninstall
- reinstall
- reattribution
- rejectedInstall
- rejectedReattribution
- reinstall reattribution (attributed only)
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 Nativex by default.
- install
- session
- uninstall
- reinstall
- reattribution
- rejectedInstall
- rejectedReattribution
- reinstall reattribution (attributed only)
Send additional data
Choose the amount and type of data that you want to share with Nativex through callbacks. Nativex may use this information to optimize performance.
Configure your link and settings
You have the option to set your:
Create your link and share it with Nativex
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 Nativex.
Once you’ve created your link, share it with Nativex for placement in campaigns.
List of all parameters forwarded to Nativex
Nativex requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{android_id} | Android ID (Android only) |
{city} | Device city |
{click_attribution_window} | Attribution window settings for device matching (hours) |
{country} | Device two-character country code |
{deeplink} | Deeplink URL appended to click URL |
{device_name} | Device model number |
{device_type} | Device type |
{event_name} | Event name, as set in the Dashboard |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{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 |
{label} | Value of the Adjust "label" parameter sent on click |
{language} | Device two-character language code |
{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_version} | Operating system version number |
{region} | Device region code |
{sdk_version} | Adjust SDK version (per app) |
{user_agent} | Incoming raw user agent |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{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 |
{conversion_duration} | Time between click and install or reattribution in seconds |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{engagement_time} | Engagement timestamp |
{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 |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{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) |
{reinstalled_at} | Reinstall timestamp |
{store} | Target store of click |
{tracker_name} | Current tracker name |
{uninstalled_at} | Uninstall timestamp (estimation based on last session time) |
{is_s2s} | 1 if server to server engagement, 0 if not |
{proxy_ip_address} | IP address of user's proxy |