Set up Yandex Direct
Yandex Direct is a network and Adjust module partner. Our integration lets Yandex Direct receive attribution and in-app event data through automated callbacks.
Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Yandex Direct. Then, use our advanced setup instructions to customize what information Yandex Direct receives.
Basic setup
To turn on Adjust’s integration with Yandex Direct, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > ADD PARTNERS
- Select the add (+) icon next to Yandex Direct
- Turn on Enabled
- Optional: see advanced setup to customize your callbacks
- Select Save
Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to Yandex Direct to launch your campaign.
Yandex Direct will receive callbacks for these activities:
- install
- session
- reinstall
- reattribution
- event
- rejectedInstall
Note: Make sure to add "&ya_click_id={logid}" to your Adjust tracker URL on the Yandex Direct platform. If you are running a re-engagement campaign (web+app scenario) make sure to add "adj_ya_click_id={logid}" or "adjust_ya_click_id={logid}"
If you are running dynamic retargeting campaigns or wants to get SKAdNetwork statistics in Yandex Direct cabinet, please add Yandex App ID in the " YANDEX APP ID " entry box
Optional: If you are running Smart Banner campaigns based on your product item feed enter your Yandex Metrika tag number in the "YANDEX ECOM FEED COUNTER" entry box
Advanced setup
Choose which data Yandex Direct receives from Adjust by customizing your setup.
Only forward data attributed to Yandex Direct
Adjust sends Yandex Direct your installs and reattributions across all ad platforms.
To stop Yandex Direct from receiving data attributed to other ad platforms, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Yandex Direct
- Turn on Attributed Only
Now Yandex Direct will only receive data attributed to their own platform.
Forward in-app revenue
In-app revenue forwarding lets Yandex Direct receive revenue amounts along with your revenue event data.
To forward in-app revenue to Yandex Direct, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Yandex Direct
- Turn on In-App Revenue Forwarding
Now Yandex Direct will receive the revenue amount for every tracked transaction.
Note: Link at least one revenue event to Yandex Direct before turning on In-App Revenue Forwarding.
Forward uninstalls / reinstalls
To forward uninstalls and/or reinstalls to Yandex Direct, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Yandex Direct
- Turn on Uninstall / Reinstall Forwarding
Now Yandex Direct will receive all of your app’s uninstall and/or reinstall data.
Forward sessions
Adjust does not automatically send session callbacks due to the high volume of sessions.
To forward in-app sessions to Yandex Direct, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Yandex Direct
- Turn on Session Forwarding
Now Yandex Direct will receive your app’s session activity.
Forward custom data
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Yandex Direct.
Note: Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.
To forward partner parameters to Yandex Direct, follow these steps.
- Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
- In the Adjust dashboard, find your app and select your app options caret (^)
- Select Partner Setup > Yandex Direct
- Turn on Parameter Forwarding
- Select Partner Parameter Mapping
- In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding Yandex Direct name.
- Select Save
Now Yandex Direct will receive custom event details for each of your linked events.
Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.
Forward in-app events
Event linking lets Yandex Direct receive in-app event data. You can link every in-app event in Adjust to a preset Yandex Direct name or a custom event name.
To forward in-app events to Yandex Direct, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > Yandex Direct > Event Linking
- Find the event you want to link and update the field with a Yandex Direct event or your own custom name
- When you finish linking events, select OK
- Select Save
Now Yandex Direct will receive in-app event data for each of your linked events.
List of all parameters forwarded to Yandex Direct
Yandex Direct requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{currency} | Original ISO 4217 currency code sent from Adjust SDK |
{device_name} | Device model number |
{device_type} | Device type |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{ip_address} | Device IP address |
{match_type} | Attribution method |
{nonce} | Random lowercase alphanumeric string (unique per callback) |
{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 |
{revenue_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{user_agent} | Incoming raw user agent |
{activity_kind} | Type of user activity |
{app_name} | Name of the app |
{app_version} | App version number (Android), build-version-number for the bundle (iOS) |
{click_time} | Attributed click timestamp |
{created_at} | Activity timestamp |
{device_manufacturer} | Device manufacturer name |
{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 |
{rejection_reason} | Reason for a rejected attribution |
{oaid} | OAID device ID |