> ## Documentation Index
> Fetch the complete documentation index at: https://docs.metricanic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Google Ads

> Connect the Google account that will receive your tracked conversions, then choose an offline conversion action.

The Google Ads integration sends conversions recorded in Metricanic back to Google. Use it when a lead or sale happens on an offer or in a backend system, and you want that outcome associated with the original Google ad click.

Connecting the account is the first half of the setup. A [Google Ads postback route](/integrations/google-ads-postbacks) chooses which Google conversion action receives an event. The campaign's **2. Events** tab defines which tracked events actually trigger that route.

## Understand the connection

The conversion follows this path:

1. Google sends a visitor with a Google click identifier.
2. Metricanic records the visit and saves that identifier.
3. Your offer or backend reports a conversion to Metricanic using the Metricanic visit ID.
4. The matching goal sends an outgoing postback.
5. The integration uploads the conversion to the selected Google Ads action through Google's Data Manager API.

The Google identifier and the Metricanic visit ID have different jobs. The visit ID attributes the conversion inside Metricanic. The Google identifier connects the uploaded conversion to the ad click in Google.

<Note>
  This integration uploads offline click conversions. It does not synchronize advertising costs,
  pause Google campaigns, or upload enhanced conversion user data such as email addresses and phone
  numbers.
</Note>

## Connect the right Google account

Open **Integrations**, click **Add integration**, and choose **Google Ads**. Sign in to Google and approve the requested access. Return to Metricanic and check that the connection is active.

Use a Google identity that can access the account owning your conversion action. Metricanic requests Google account identity and Data Manager access. There is no Google Ads developer token field in this setup.

If you manage several advertisers, check the connected Google identity and destination account when generating each route. An active connection alone does not select the advertiser that should receive a conversion.

## Choose the conversion destination

Click **Configure postback** on the active connection and enter:

| Setting                          | How to choose it                                                                                      |
| -------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Operating account ID**         | The Google Ads customer account that owns the conversion action                                       |
| **Login account ID**             | The manager account used to access that customer, when your setup needs one. Otherwise leave it empty |
| **Offline conversion action ID** | The numeric ID of an offline/import click conversion action with type `UPLOAD_CLICKS`                 |

You can enter a customer ID with or without hyphens. For the action, the setup also accepts a full resource name such as `customers/1234567890/conversionActions/987654321`, provided the customer matches the operating account.

For example, if an advertiser owns a **Qualified lead** action, use that advertiser's customer ID as the operating account. A manager account belongs in **Login account ID**, not in place of the action's owner. Open the action in Google Ads and use the numeric `ctId` value shown in its URL, rather than the action's display name.

Click **Generate postback URL**. Metricanic validates the configuration with Google before returning a route. This validation does not upload a real conversion. Continue with [Send conversions to Google Ads](/integrations/google-ads-postbacks) to connect the route to a campaign and test the full journey.

## Keep the connection usable

If setup reports expired authorization or invalid credentials, reconnect Google Ads before generating or testing another route. If validation rejects the destination, verify the operating account, manager relationship, and action type together.

**Archive integration** stops conversion delivery through that connection. Use it when retiring the Google destination. Removing an integration does not stop the advertising campaign in Google.

Record spend separately using the campaign's [cost settings](/tracking/costs) or [cost corrections](/reports/cost-corrections). A working conversion connection does not make cost or ROI complete.