We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Set up Smadex

Smadex is an ad network integrated with Adjust. Our integration lets Smadex receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with Smadex for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Smadex.

Before you begin

Requirements

Admin, Editor, or Custom Editor permissions in Adjust.
Adjust SDK v4.0.0 and later to map SDK parameters to Smadex parameters. Follow the guides linked below to use this feature.

Credentials

TRACKING GROUP ID

For help finding your credentials, contact your Smadex representative.

Select Smadex and your app in Campaign Lab

Under Campaign Lab, select Partners.
Select New partner > Smadex. 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 Smadex.
Select Next.

Enable data sharing

Enable data sharing to activate the integration with Smadex. To enable data sharing:

Enter your TRACKING GROUP ID.

Once you enable data sharing with Smadex, Adjust automatically sends Smadex the following data, by default:

install
session
uninstall
reinstall
reattributionReinstall
reattribution
event
rejectedInstall
rejectedReattribution
ad revenue

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 Smadex by default.

install
session
uninstall
reinstall
reattributionReinstall
reattribution
event
rejectedInstall
rejectedReattribution
ad revenue

Send additional data

Choose the amount and type of data that you want to share with Smadex through callbacks. Smadex 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 Smadex:

Data from all attribution sources
Only data attributed to Smadex

Ad revenue (from ad views)

Ad revenue sharing lets Smadex receive user ad revenue data. This lets Smadex use ad revenue data to optimize your user targeting and campaigns.

Growth solution:

This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.

To share ad revenue to Smadex, select one or more Ad Revenue Sources.

If you leave this field empty, we send ad revenue data from all integrated mediation sources.

Sessions

Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Smadex will receive your app’s session activity.

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets Smadex receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Smadex 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 Smadex can receive. Data for unmapped events is not shared with Smadex.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Smadex. 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 Smadex.

Select Map event.
In the Adjust event list, choose the Adjust event that you want to share with Smadex.
Under Partner event, you need to select the Smadex event that corresponds to the Adjust event.
1. 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.
2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
Select Apply.

Now Smadex will receive in-app event data for each of your linked events.

Map all events

If Smadex supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Smadex 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 Smadex

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 Smadex.

Once you’ve created your link, share it with Smadex for placement in campaigns.

List of all parameters forwarded to Smadex

Smadex requires Adjust to send the following parameters (data points) with your callbacks:

Placeholder	Information
`{country}`	Device two-character country code
`{idfa\|\|gps_adid}`	IDFA, or GPS ADID if IDFA is empty
`{ip_address}`	Device IP address
`{match_type}`	Attribution method
`{os_name}`	Device operating system
`{revenue_usd}`	Revenue, in US dollars
`{app_id}`	Store App ID or Google Play Store
`{created_at}`	Activity timestamp
`{impression_based}`	1 if impression-based engagement, 0 if not
`{installed_at}`	Install (i.e., first app open) timestamp
`{is_organic}`	1 if organic traffic, 0 if non-organic
`{rejection_reason}`	Reason for a rejected attribution
`{ad_impressions_count}`	Number of mobile ads served to end users
`{ad_revenue_network}`	Ad network that displayed the ad
`{ad_revenue_unit}`	Ad unit that generated the revenue
`{ad_revenue_placement}`	User placement, as defined on the platform
`{ad_mediation_platform}`	Mediation platform name