> 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/faq/debugging-monitoring/google-ads-product-ids-do-not-match-my-conversion-events.md).

# Google Ads Product IDs do not match my conversion events

Why Google Ads shows "Basket data needs attention" and how to align the product IDs in your conversion events with the IDs in your product feed.

### What is the problem?

When you send purchase events with product data (also called *basket data* or *conversions with cart data*), the advertising platform tries to match every product in the event to a product in your product feed. In Google Ads, the `item_id` of each product in the purchase event must be **exactly equal** to the `id` of that product in your Google Merchant Center feed.

If the IDs don't match, conversions are still recorded, but Google cannot connect them to specific products. In Google Ads, you'll see this as **"Basket data needs attention"** on the conversion action:

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FKdpXnGXpmXuvSyK5ShRu%2Fconversions_ads.png?alt=media&amp;token=f511eae4-3f2e-4009-820d-2ce0125317b6" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This is not a server-side tagging issue. AdPage forwards the product IDs exactly as they are sent from your website's dataLayer. The mismatch is between your website's data and your product feed.
{% endhint %}

### Why does this matter?

Without matching product IDs, you lose:

* Product-level reporting in Google Ads (which products were sold, revenue per product).
* Insights into which ads led to which products being bought (including cross-sell).
* Better input for Performance Max and Shopping campaign optimisation.

### Common causes

| Cause                                                                      | Product feed `id`      | Event `item_id`                |
| -------------------------------------------------------------------------- | ---------------------- | ------------------------------ |
| Feed uses variant ID, tracking uses parent product ID                      | `331356` (size 48)     | `70249C`                       |
| Feed uses SKU, tracking uses internal product ID (or the other way around) | `GRI-70249C-48`        | `331356`                       |
| Prefix or suffix added by a feed app or plugin                             | `shopify_NL_8123_4456` | `4456`                         |
| Different formatting                                                       | `00331356`             | `331356`                       |
| Variant ID missing from tracking                                           | `331356`               | *(empty or only product name)* |

{% hint style="warning" %}
The IDs must match **exactly**, including prefixes, leading zeros and capitalisation.
{% endhint %}

### How to check whether your IDs match

{% stepper %}
{% step %}

#### Open the basket data diagnostics

In Google Ads, go to **Goals → Conversions → Summary**, hover over the status of your purchase conversion action and click **Go to diagnostics** next to *Basket data*.
{% endstep %}

{% step %}

#### Look up the IDs in your product feed

In Google Ads, go to **Campaigns → Products → Products**. The **Item ID** column shows the IDs Google expects. You can also find them in Google Merchant Center.

Note whether the feed contains one ID per variant (for example per size) or one ID per product.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2Fw1ggkgt1ALDsKIInA4IX%2Fimage.png?alt=media&amp;token=4bce9863-90dd-4a8d-805d-ea33f0637f02" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Check the IDs in your purchase event

Place a test order (or use a recent order) and check the `item_id` values in the `items` array of the `purchase` event. You can do this in GTM Preview mode, the server container's preview mode, or your browser's developer console (`dataLayer`).
{% endstep %}

{% step %}

#### Compare

Take the same product and compare the feed `id` with the event `item_id`. If they differ, use the causes table above to find the pattern.
{% endstep %}
{% endstepper %}

### How to fix it

There are three options. We recommend them in this order:

1. **Align the dataLayer with the feed (recommended).** Have your developer send the same ID in `item_id` that the feed uses as `id`. If the feed works on variant level, the dataLayer must send the variant ID of the product that was actually bought.
2. **Transform the ID in your tag configuration.** If the difference is a fixed pattern (for example a prefix), you can rebuild the ID in GTM with a variable before it's sent. This works, but adds maintenance: every change in the feed app can break it again.
3. **Change the feed.** Only do this if the feed IDs are clearly wrong.

{% hint style="danger" %}
Changing the IDs in your product feed resets the performance history of those products in Shopping and Performance Max campaigns. Prefer fixing the tracking side.
{% endhint %}

Also check that the Google Ads conversion tag has product-level sales data enabled with the correct **Merchant Center ID**, **feed country** and **feed language**. A wrong feed country or language also prevents matching, even when the IDs are correct.

### After the fix

Google Ads needs a few days of new conversions before the diagnostics update. Only new conversions are matched; historical conversions are not corrected.

{% hint style="info" %}
Need help comparing your feed with your tracking? Contact AdPage support and share an example order number and the matching product ID from your feed.
{% endhint %}


---

# 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/faq/debugging-monitoring/google-ads-product-ids-do-not-match-my-conversion-events.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.
