Overview

Nativex is a cross-regional mobile marketing and advertising company, part of Mobvista, offering media buying, a DSP, creative production, and influencer marketing. Connect Nativex to Branch to attribute clicks and installs and configure Postbacks.

For more information about integrating ad partners in general, visit our Ad Partner Integration Guide.

Note: this guide is for new Branch

Please note that this guide is about integrating Nativex in the new Branch experience. For information on Nativex in legacy Branch, visit our legacy guide.

Partner capabilities

Capability	Details
Company type	Ad network, exchange
Deep linking	Supported
Attribution	Click-through attribution, View-through attribution
Ad campaign types	Acquisition campaigns, Retargeting campaigns
Ad formats	Desktop web inventory, In-app inventory, Mobile web inventory
Click types	Client-side click
Supported platforms	iOS, Android
Link wrapping	Not supported
Cost ingestion support	Not supported
Pricing models	CPI, CPC

Before you begin

To set up the Nativex integration, you need:

• Ad partner integrations enabled for your Branch account. Availability varies by Branch plan. See Branch pricing or contact your Branch representative.
• A Branch account with access to Configuration > Ad Partners and admin permissions to enable and configure integrations.
• A Nativex account with admin access.

Enable Nativex

To begin, navigate to Configuration > Ad Partners > Nativex.

Nativex doesn't require credentials to activate. The integration is enabled automatically when you select Enable Nativex on the Nativex page.

Configure attribution

By default, Nativex uses your global app attribution settings. To set attribution windows specific to Nativex, enable the Override global app settings toggle on the Attribution windows tab.

For more information, follow Configure attribution in the general Ad Partner Integration Guide.

Configure postbacks

Enabling Nativex automatically activates postbacks, including INSTALL, OPEN, and PURCHASE. The default postback URL template is:

http://next.mobvista.com/install?mobvista_campuuid=${ (last_attributed_touch_data.~campaign_id)! }&mobvista_clickid=${ (last_attributed_touch_data.~click_id)! }&mobvista_type=branch&mobvista_device=${ (user_data.model)! }&mobvista_pl=${ (user_data.os)! }&mobvista_ip=${ (user_data.ip)! }&mobvista_os=${ (user_data.os_version)! }&mobvista_devid=${ (user_data.android_id)! }&mobvista_gaid=<#if (user_data.os)! == "IOS" && (user_data.idfa)!?has_content >${(user_data.idfa)!}<#elseif (user_data.os)! == "IOS">${(user_data.idfv)!}<#elseif (user_data.os)! == "ANDROID"&& (user_data.aaid)!?has_content  >${(user_data.aaid)!}<#elseif (user_data.os)! == "ANDROID">${(user_data.android_id)!}<#elseif (user_data.os)! == "ROKU" >${(user_data.roku_rida)!}<#elseif (user_data.os)! == "SAMSUNG"  >${(user_data.samsung_ifa)!}<#elseif (user_data.os)! == "LG"  >${(user_data.lg_ifa)!}<#elseif (user_data.os)! == "PANASONIC" >${(user_data.panasonic_ifa)!}<#elseif (user_data.os)! == "WINDOWS"  >${(user_data.windows_aid)!}<#elseif (user_data.os)! == "PLAYSTATION" >${(user_data.playstation_ifa)!}<#elseif (user_data.os)! == "XBOX" >${(user_data.xbox_msai)!}</#if>&publisher_id=${ (last_attributed_touch_data.~secondary_publisher)! }&install_begin_time=${(store_install_begin_timestamp)!}&install_time=${(install_activity.timestamp)!}

To add postbacks for additional events or to customize behavior, follow Configure postbacks in the general Ad Partner Integration Guide.

Create a Branch Ad Link

Create a Branch Ad Link to use in your Nativex campaigns. Branch uses the link to attribute clicks and deep link users into your app.

Follow Create Ad Links.

Verify your data

After your integration is connected and events are flowing, you can verify data is reaching Branch:

• In Branch Liveview: confirm that events from your app appear in real time. This is the fastest way to confirm SDK events are firing.
• In Branch Analysis dashboards: review attributed installs and events where Ad Partner Name = Nativex.
• In Nativex: confirm that forwarded events are appearing in your Nativex attribution reporting.

Data mappings

Campaign data

Branch populates the following fields from Nativex campaign data.

Branch field	Partner data
~advertising_partner_name	"Nativex" (static)

Link parameters

By default, Branch automatically appends these link parameters to Nativex ad links. When a user clicks the link, Nativex provides the corresponding values, which Branch ingests and uses for attribution and reporting.

Branch parameter	Link placeholder
Campaign ID	{uuid}
Click ID	{clickid}
Secondary Publisher	{subids}
Click IDFA	{mobvista_idfa}
Click AAID	{mobvista_gaid}&device_ip={mobvista_ip}