Google just slipped three things into GA4: a new tab, a recommendation and a warning. The tab is Google Analytics Data Manager, in beta since November 6, 2026. The recommendation: set up all your future data connections there. The warning, spelled out in the official help: activate the same pipeline in both GA4 and Google Ads and your conversions can be logged twice. Three weeks before Black Friday, that’s exactly the kind of fine print that ends with Smart Bidding chasing sales that never happened.
This article covers what the tab actually contains, what it doesn’t do yet, and then an audit method built on the connection map, plus a simple rule for deciding where each pipeline should live.
Google Analytics Data Manager: What’s in the New Tab
If you’ve read our Google Ads Data Manager guide, the idea will sound familiar: one hub to connect your first-party data instead of a patchwork of imports. On September 10, 2026, Google said it was bringing that hub to Google Analytics and Display & Video 360. The GA4 side is now live, according to the What’s new in Google Analytics page, which describes a unified hub in the admin console for product links, data streams and first-party data, with diagnostics and connection health monitoring.
You’ll find it under the property’s Admin, in a “Data Manager” tab in the left navigation. The dedicated help article mentions “appropriate permissions” on the property without saying which ones: if you can’t see the tab, check your role before blaming the beta.
The Data Connection Map
This is the genuinely new part. Your property sits in the middle, data sources on the left (Google Tag Manager, a CRM, offline files, partner sources), destinations on the right (Google Ads, Google Marketing Platform). You can switch between a mini view and a full-page view, hover or click a node for details, filter by name and, above all, highlight a path from a source to its destination.
For a consultant inheriting a property, that’s a huge time saver. Until now, piecing together “who sends what, where” meant clicking through five admin screens and two Google Ads accounts. The map gives you a first answer at a glance. Only a first answer, as we’ll see.
Diagnostics and the Fix Button
A broken source shows up in a broken state with a red indicator. Click it, read the issue, and a “Fix” button offers a correction. Google also built in the Data Strength guide, meant to spot measurement gaps and suggest actions. Useful, but remember what a Google metric that scores the data you send to Google is worth: we covered that with the Data Strength Uplift metric.
The Connections List
Next to the map, a list view separates data streams (web and app, with an add stream button) from connected products (product links and data imports). Third-party campaign data imports (Meta, TikTok, Pinterest, Snap, Reddit) are now set up here: if your costs aren’t showing up, our GA4 campaign data import article walks through the usual causes.
What’s Still Missing
| Item | Status as of November 8, 2026 | What it means |
|---|---|---|
| Status | Beta, no exit date announced | The interface may still change |
| Subproperties and roll-up properties | Not supported “currently” | Audit from the source property |
| Required permissions | Not specified by Google | Test with an administrator account |
| BigQuery, offline conversions | Not mentioned in the GA4 help | Don’t assume they appear on the map |
| Duplicate detection | Not mentioned | The audit stays manual |
That last row is the one that matters. As PPC Land pointed out on November 8, 2026, Google doesn’t say how it detects or reconciles duplicates, or whether the map flags them.
GA4 vs Google Ads Data Manager: Who Does What
Two Data Managers, one name, two interfaces. No wonder people are confused. Here’s what the documentation supports:
| Data Manager in Google Ads | Data Manager in GA4 | |
|---|---|---|
| Where | Google Ads, Tools, Shared data | GA4 property Admin |
| Availability | Generally available since April 2026 | Beta since November 6, 2026 |
| Data direction | Into Google Ads | From GA4 to Google Ads and GMP, not the reverse |
| Google’s recommended use | Keep managing existing connections | Create future connections |
The key sentence in the help is that last row: Google recommends Data Manager in GA4 for future connections, while existing connections stay managed in Google Ads or GMP. In other words, throughout the transition you’ll have pipelines on both sides. That’s exactly where duplicates are born.
The Duplicate Conversions Risk
How It Happens: One Pipeline, Active on Both Sides
Picture two pipes filling the same bucket. Your CRM sends closed deals into Google Ads through the Google Ads Data Manager, set up last year. This month, someone discovers the tab in GA4, follows Google’s advice and connects the same CRM on the GA4 side, activated toward the same Google Ads account. Result: every deal lands in Google Ads twice, through two different paths.
The help is blunt about it: don’t activate an identical data pipeline in both interfaces, as this can log conversions twice. And since data doesn’t flow back from Google Ads to GA4, the GA4 map only sees its half of the problem.
Setups at Risk
Ranked by risk, based on what I see in audits:
- A CRM or offline import rebuilt on the GA4 side. The scenario above. The most likely one in the coming weeks, because it follows Google’s recommendation to the letter.
- A partner source connected twice. A customer data platform connected to the Google Ads Data Manager, then again to GA4 “so Analytics has the data too”, with activation toward Google Ads on both sides.
- The classic duplicate, nothing new about it. The Google Ads conversion tag plus the GA4
purchasekey event imported into Google Ads, both set as primary. Not the pipeline duplicate Google is warning about, but by far the most common one, and you’ll run into it during the audit anyway. Our Google Ads conversion tracking audit checklist explains how to spot and fix it.
Audit Your Connections With the Map, Step by Step
Budget about an hour per property. The point is to cross-check what GA4 sees against what Google Ads sees, because neither interface sees everything.
- Capture the GA4 map. Open Data Manager in full-page view and, for each source, note its type, the property and stream involved, and its destinations. One screenshot per highlighted path is enough.
- List the Google Ads connections. In the Google Ads Data Manager, note every connected source and what it activates (conversions, Customer Match, enhanced conversions for leads).
- List the conversion actions. In Google Ads, All conversions tab, export the actions with their source, primary or secondary status, and 30-day volume.
- Cross-check. For each business event (purchase, qualified lead, closed deal), count how many paths bring it into Google Ads. More than one path into a primary action: probable duplicate.
- Check the volume. Compare the suspect action’s conversion count with your back office or CRM over the same period. A ratio close to 2 is a confession.
- Handle the red alerts. Review the diagnostics while you’re there, but read what the Fix button proposes before clicking: an automatic fix that reactivates a pipeline you switched off on purpose creates the very problem you’re hunting.
If you also send conversions through an API (Measurement Protocol or the Data Manager API), add them to the cross-check: they won’t necessarily appear on the map. Our Measurement Protocol vs Data Manager API comparison helps you figure out which one you use and where it lands.
The Decision Rule: Where to Set Up Each Pipeline
My take: don’t migrate anything in a hurry. Google’s recommendation is about future connections, and a beta is not the place to move a pipeline that feeds your bidding right before the biggest peak of the year.
| Situation | Where to set it up | Why |
|---|---|---|
| Existing pipeline in Google Ads that works | Leave it in Google Ads | That’s Google’s own advice, and moving it gains nothing |
| New connection GA4 also needs (CRM, cost imports) | GA4 Data Manager | One source, visible on the map |
| New connection only useful for bidding | Either, but on one side only | The golden rule: one path per event |
| Moving a Google Ads pipeline to GA4 | After the peak, switching off the old one the same day | Never two active pipelines in parallel |
And document it. A shared sheet with “event, source, path, primary action” stops the next intern from following Google’s advice without knowing what already exists on the other side.
Pre-Black Friday Checklist
- The Data Manager tab is visible on the property (if not, check permissions or the property type).
- The connection map is captured, path by path.
- Google Ads Data Manager connections are listed.
- Each business event reaches Google Ads through a single path into a primary action.
- Primary action volumes match the back office over 30 days.
- No new pipeline was activated in GA4 if it already exists in Google Ads.
- Red alerts are handled, with no blind clicks on Fix.
- A connection freeze is in place until the holidays are over.
Data Manager in GA4 is good news: for the first time, you can see at a glance where a property’s data comes from and where it goes. But a map isn’t an audit. Until Google flags duplicate pipelines itself, it’s on you to make sure only one pipe fills each bucket.