{"id":30372,"date":"2026-11-11T11:26:00","date_gmt":"2026-11-11T10:26:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=30372"},"modified":"2026-11-11T13:57:00","modified_gmt":"2026-11-11T12:57:00","slug":"ga4-data-manager-beta-audit-connections","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/digital-analytics\/ga4-data-manager-beta-audit-connections\/","title":{"rendered":"GA4 Data Manager beta: Audit connections and avoid duplicate conversions"},"content":{"rendered":"

Research checked on 11 November 2026.<\/em><\/p>\n

What changed in November<\/h2>\n

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.<\/p>\n

A connection map is not a business result<\/h2>\n

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.<\/p>\n

\"Inventory
Schematic connection map \u00b7 not a screenshot of Google's interface<\/figcaption><\/figure>\n

Start with the pipeline that already exists<\/h2>\n

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.<\/p>\n

A read-only review before the first change<\/h2>\n

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.<\/p>\n

Accept a change with two kinds of evidence<\/h2>\n

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.<\/p>\n

\"A
Editorial workflow \u00b7 connection health and business data are separate<\/figcaption><\/figure>\n

What the beta improves in daily work<\/h2>\n

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.<\/p>\n

Measurement Summary<\/h2>\n

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.<\/p>\n

Related articles and tools<\/h2>\n