Google Ads, GA4 and Merchant Center linked: the data AI needs to decide

Abstract orange illustration on a dark background: a chain link. Article topic: “Google Ads, GA4 and Merchant Center linked: the data AI needs to decide”
In brief

Automatic bidding and recommendation systems decide based on the data they receive. Properly linking Google Ads, GA4 and Merchant Center gives those systems consistent signals on products, visits and conversions. Inconsistent data across the three tools teaches the system to optimise for what does not matter.

The essentials in a definition

The link between Google Ads, GA4 and Merchant Center is the integration of accounts and data so that bidding and recommendation systems receive consistent signals on products and conversions. It rests on Merchant Center, well-defined key events and smart bidding.

Why the link matters

Merchant Center provides product data, GA4 records on-site behaviour and Google Ads uses conversions and signals to bid. When the tools are linked and use coherent settings (currency, identifiers, events), the system receives a reliable picture. When there are duplications, poorly defined events or misaligned products, it learns from noise.

Smart bidding depends on the quality of the conversions it receives.

What to link and check

Link the Merchant Center account to Google Ads, link the GA4 property to Google Ads and define which key events are imported as conversions. Confirm that product identifiers in the feed match those on the site and in the purchase event, to relate performance and catalogue.

Assign an owner for each link and document them.

Illustrative diagram with 4 numbered steps joined by an orange line, the last one marked as done. It represents: Three tools, one version of the facts

Three tools, one version of the facts

  1. Link accounts and check permissions
  2. Define primary conversions without duplicating
  3. Align product identifiers
  4. Review the integration every quarter

Avoid duplications and conflicts

Define a single primary conversion per action (purchase, lead) and avoid counting the same action from different sources as primary conversions. Align attribution windows and currencies. If you send conversions via API as well as from the browser, use a common identifier to deduplicate.

Regularly check the differences between what platforms report and what the database records.

Large orange quotation marks on a dark background with abstract lines of text, illustrating the quote: “An automatic system is only as smart as the data it receives.”
An automatic system is only as smart as the data it receives.

Ongoing governance

All changes (new events, new campaigns, commerce-platform changes) should go through a simple check: is data still arriving? Do identifiers remain aligned? Keep a change log and review the integration every quarter.

Test the integration after any migration.

Decision table

LinkWhat it enablesTypical error
Merchant Center and Google AdsProduct ads with catalogue dataAccount not linked or feed disapproved
GA4 and Google AdsImport conversions and audiencesDuplicated events
Product identifiersLink catalogue and performanceDifferent identifiers
ConsentMeasurement respecting choicesTags out of control

Common mistakes to avoid

  • Duplicating conversions. It inflates results and misleads optimisation.
  • Linking without checking. Errors go unnoticed.
  • Not documenting. Nobody knows what was done.

How to measure the result

Compare reported conversions and real orders, and track product approval and identifier consistency.

Limits and exceptions

Even with everything linked, attribution is imperfect and part of the data depends on consent. Options and requirements change; confirm current documentation. Integration improves data but does not replace strategy.

Illustrative example

Illustrative example: a store discovers that purchase is counted both by a GA4 event and a Google Ads tag. It defines only one as primary, aligns product identifiers between feed and event and validates against orders. Bidding stabilises and reports match the database better.

In practice: checkpoints

Schedule a monthly check that conversions in Google Ads, GA4 and the database stay within an agreed margin, and investigate immediately when they drift. Keep product identifiers, currencies and tax settings aligned across all three tools, assign owners for each connection and record every change with its date. Test new campaigns, events or feed changes in a controlled way before relying on them for bidding, and keep a list of known limitations of each source so everyone interprets the numbers consistently.

Frequently asked questions

Do I need to link everything?

For advertisers with a catalogue, yes; it is the basis of reliable data for product campaigns.

How do I avoid double counting?

Define single primary conversions and use deduplication identifiers.

Who should manage this?

Someone with explicit responsibility and access to the three tools.

How often should I check?

Quarterly and after any technical change.

What should I link first?

Reliable conversion measurement, then the product feed.

Summary to quote

Link Google Ads, GA4 and Merchant Center with single conversions, aligned identifiers and regular review, so bidding learns from reliable data.

Sources and recommended reading

Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.

Keep reading

Quick contact

Want to talk about your campaigns?

Leave a short note. I'll reply within one working day.