English
Deutsch
PolskiGA4 Data Manager beta: Audit connections and avoid duplicate conversions
Management Summary
The new Data Manager brings data sources and product connections into one area of Google Analytics administration. A connection map shows how data reaches a property and which linked Google products receive it. This makes a complex measurement setup easier to inspect. Existing connections still need careful review: importing the same data through a second route can count conversions twice. The open beta therefore supports an inventory of the setup rather than replacing business validation.
Contents
- What changed in November
- A connection map is not a business result
- Start with the pipeline that already exists
- A read-only review before the first change
- Accept a change with two kinds of evidence
- What the beta improves in daily work
- Measurement Summary
- Related articles and tools
- Questions and answers
- Sources
Research checked on 11 November 2026.
What changed in November
Google announced Data Manager as an open beta on 6 November 2026. The administration area brings data sources, streams and connected products into a shared view. Its entry appears under Data Manager in Admin. This is useful when a property combines several websites, apps and imports: the setup gains a common overview. Beta features remain subject to change. A missing menu entry alone is therefore insufficient evidence of a fault in event collection.
A connection map is not a business result
The map places sources on the left, the Analytics property in the centre and destinations on the right. It helps answer a concrete question: which system supplies data, and where does that data go next? A visible connection does not establish that revenue or lead quality has been defined correctly. A technically healthy import can still carry incorrect amounts. An initial inventory should therefore record the source, data type, destination, owner and business purpose. This inventory is an editorial recommendation, not an additional Google feature.
Start with the pipeline that already exists
Consider an invented shop that already sends completed orders through a connection managed in Google Ads Data Manager. The same CRM provider appears as an available source in the new Analytics interface. Adding another connection may look like completing the setup, while creating a second route for the same business activity. Google explicitly warns against activating identical pipelines in both interfaces. Existing Ads or GMP connections should continue to be managed in their original location. Existing Analytics data imports appear automatically in Data Manager; this does not require every connection to be recreated.
A read-only review before the first change
A small initial review can list streams and connections, open diagnostics and identify the real origin of each delivery. A red status belongs to a particular connection and does not automatically describe the whole property. Before a correction, the affected period and failure type need to be clear: missing data, late delivery and duplicated data require different investigations. A screenshot records the interface; a usable internal record also includes the observation time and relevant identifiers. Personal customer details are unnecessary for this overview.
Accept a change with two kinds of evidence
After a change, the connection needs a fresh technical status check. A separate business check then compares a small, traceable dataset. For orders, approved internal test transactions with known amounts and currencies provide a practical basis. Matching periods avoids confusing different day boundaries with an import defect. The existing GA4 configuration comparison tool can compare selected settings before and after a change. Its scope does not include a complete backup of Data Manager connections or a validation of Google Ads destination settings.
What the beta improves in daily work
The useful improvement is a shorter route to finding broken paths and their owners. A central interface can simplify maintenance, while each new connection still needs its own business decision. A useful completion record identifies the repaired connection, checked transactions and remaining differences. A green icon alone cannot provide that evidence. Google's documentation currently excludes subproperties and roll-up properties from the Data Manager landing page. Availability therefore needs checking before a larger migration is planned.
Measurement Summary
A practical review can track unresolved connections, known duplicate delivery routes and open diagnostics before and after a change. These are suggested internal measures. This article combines current documentation with an editorial workflow; no production customer property was changed for its preparation.
Related articles and tools
- Compare selected GA4 configuration settings
- Distinguish Measurement Protocol from the Data Manager API
- Reconcile shop and Analytics orders
Questions and answers
Does Data Manager replace Google Tag Manager?
Data Manager organises connections and linked products. Google Tag Manager continues to deploy and control tags. A common overview does not merge those responsibilities.
Do existing imports need to be recreated?
Google says existing Analytics imports appear automatically. Connections already managed in Google Ads or GMP should continue to be managed there.
Does new data automatically flow both ways?
The documented direction runs from Analytics to linked Google Ads and GMP accounts. This does not promise a matching return flow from those products.
Does a green connection status prove accurate revenue?
Connection health describes the technical route. Amount definitions, currency, duplicates and completeness require a separate business comparison.
Sources
Related articles
