Blog

GA4 Data Manager: how to avoid counting conversions twice

Published JAYC Consultancy5 min read

  • Tracking & Analytics
  • Google Ads
  • GA4
  • Conversion Tracking

A new tool in Google Analytics promises a clearer view of your data connections. Before adding anything, though, we recommend checking what is already connected.

PPC Land's report highlights a warning about duplicate pipelines. We checked the underlying Google documentation: both the beta launch and the warning are confirmed by Google's own pages. This is a setup risk to review, not a reason to panic or disconnect working tracking.

What is Data Manager in GA4?

Google's release notes date the launch of Data Manager in Google Analytics, in beta, to 6 November 2026. It brings product links, data streams and first-party data connections together in the Admin console, with connection health monitoring and diagnostic alerts.

The Data Manager help page describes a connection map showing sources feeding into your Analytics property and destinations receiving its data. Below it, a list shows data streams, product links and import connections.

For a small business, we would use this as a starting point for understanding where data comes from and where it goes. It is not an instruction to rebuild every existing connection.

Why can double counting happen?

Google's warning is specific:

“Don’t activate an identical data pipeline in both interfaces together, as this can log conversions twice.”

The same help page explains that data ingested through Data Manager in Analytics flows downstream to linked Google Ads and Google Marketing Platform accounts, not the other way round. Creating an identical pipeline in both interfaces therefore risks recording the same conversions twice.

Google distinguishes three situations:

  • Existing Google Ads or Google Marketing Platform connections: continue managing them there, without duplicating them in Analytics.
  • Existing Analytics data imports: these automatically appear in Data Manager.
  • Future connections: Google recommends using Data Manager in Analytics.

We would check which situation applies before clicking “Connect Product”. The launch does not mean an existing Ads connection needs a matching Analytics connection.

There is also a related bidding risk to review: separate conversion actions representing the same business outcome. Google's GA4 conversion guidance says Analytics-based actions are set to secondary to prevent counting the same event twice for bidding. Check their actual settings rather than relying on defaults.

Why it matters for bidding and reporting

Smart Bidding learns from conversion signals. Google's primary and secondary actions guidance warns that incorrect settings can prevent effective optimisation because the algorithm relies on those signals.

If duplicate conversions feed the goals a campaign bids towards, Smart Bidding is learning from an inflated picture of success. That is the practical implication of Google's guidance, not a claim that every duplicate connection will automatically change bids or spending.

The distinction matters:

  • Primary actions appear in “Conversions” and are used for bidding when their standard goal is used by the campaign.
  • Secondary actions appear in “All conversions” and normally serve observation only.
  • Custom goals are an exception: included actions are used for bidding regardless of their primary or secondary setting.

Moving an overlapping action to secondary can therefore protect standard-goal bidding without removing it from “All conversions”. We should still explain the overlap when reporting totals.

Not every discrepancy is duplication. Our guide to why GA4 and Google Ads report different numbers explains other reasons the platforms may disagree.

Your checklist before connecting anything new

We recommend recording the answers in a simple tracking inventory, with a named owner for each connection.

  • Map the existing routes. Review Analytics Data Manager and existing Google Ads connections. Record the source, destination and business event each route measures. Do not recreate an Ads pipeline simply to make it appear in Analytics.
  • Check GA4 links and conversion imports. Confirm which Analytics property is linked to which Ads account, then list the events or key events shared as Ads conversions. Google's setup guidance requires the accounts to be linked.
  • Compare imports with native Ads tracking. Check whether a GA4-based action and a Google tag or Google Ads conversion tracking tag represent the same purchase or enquiry. Treat overlap as something to investigate, not proof that both should be deleted.
  • Review primary and secondary settings. In Google Ads, review each action's optimisation setting and the standard goals used by campaigns. Check custom goals separately: “secondary” does not exclude an action from their bidding.
  • Include offline and enhanced conversions for leads. List CRM connections, file uploads and API routes. Google's upgrade guide allows existing offline actions to be upgraded; do not assume an upgrade always needs a separate action.
  • Check identifiers and event definitions. Google's offline import guidelines describe duplicate detection using the identifier, conversion name, date and time. Confirm these reflect the actual event, rather than assuming all routes are interchangeable.
  • Verify purchase transaction IDs. Google's transaction ID guidance says repeat conversions with the same ID are deduplicated within the same conversion action. IDs must be unique per transaction; a fixed placeholder can cause undercounting.
  • Review diagnostics and validate reporting. For imports, Google recommends “All conv. (by conv. time)” for validation. For supported multi-source website conversions, review diagnostics for missing IDs or overcounting alerts before trusting the combined data.

Two sources are not always a mistake

Google also documents a legitimate multi-source conversions beta: supported Google Ads website conversion actions can combine tag data with an additional source. Matching transaction IDs within the same action prevent double counting.

That is different from activating identical Analytics and Ads pipelines. Google's FAQ also says imported Analytics conversions are not supported by this particular multi-source feature. We should not assume its deduplication rules protect a different configuration.

The aim is to understand each route, not remove useful measurement indiscriminately.

Need a second pair of eyes?

Before connecting another feed, we would agree which business outcomes matter, which actions measure them and which signals guide bidding.

If you would like help, ask JAYC Consultancy about a conversion tracking health check. We can help you review your connections and conversion goals, with clear recommendations rather than unnecessary rebuilding.

Sources

Back to blog

Want this sorted for your own tracking?

A free 30-minute call. We'll look at your tracking with you and tell you what's broken and what to fix first.

Book a free call See all services