Set up VK Ads (ex. myTarget)
VK Ads (ex. myTarget) is an ad network integrated with Adjust. Our integration lets VK Ads (ex. myTarget) receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with VK Ads (ex. myTarget) for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with VK Ads (ex. myTarget).
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to VK Ads (ex. myTarget) 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 VK Ads (ex. myTarget) and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > VK Ads (ex. myTarget). 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 VK Ads (ex. myTarget).
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with VK Ads (ex. myTarget). To enable data sharing:
- Turn on Enabled
Once you enable data sharing with VK Ads (ex. myTarget), Adjust automatically sends VK Ads (ex. myTarget) the following data, by default:
- install
- event
- rejectedInstall
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 VK Ads (ex. myTarget) by default.
- install
- event
- rejectedInstall
Send additional data
Choose the amount and type of data that you want to share with VK Ads (ex. myTarget) through callbacks. VK Ads (ex. myTarget) 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 VK Ads (ex. myTarget):
- Data from all attribution sources
- Only data attributed to VK Ads (ex. myTarget)
In-app revenue (from in-app purchases)
Sharing in-app revenue lets VK Ads (ex. myTarget) 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 VK Ads (ex. myTarget) can receive. Data for unmapped events is not shared with VK Ads (ex. myTarget).
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with VK Ads (ex. myTarget). 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 VK Ads (ex. myTarget).
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with VK Ads (ex. myTarget).
- Under Partner event, you need to select the VK Ads (ex. myTarget) 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 VK Ads (ex. myTarget) will receive in-app event data for each of your linked events.
Map all events
If VK Ads (ex. myTarget) supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now VK Ads (ex. myTarget) will receive in-app event data for all your linked events.
Map parameters
You usually need to map parameters to share custom data with VK Ads (ex. myTarget).
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to VK Ads (ex. myTarget). This lets VK Ads (ex. myTarget) receive custom event details for each of your linked events.
Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.
To share partner parameters to VK Ads (ex. myTarget), follow these steps.
- Set up partner parameters within the Adjust SDK.
- Check Before you begin for all SDK development platform links.
- Under Set your data sharing options, select Parameters.
- Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
- Select Map parameter.
- In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
- In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.
Configure your link and settings
You have the option to set your:
Create your link and share it with VK Ads (ex. myTarget)
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 VK Ads (ex. myTarget).
Once you’ve created your link, share it with VK Ads (ex. myTarget) for placement in campaigns.
Partner specific setup instructions
VK Ads allows you to send any kind of partner parameters. Any partner parameters that you send in the SDK will be forwarded to VK Ads, and incorporated into their analysis.
List of all parameters forwarded to VK Ads (ex. myTarget)
VK Ads (ex. myTarget) requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{android_id} | Android ID (Android only) |
{city} | Device city |
{country} | Device two-character country code |
{currency} | Original ISO 4217 currency code sent from Adjust SDK |
{device_name} | Device model number |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{ip_address} | Device IP address |
{isp} | Device internet service provider |
{language} | Device two-character language code |
{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_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_usd} | Revenue, in US dollars |
{user_agent} | Incoming raw user agent |
{activity_kind} | Type of user activity |
{app_id} | Store App ID or Google Play Store |
{app_version} | App version number (Android), build-version-number for the bundle (iOS) |
{connection_type} | Internet connection type |
{device_manufacturer} | Device manufacturer name |
{impression_based} | 1 if impression-based engagement, 0 if not |
{installed_at} | Install (i.e., first app open) timestamp |
{referral_time} | User landed on app Play Store page timestamp (Android and Google Play Store only) |
{rejection_reason} | Reason for a rejected attribution |
{oaid} | OAID device ID |