---
metadata:
- name: generator
content: Diplodoc Platform v5.50.6
alternate:
- https://appmetrica.yandex.by/docs/en/mobile-tracking/vkads-settings.md
- https://appmetrica.yandex.by/docs/ru/mobile-tracking/vkads-settings.md
---
> **Documentation Index:** Fetch the complete configuration index at https://appmetrica.yandex.by/docs/en/llms.txt
# Tracking VK Ads campaigns (formerly myTarget)
AppMetrica tracks VK Ads campaigns (formerly myTarget).
## Step 1. General settings {#general}
1. In the AppMetrica interface, go to **Tracking** → **Add tracker**.
1. Enter the name of the tracker.
1. Select VK Ads (formerly myTarget) as the media source.
1. Specify **Main** as the tracker type.
1. Choose a platform: iOS or Android.
1. Specify the destination URL and deeplink.
## Step 2. (_Optional_) Configure attribution {#attribution}
This attribution type correctly detects the source that brought users to your app and accurately links app installs to ad interactions, whether they're a click or an impression.
Attribution settings are common for all types of conversions, both installations and subsequent events. For more information about attribution methods, see [AppMetrica tracking technology](https://appmetrica.yandex.by/docs/en/mobile-tracking/technology.md) and [Impression attribution](https://appmetrica.yandex.by/docs/en/mobile-tracking/vta-tracking-specification.md).
- **Reattribution** — Attribution of reinstalls by pre-existing users. This option is disabled by default. For more information, see [Attributing app installs](https://appmetrica.yandex.by/docs/en/mobile-tracking/policy.md#reattribution).
{% note info "" %}
For test devices, reattribution is always enabled (regardless of the option status). For more information about adding test devices, see [Testing attribution](https://appmetrica.yandex.by/docs/en/mobile-tracking/testing-attribution.md).
{% endnote %}
- **Click settings**
- **Fingerprint** — Time interval of attribution (the time between the click and first start). AppMetrica uses it for the [Device Fingerprint Matching](https://appmetrica.yandex.by/docs/en/mobile-tracking/technology.md) attribution.
Acceptable values are from 1 to 24 hours. The default value is 24 hours.
- **Device ID / Install Referrer** — Time interval of attribution, that is used for the [Device Identifier Matching](https://appmetrica.yandex.by/docs/en/mobile-tracking/technology.md) attribution.
Acceptable values are from 1 to 30 days. The default value is 10 days.
- **Impression attribution**, also known as post-view attribution or view-through attribution (VTA), accounts for cases where a user didn't navigate to the app store by clicking an ad but still installed your app shortly after viewing it. The option is enabled by default. For more information, see [Impression attribution](https://appmetrica.yandex.by/docs/en/mobile-tracking/vta-tracking-specification.md).
- **Fingerprint** — Time interval of attribution (the time between the impression and first start). AppMetrica uses it for the [Device Fingerprint Matching](https://appmetrica.yandex.by/docs/en/mobile-tracking/technology.md) attribution.
Acceptable values are from 1 to 24 hours. The default value is 24 hours.
- **Device ID / Install Referrer** — Time interval of attribution, that is used for the [Device Identifier Matching](https://appmetrica.yandex.by/docs/en/mobile-tracking/technology.md) attribution.
Acceptable values are from 1 to 72 hours. The default value is 24 hours.
- **CTV/Desktop attribution** — allows to track installations after ad impressions on Connected TV (CTV) and other platforms. CTV/Desktop attribution accounts for scenarios where the impression occurs on one device and the installation occurs on another, if the devices are on the same network. Enable the option if you run campaigns with impressions on media platforms, and specify the attribution window for CTV and/or Desktop devices. For more details see [CTV/Desktop attribution](https://appmetrica.yandex.by/docs/en/mobile-tracking/ctv-desktop-attribution.md).
Acceptable values for both CTV and Desktop are from 1 to 24 hours. The default value is 6 hours.
- **Equal priority for CTV/Desktop** — if enabled, within the equal priority window, the installation will be attributed to the closest interaction, regardless of the source type.
If disabled, attribution for clicks and impressions on the same device takes priority over CTV/Desktop — if a click or impression on the same device is found within the attribution window, the event will be attributed to it. For more details see [CTV/Desktop attribution](https://appmetrica.yandex.by/docs/en/mobile-tracking/ctv-desktop-attribution.md).
Available only when the **CTV/Desktop attribution** option is enabled.
Acceptable values are from 1 to 6 hours. The default value is 1 hour.
{% cut "Setting up attribution" %}
{style="border: solid 1px #cccccc; max-width: 800px;"}
{% endcut %}
## Step 3. (_Optional_) Configure postbacks {#postbacks}
{% note alert "" %}
You don't need to configure the Installation postback for VK Ads.
{% endnote %}
A postback is a request to the media source's server sent via a set link (postback URL). The request transmits data about a conversion that occurred in the app.
Postbacks are typically used when running CPI/CPA campaigns. You can add up to 10 postbacks per tracker.
Postbacks can be created for configured types of [conversions](https://appmetrica.yandex.by/docs/en/mobile-tracking/conversions.md):
- app installation;
- deeplink opening;
- conversion event.
If you have [default postbacks](https://appmetrica.yandex.by/docs/en/mobile-tracking/add-partner.md#postback-template) configured for the selected media source, they're automatically added to the tracker. You can disable these postbacks, add templates that exist for the media source and are disabled by default, or create new ones.
For media source, [postbacks for all sources](https://appmetrica.yandex.by/docs/en/mobile-tracking/add-partner.md#postback-all-sources) can also be configured — they allow you to send event data to the media source regardless of whether the user was acquired through advertising or organically. Such postbacks are not linked to specific trackers. You can view them on the [media source page](https://appmetrica.yandex.by/docs/en/mobile-tracking/add-partner.md#partner-page).
1. Select the [conversion](https://appmetrica.yandex.by/docs/en/mobile-tracking/conversions.md) for which you want to send a postback, then choose a sending method (POST or GET).
1. Generate a postback URL.
To transmit additional information about the event to the media source, use [macros](https://appmetrica.yandex.by/docs/en/mobile-tracking/postback-specification.md) when generating the URL.
{% note info "" %}
Some media sources can set a permanent Postback URL for their network. In this case, the postback is sent to the media source regardless of other settings. It can't be edited.
{% endnote %}
{% cut "Setting up postbacks" %}
{style="border: solid 1px #cccccc; max-width: 800px;"}
{% endcut %}
## Step 4. (_Optional_) Configure anti-fraud {#anti-fraud}
Enable **FraudScore** to check installs and events for fraud via [FraudScore](https://appmetrica.yandex.by/docs/en/common/fraud-score.md).
**FraudScore** is a paid option ([Pricing plans](https://appmetrica.yandex.by/docs/en/common/pricing/uae-currency.md)) only available for legal entities registered in Russia.
## Step 5. Save changes and test the tracker {#test}
1. Click **Save** at the bottom of the page.
The list of all saved trackers are in the **Trackers** section. You can edit and archive them. The statistics from archived trackers remain available in reports.
2. [Test the tracker](https://appmetrica.yandex.by/docs/en/mobile-tracking/testing-attribution.md) before launching a campaign.
## Step 6. Use the created tracking URLs {#apply}
When creating a tracker, several URL types are available in the interface on the right. You can use them in your campaign after successful testing. To do this, copy the URL from the desired field on the right.
Choose the URL that best matches your scenario:
- **App-to-app link**: A universal link suitable for most campaigns.
- **Tracking link**: Another universal link suitable for most campaigns, excluding when you need your deeplink to direct users to an iOS app. In those cases, use the App-to-app link instead.
- **Impression URL**: Used for [impression attribution](https://appmetrica.yandex.by/docs/en/mobile-tracking/vta-tracking-specification.md).
- **Re-engagement deeplink**: Used for campaigns with deeplinks.
For each tracking URL, you can specify predefined, static (UTM), and custom parameters that will be passed to the destination URL or deeplink. For example, you can disable JavaScript redirect using the `appmetrica_js_redirect=0` parameter. For more information, see [Parameters of the tracking URL](https://appmetrica.yandex.by/docs/en/mobile-tracking/tracking-specification.md).
{% note alert "" %}
Don't use the `target= "_blank"` attribute when inserting a URL into the markup. Some browsers may block the click-through when opening a URL in a new window.
Don't place the URL in the `iframe` element.
{% endnote %}
If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.
Contact support
Suggest an improvement for documentation