> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/optimize-your-setup/conversion-recovery.md).

# Conversion recovery

Let AdPage send the purchases your Google Ads tag missed to Google Ads after all, through Google's Data Manager API, without an extra tag in your server container.

Your Google Ads tag does not see every purchase. A visitor pays in their banking app and never returns to the thank-you page, closes the tab too early, or comes back in a different browser. [Webhook Matching](https://docs.adpage.io/optimize-your-setup/webhook-matching.md) already links those orders to the visit they belong to. Conversion recovery sends them on to Google Ads.

AdPage sends each purchase itself, through Google's Data Manager API, with the order's click id and hashed customer data. You do not build or import a tag for it in your server container.

Google deduplicates on the order number. A purchase your tag already sent counts once, so keep your conversion tag: Conversion recovery is an extra source on the same conversion action.

## What you need

* **Webhook Matching** is on. Conversion recovery runs on the matched order webhooks.
* A **conversion action** in the Google Ads account, usually your primary purchase action. See [Where to find the Google Ads Conversion ID and Conversion Labels](https://docs.adpage.io/integrations-marketingtools/google-ads/where-to-find-the-google-ads-conversion-id-and-conversion-labels.md) if you still need to create one.
* A way for AdPage to reach the Google Ads account: the account is linked to AdPage's manager account (MCC), or Google Ads is connected for the container under **Integrations**.
* The **Performance** plan or higher. On a lower plan the page shows **From Performance**. AdPage support can open it for your account.

## Set it up

You find it in your container under **Data boosts**, on the **Boosts** tab, at **Conversion recovery**.

1. Under **Settings**, choose the **Google Ads account**.
2. Choose the **conversion action**. Pick the action Smart Bidding optimises for, and use the same action in the tag on your site. With two different actions Google does not deduplicate the two. The action your tag already sends to is marked **your tag**.
3. Choose **which Google login** AdPage delivers with, see below.
4. Click **Test connection**. Google checks a test conversion without anything landing in your account. **View the latest order** shows what AdPage would send for the latest order.
5. Switch on **Send to Google Ads**. The status changes to **Active**.

There is no Save button: a change is stored right away. If you choose another account, the conversion action is cleared and sending switches off, so you choose it again.

{% hint style="warning" %}
**Does your tag send the order number without a prefix?** If Webhook Matching uses a transaction ID prefix, switch on **Remove order prefix**. Google only recognises the same order when both sources send the same order number.
{% endhint %}

{% hint style="info" %}
If AdPage's MCC shows an account whose conversion actions do not match the conversion ID your tag sends to, AdPage warns you. Check that the account belongs to this customer before you click **Use this account anyway**.
{% endhint %}

## What is sent

Per purchase: the order number, value and currency, the time of the purchase, the click id (`gclid`, `gbraid` or `wbraid`), hashed customer data (email address, name and address), device and IP, and whether it is a new or returning customer when your webshop knows it.

* Only purchases are sent. Other events are skipped.
* Only with consent for advertising. Without it nothing goes to Google.
* Email address, name and street leave AdPage hashed with SHA-256 only.
* An order with neither a click id nor customer data is not sent: Google would have nothing to match it with.

## Which Google login

| Choice                        | When                                                                                                                                                                                                 |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Through AdPage's MCC**      | The default. The Google Ads account is under AdPage's manager account.                                                                                                                               |
| **With the own Google login** | The account is under your agency's manager account (MCC), not under AdPage's. AdPage then delivers with the Google login connected for this container under Integrations. No link request is needed. |

If Google refuses the test through AdPage's MCC with a 403, the account is not under that MCC. The test then shows what you can do:

* **Send link request from AdPage**, and accept it in Google Ads under **Admin → Access and security → Managers**. Then test again.
* **Deliver with the own Google login**, for an account under your agency's manager account.

The own Google login needs the permission to send conversions. If it does not have it, a notice with **Reconnect** appears. Click it, sign in with **the same Google account** and tick every box. Your account choice under Integrations stays.

## A separate account per domain

Does your webshop have several domains, each with its own Google Ads account, for example one domain per country? Then link each domain to its own account under **Per domain**. That section appears once the account and conversion action above are chosen.

* An order goes to the account of the domain it checked out on in the browser. A subdomain falls under its domain: an order on `m.shop.com` goes to the account of `shop.com`.
* A domain without its own line, or an order without a domain, goes to the account above.
* All domains use the same Google login.

1. Click **Add the domains of your tag**. AdPage lists the domains your Google Ads tag sent purchases from, with the account named after the domain when there is exactly one. Add a single line with **Add domain**.
2. Choose the **account** and the **conversion action** for each domain. AdPage picks the action your tag on that domain already sends to.
3. A domain is saved as soon as it has an account and an action. Below the list you see how many domains are not done yet.
4. Click **Test all domains**. An error shows next to its domain, and below the list how many domains are OK.

## Read the results

The top of the page measures the last 7 days. It matches the orders from your webshop, by order number, to the conversions your server container sent to Google Ads.

| Tile                        | What it tells you                                                                                                              |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Recovered by AdPage**     | The share of your orders that your tag missed, Conversion recovery sent and Google processed, with the number and the revenue. |
| **Processed by Google**     | What Google processed of everything that reached Conversion recovery.                                                          |
| **Attributed to campaigns** | What Google Ads counts on the conversion action, on the day of the purchase, with the conversion value.                        |

Click a tile to see what is behind it: the orders per outcome, the campaigns and a table per day.

An order ends up in one of these rows:

* **Your tag sent the conversion**. Nothing to recover.
* **Recovered by AdPage**. Your tag missed it, AdPage sent it and Google processed it.
* **Waiting for Google**. Google took the request but has not given a final status yet.
* **Missed, not recovered**, with the reason below.
* **Missed, unknown**. From before AdPage kept track of this.

{% hint style="info" %}
A conversion your site fires directly with gtag.js, outside the server container, is invisible to AdPage and counts as missed here.
{% endhint %}

### Why an order was not recovered

| Reason                                | What it means                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| **No consent for ads**                | The visitor did not consent to advertising. Nothing is sent.                                             |
| **No click id and no customer data**  | Google would have nothing to match the purchase with.                                                    |
| **Match not certain enough**          | Webhook Matching linked the order to a visit as a probable match only. Those are not sent to Google Ads. |
| **Rejected by Google**                | Google refused the purchase, see the reasons below.                                                      |
| **Failed at AdPage**                  | Sending did not work, for example because the Google login was not available.                            |
| **Never reached Conversion recovery** | Webhook Matching did not match the order, or Conversion recovery was off at the time.                    |

When Google refuses a purchase, the page gives Google's reason:

| Google's reason                                    | What it means                                                                                     |
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Click id not valid for this account**            | The click belongs to another Google Ads account. Check the account, or set an account per domain. |
| **Google already had this order number**           | Another source sent the same order first. It counts once.                                         |
| **Google already had this click for this action**  | Google already counted a conversion for this click on this action.                                |
| **Too old for Google**                             | The click or the purchase is too old for Google to accept.                                        |
| **No consent according to Google**                 | Google has no consent for this user.                                                              |
| **Customer data terms not accepted in Google Ads** | Accept the customer data terms in the Google Ads account.                                         |
| **No final status from Google within 48 hours**    | Google never confirmed the request. If this happens often, contact support.                       |

{% hint style="warning" %}
**Does Google Ads count more than AdPage sent?** Then other sources send to the same action too, for example an older upload tag in your server container. If that source uses a different order number, a purchase counts twice. Remove the old tag or point it at another action.
{% endhint %}

### An import action

If the chosen conversion action is an import action, your tag cannot send to it. Everything the action gets comes from AdPage. The page then shows what AdPage sent and what Google did with it, not what it recovered.

## Coming from the AdPage Google Ads tag

Older setups upload purchases with the **AdPage Google Ads tag** in the server container. That tag takes a conversion action ID and a Tagging API key, and sends through the Google Ads API (`UploadClickConversions`).

Since June 2026 Google only allows that call for accounts that already used it, and points new integrations to the Data Manager API. For a new setup, use Conversion recovery instead. A `400` with **Customer ID not found** in Preview means the upload was never switched on for the container. The tag has no field for it.

1. Set up [Webhook Matching](https://docs.adpage.io/optimize-your-setup/webhook-matching.md), so the order webhook is matched to the visit and its click id.
2. Set up Conversion recovery as described above, with the same conversion action.
3. Pause the AdPage Google Ads tag in your server container. Left on, it keeps failing, or it counts purchases twice if it sends a different order number.

## Need help?

Contact support at <support@adpage.io> with the container ID and the order number of a purchase that did not arrive.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/optimize-your-setup/conversion-recovery.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
