---
metadata:
- name: generator
content: Diplodoc Platform v5.50.6
alternate:
- https://appmetrica.yandex.by/docs/en/mobile-tracking/adwords-settings.md
- https://appmetrica.yandex.by/docs/ru/mobile-tracking/adwords-settings.md
---
> **Documentation Index:** Fetch the complete configuration index at https://appmetrica.yandex.by/docs/en/llms.txt
# Tracking Google Ads campaigns
AppMetrica allows you to track Google Ads advertising campaigns.
To enable tracking, you should link the AppMetrica and Google Ads accounts via the link identifier that is used for attributing the installation source.
## How tracking works {#features}
Google Ads tracking requires collecting advertising IDs (GAID/IDFA) from devices. If the app doesn't collect advertising IDs, tracking won't work.
#### Android
Access to [advertising IDs](../sdk/android/get-ad-id) is granted by default.
#### iOS
{% note alert "" %}
Starting from version 14.5, apps don't have access to IDFA by default. To enable tracking, you have to implement an [access request for IDFA](../mobile-tracking/ios-tracking#request).
{% endnote %}
This section explains the steps for setting up AppMetrica tracking to work with Google Ads ad campaigns.
## Step 1. Get the Google Ads link ID {#gaid}
Create a link to AppMetrica for advertised app in the Google Ads web interface:
1. Log in to your Google Ads account, go to the page menu, and click **Tools** {width=20px}.
1. In the section menu, select **Data manager**.
1. On the **Data manager** page, click **Connect product**.
1. Select **Third-party app analytics** and click **Continue**.
1. Click **Create link ID** if you link accounts for the first time, or the **+** button if your account already linked AppMetrica or other third-party app analytics accounts.
1. In the **App analytics provider** drop-down list, select **Other provider**. Specify the provider ID AppMetrica — 1444794547.
1. Select the platform of the mobile app.
1. Find the advertised application using the search field.
1. Click **Create link ID**.
1. Copy the received link ID and use it when creating a tracker in AppMetrica.
## Step 2. Create a tracker in AppMetrica {#general}
1. In the AppMetrica interface, go to **Tracking** → **Add tracker**.
1. Enter the name of the tracker.
1. Select Google Ads as the media source.
1. Specify **Main** as the tracker type.
1. The provider ID is already specified. Specify the link ID that you obtained in [Step 1](#gaid). You can find it in the [Linked Accounts](https://adwords.google.com/aw/productlinks/thirdpartyappanalytics) section of Google Ads.
## Step 3. (_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.
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. The default value is 24 hours.
Acceptable values are from 1 to 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. The default value is 10 days.
Acceptable values are from 1 to 90 days for clicks and up to 24 hours for impressions.
- **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).
## Step 4. (_Optional_) Configure postbacks {#postbacks}
{% note alert "" %}
You don't need to configure the Installation postback for Google Ads. Attribution to the source is performed by link ID.
{% 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 5. Save your changes {#save}
Click **Save** at the bottom of the page.
## Step 6. Import conversions {#conversions}
{% note alert "" %}
Events for import can be displayed with a delay. If events do not appear immediately, start the Google Ads campaign and check the list after a few hours.
{% endnote %}
After your ad campaign launches, import the events in the Google Ads interface:
1. In your Google Ads account, go to the page menu and click **Goals** {width=20px}.
2. In the section menu, expand the **Conversions** list.
3. Select **Summary**.
4. Click **Create conversion action**.
5. Select **Import** → **Third-party app analytics** and click **Continue**.
6. Select the `first_open` event of the advertised application.
{% note info "" %}
You can also select target events that are sent via [postback](*postback).
{% endnote %}
7. Click **Import and continue**.
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
[*postback]: A GET request to the specified URL (the postback URL), which certain parameters can be sent to. You can add up to five requests per campaign. For more information, see the [postback policy](https://appmetrica.yandex.by/docs/en/mobile-tracking/policy.md).