GA4 Data Manager can log one conversion twice in Google Ads

Google Analytics now has its own Data Manager. It launched in beta on 6 November, in the GA4 admin, as one place to connect data streams, product links and first-party data such as CRM records and offline files. The help page for it carries a warning that matters more than the launch: data that comes in through GA4 flows on to linked Google Ads accounts, and an identical pipeline set up in both GA4 and Google Ads “can log conversions twice”.

What Google launched

The help page describes Data Manager as a hub with a data connection map: your sources on the left (Google Tag Manager, a CRM, a Google Ads link, an offline file), the GA4 property and its streams in the middle, and the products that receive GA4 data on the right. A broken source shows a red status indicator, and some issues can be fixed from the map. Existing GA4 data imports appear in it automatically.

Three rules on the page decide how you use it:

• Data goes one way. What comes in through Data Manager in GA4 flows on to linked Google Ads and Google Marketing Platform accounts. Data that comes in through Google Ads does not flow back to GA4.
• Existing Google Ads pipelines stay where they are. Google says to keep managing connections that already exist in Google Ads or GMP there, “without duplicating these connections in Google Analytics”, and to set up new ones in GA4.
• Some imports are GA4-only. Item data and third-party campaign data, meaning cost, clicks and impressions from other ad platforms, must be set up through Data Manager in GA4.

Subproperties and roll-up properties do not get the Data Manager page.

The read

The duplicate sits between two tools, and neither map shows both. The GA4 map shows what is connected to the GA4 property. The CRM upload or offline conversion feed that a team set up in Google Ads’ own Data Manager is managed in Google Ads, and the GA4 help page tells you to leave it there. So a person who connects the same CRM in GA4 sees a clean map in GA4. Google Ads then gets the same sale twice: once from its own pipeline, and once through GA4.

Google’s guard covers bidding, not every report. Google Ads sets conversion actions based on GA4 key events to secondary when the account already has goals from a GA4 property, “to prevent counting the same event twice for bidding”. Secondary actions are not used for bidding, but they are still counted in the All conversions column, and an action in a custom goal is used for bidding even when it is secondary. A report built on All conversions, or a custom goal that includes both actions, still counts the sale twice.

An event import cannot be undone by deleting it. GA4 processes imported events “as though they were collected” by its own tags. Deleting the data source does not delete the events. You need a data-deletion request. Google’s campaign data import page has the same warning: delete overlapping datasets before you connect a new cost source, “or risk duplicate data entries”. A test import into a production property is a permanent test.

Nothing on the Data Manager page says GA4 and Google Ads deduplicate a sale that reaches Google Ads by both routes. The page’s answer is to build the route only once.

What to do

1. List what already reaches Google Ads directly: offline conversion imports, enhanced conversions for leads, CRM connections in Google Ads’ Data Manager. Do not connect the same source in GA4.
2. Check the All conversions column for a conversion action whose count roughly matches another action’s. A GA4-based action and a direct import of the same sale look like that.
3. Test event imports in a test property first. In production, you can only remove them with a data-deletion request.

Data Manager makes it easy to send the same sale to Google Ads from two places. Before you pick one, decide which tool should count it. Attribution is two jobs explains what GA4 counts for and what Google Ads counts for, and why the two answers differ.