Skip to content
Marketing5 min read

Data Manager Arrives in Google Analytics: Map Your Data Pipelines Before Conversions Count Twice

Google has put Data Manager inside Google Analytics in beta, with a map of every data source and destination. Google's own help page warns that setting up the same pipeline in Analytics and Google Ads can log conversions twice. How to audit before you connect anything new.

Share

On 6 November Google released Data Manager in Google Analytics as a beta. It is a hub in the Analytics admin area for connecting and managing product links, data streams and first-party data imports, with diagnostics for broken connections and a visual map of where a property's data comes from and where it goes.

It is a genuinely useful tool for anyone managing several data sources, and it arrives with a warning from Google that every advertiser feeding offline or CRM data into Google should read before clicking anything: setting up the same data pipeline in both Analytics and Google Ads can log conversions twice.

What Google released

  • Where it lives: a Data Manager tab in the left navigation of the Analytics Admin page, below My preferences. Access needs the appropriate permissions on the property.
  • The data connection map: the property sits in the centre, data sources flow in from the left and destinations flow out to the right. A mini map expands into a full-page view, with filters and path highlighting that trace each connection from source to destination.
  • Diagnostics: data sources with issues show a broken state or red status indicator, with a Fix option on the node, plus Google's data strength guidance on measurement gaps.
  • Connectors: imports for third-party campaign data from platforms including Meta, TikTok, Pinterest, Snap and Reddit, alongside item, user and event data imports.
  • Limits: subproperties and roll-up properties, both Analytics 360 features, do not yet support the Data Manager landing page.

The one-way flow, and why it matters

Google already had a Data Manager inside Google Ads and Google Marketing Platform. The new one in Analytics does not merge with it. Google's help page describes three cases: new connections set up in Analytics send data on to linked Google Ads and Marketing Platform accounts; existing connections built in Google Ads or the Marketing Platform stay managed there; and data imports already configured in Analytics appear in the new Data Manager automatically. Google recommends using Data Manager in Analytics for future connections.

Then comes the warning, set apart on the help page: data ingested through Data Manager in Google Analytics flows downstream to linked Google Ads and Marketing Platform accounts, but not the other way round, and you should not activate an identical pipeline in both interfaces, because that can log conversions twice.

Picture the common case. An agency set up offline conversion uploads from a CRM through Google Ads a year ago. Someone else, seeing the new tab in Analytics and Google's recommendation to use it, connects the same CRM there. The same sales now reach Google Ads by two routes. For a campaign bidding on conversions, that is not a reporting blemish; Smart Bidding now believes the campaign is twice as effective as it is, and spends accordingly.

Where the pipeline is set upWhere the data goesRisk
Google Analytics Data ManagerAnalytics, then on to linked Google Ads and Marketing Platform accounts.Duplicates any identical pipeline already running in Google Ads.
Google Ads Data ManagerGoogle Ads (and Marketing Platform). Not back into Analytics.Analytics does not see it, so the new map will not show it as a source.
Both, for the same dataGoogle Ads receives it twice.Conversions may be counted twice, which inflates reported results and misleads bidding.

The help page does not say how Google detects or reconciles duplicates if they occur, or whether the map flags a pipeline that exists in both interfaces. Prevention is left to the account owner, which in practice usually means the agency.

What only Analytics can take

There is a reason to use the new hub rather than ignore it. Google notes that Analytics supports exclusive data types, such as item data and third-party campaign data, that must be set up through Data Manager in Analytics. If you bring cost and click data from Meta, TikTok, Pinterest, Snap or Reddit into Analytics for cross-channel reporting, this is now where it lives. If you have relied on spreadsheets or a third-party connector to do that, check whether the native import covers your platforms before switching, and keep only one route running, for the same reason as above.

A pipeline audit before you connect anything

  1. List every data source that reaches Google Ads: the Google tag, the Analytics link, offline conversion imports, CRM connections, Customer Match uploads, and any third-party tools. Note which interface each was set up in, and by whom.
  2. Open the new connection map in Analytics and compare. Anything you listed that sends conversions to Google Ads, but appears only in Google Ads, is a candidate for duplication if someone recreates it in Analytics.
  3. Decide one home for each pipeline and write it down. For most accounts that means leaving working Google Ads connections where they are and using Analytics for new connections and Analytics-only data types.
  4. Check conversion actions in Google Ads for duplicates. Two conversion actions recording the same purchase, both set as primary, will be counted by bidding regardless of where the data came from.
  5. Restrict who can create connections. Data Manager respects property permissions, so review who has the access to add one.

Agencies should add one more step: agree with each client which party owns data connections. The most common cause of double counting is not a technical fault but two well-meaning people, on either side of the relationship, each setting up the thing they were told to.

Data Manager in Analytics is a step towards seeing the whole measurement setup in one place, which is exactly what most accounts lack. Used carefully, it will catch broken connections sooner. Used carelessly in the middle of the holiday season, it can make the numbers look better than they are, which is worse than a broken connection, because nobody goes looking for the cause of good news.

Sources

  • https://support.google.com/analytics/answer/9164320?hl=en
  • https://support.google.com/analytics/answer/18107176?hl=en
  • https://ppc.land/google-analytics-data-manager-duplicate-ads-setups-can-log-conversions-twice/

Have a challenge?
Let's turn it into growth.

Start a Project