CRO and Conversion Strategy

Use GA4 Data Manager without counting the same lead twice

 ·  13 min read

A receptionist feeds a marked enquiry envelope into a machine while a matching envelope is held above the line.
In this article

GA4 Data Manager puts data streams, first-party imports and product links in one place in Google Analytics Admin. Keep your working CRM import in Google Ads. Google warns that turning on an identical pipeline in both products can log conversions twice.

Google announced the Data Manager beta on November 6, 2026. The connection map shows where data starts, which property receives it and where it can go next. Start there when your CRM and Ads reports disagree about the leads you paid for. Google Analytics release notes

Decide where the data should enter

Keep a working Ads or Google Marketing Platform connection where it already runs. Google recommends starting new supported first-party connections in GA4. Existing GA4 imports appear in the new hub automatically. Pick the entry point based on who needs the data and which system already sends it.

What you have What to do
A CRM connection already sends qualified leads directly to Google Ads Manage it in Google Ads. Document the lead stage and conversion action before adding anything in GA4.
GA4 already imports the data you need Find the existing import in Data Manager and check its status. Keep its source and schedule in place.
GA4 and Google Ads both need a new first-party dataset Check that GA4 supports the data type. Set it up from GA4 and verify how the linked Ads account uses it.
GA4 needs item data or third-party campaign data Configure that import in GA4. Review the required fields and verify the outcome in the matching report.

Data you import through Data Manager in GA4 can flow downstream to linked Google Ads and Google Marketing Platform accounts. A CRM import made directly in Ads does not flow back into GA4 through this setup. The products can exchange other data through their link. This direction rule concerns the data import. Google’s Data Manager guide

Draw the event paths you already use before touching a connector. Include the website tag, any server integration, scheduled uploads, and Ads conversion imports. Write down the action that triggers each one. Two connectors can have different names and still send the same enquiry. The path matters more than the name on the card.

A receptionist holds one enquiry beside a customer file, a signal lamp and an advertising tray.

Read the connection map from left to right

Open Admin and select Data Manager under My preferences. Expand the connection map to see the source, import type, property or stream, and export destination. Hover over a node to trace its path. Open its details when you need to confirm which account, stream or data source a connection refers to.

The expanded map has four columns. The first shows where data originates, such as a tag, CRM or file. The second shows the data import type when that connection uses one. Product links bypass this column. The third shows the Analytics property and its web or app streams. The fourth shows connected products receiving Analytics exports. Google’s Data Manager guide

Start with one path, such as the website enquiry form. Check the source tag or stream ID against the property your team uses for its lead report. Follow it to the right and note any linked Ads account. Then compare that picture with the conversion actions listed in Ads. A link between products gives them a way to share data. Check which event each action counts before treating the link as proof that a lead arrived or affected a bid.

Use the lists under the map when you need to inspect one connection. Data streams contains the web and app streams. Connected products contains links and import connections. For a new source, choose Connect Product, select the source and how you intend to use it, then begin setup. Read the fields and destination before you save. If a colleague already connected the source, open its details and check its scope first.

Check access and fix the earliest break

If Data Manager is missing, confirm the property and your access before opening a second connection. Google calls this an open beta and says its landing page currently excludes subproperties and roll-up properties. If a node shows an error, follow that path from the source and check the first broken connection.

To start a GA4 data import, you need Editor access or higher at the property level. To link Google Ads to Analytics, the account making the link needs Editor or Administrator in GA4 and administrative access in Ads. Ask someone with those rights to make the change if you only review the reports. GA4 import permissions · Google Ads linking permissions

Click a red or broken source node. Its summary card shows the issue and can offer Fix. Read the message before you change the connection. For example, check whether the account that authorized a connection can still read the source. Then verify that the import receives the field it expects and sends it to the intended property. If the source has fresh rows and the destination is empty, test the join or event rule before you reconnect the account.

Use the other end of the map to diagnose a different problem. If the original form record and the GA4 event both exist, inspect the Ads conversion action and goal. Adding another copy of the feed at the source gives you another variable to investigate. Our lead tracking cleanup guide covers matching the web record to the next sales step.

A technician finds an unplugged connector between a customer form and a reporting gauge.

Give each lead stage its own job

Use the saved form receipt or CRM record to decide whether a new enquiry exists. Then decide what counts as a qualified lead and what counts as a sale. Report these stages separately. If a campaign bids for qualified leads, check which Ads action represents that stage and which campaign goals use it.

Use generate_lead to record a successful enquiry, qualify_lead when a lead meets your criteria, and close_convert_lead when a qualified lead becomes a customer. Use the transition that happened. If a sales rep edits a contact’s phone field, the lead has not qualified again. Google’s recommended lead events

A key event marks an action you want to track in Analytics. An Ads conversion action can use an eligible Analytics event and has its own Ads settings. A report of enquiries and an Ads report for attributed qualified leads answer different questions. Compare actions at the same stage and use the same date window before investigating a difference. Google’s key event and conversion guide

Check both the action setting and the campaign goal in Google Ads. Google usually treats secondary actions as observation only and shows them in All conversions. A secondary action inside a custom goal can still affect bidding. Keep synthetic traffic outside live goals. Review the campaigns that would use a new action before you change which one is primary. Google Ads conversion actions

A form tag and CRM feed may both have a purpose. Keep the form event if it measures the initial enquiry and the CRM event if it records a real qualification. Stop and inspect the setup if both sources claim to count the same qualification. Look at how offline conversion tracking works before changing a feed that already informs bids.

Choose the Admin interface or a server integration

Use the Admin hub to inspect, connect and troubleshoot supported data sources. Use the Data Manager API when an implementation needs to send events from a server. Google added GA4 support for server-to-server events in May 2026. The November release adds an Admin view for connections, streams and imports.

If you use a working tag or Measurement Protocol integration, map its destination before deciding whether to change it. Google describes the Data Manager API as an alternative for supported server events. It accepts recommended and custom events for GA4 web and app streams, subject to event restrictions. Check the identifiers and destinations your chosen event needs. Google’s May release notes · Developer guide

For an integration, keep the destination, event name, source time and internal event identity together. The ingestion endpoint returns a request ID so you can look up the submission. Use the record-level results to check what happened at the destination and which rows need attention. Ingestion endpoint · Request status and diagnostics

For events sent under its documented GA4 API setup, Google uses transactionId to deduplicate the same event in the same property. Analytics keeps the first matching copy. Give each lead stage one sender and give each event a stable ID for retries. Verify the exact route you plan to run, including Google Ads action IDs and goals. The GA4 API currently accepts leadId and matchId without attributing events that rely on those identifiers alone. GA4 API event deduplication and attribution

Google puts its separate API feature for supplementing tag or Firebase events on an allowlist. If you bid on GA4 conversions in Google Ads, its multi-source API events sent to web streams stay out of bidding during a 14-day trial. Existing Google tag events and API events sent to app streams fall outside that trial restriction. Google’s multi-source event guide

Keep personal details out of ordinary Analytics fields, including URLs and event parameters. Use an opaque internal reference when you need to compare a test with a saved record. For any supported use of customer identifiers, check Google’s requirements and your consent setup before sending them. User-provided data requirements · Analytics privacy guidance

Trace one test enquiry before changing bids

Use one synthetic enquiry to check a proposed connection in a test property or another setup isolated from live bidding. Check that the form saves one record and that the CRM qualifies it once. Then verify the intended event and destination. Repeat the same submission callback or job delivery to check how a retry behaves.

Suppose a B2B team accepts a test demo request and saves receipt QA-104. The browser should fire one generate_lead when the form confirms success. The test CRM adds one qualification after the sales check. That yields one enquiry and one qualification in the test records. If the qualification callback runs a second time, the intended result is still one qualification for that record.

Check Expected result for QA-104 If the result differs
Form and CRM One saved enquiry and one qualification Check the form success callback, CRM rules and job retry.
GA4 test event One enquiry and, if this path sends it to GA4, one qualification event Inspect event names, stream and repeat sends.
Destination setup One intended Ads qualification action, outside live bidding in the test Compare action IDs and confirm which campaign goals use them.
Retry The same qualification keeps its original identity Fix the retry before sending a backlog or switching goals.

Use DebugView and Tag Assistant to inspect the browser event. Use connector records or API diagnostics for server sends. Google says Analytics processing can take 24 to 48 hours. During that time, label a missing report row as pending and check the original request before considering a resend. DebugView · GA4 data freshness

For a live cutover, record the old schedule, the new schedule and the boundary between them. Keep the original lead log and the last delivery record for each path. Compare website receipts, CRM stages and the Ads actions you expect to see. Review CRM duplicate cleanup rules if merges or repeated stage changes make that comparison hard.

Check the quality of the count as well. One form record and one event can agree while the enquiry itself comes from a bot or falls outside your sales criteria. Log test receipts and show legitimate enquiries separately from Google Ads spam leads. Protect that distinction when you switch sources.

The same mark connects a phone form, a saved receipt and a confirmation light.

Use earlier GA4 changes where they help

The beta brings connections together. It leaves the reporting rules and import requirements in place. If you import campaign costs, check currency mapping and use the campaign data import validation report. If you track AI traffic in GA4, use acquisition reports for source data and compare lead events with saved submissions.

Google added a required currency field for campaign cost imports in July 2026 and introduced a campaign import validation report in August. Use it to find campaigns missing cost, click or impression data. If costs arrive and lead counts still disagree, inspect the conversion events and goals on their own. Google’s campaign import updates

The AI Assistant channel appears in GA4’s default grouping for recognized assistant traffic. Google classifies AI Overviews and AI Mode under Organic Search. If someone asks which assistant visits brought enquiries, use Traffic acquisition and inspect the session source before looking at lead records. Google’s default channels

Pick one lead stage the team uses to judge performance. Trace it from the saved record to every reporting or bidding destination, then write down which path owns it. Start there before connecting a second source. If the saved forms and campaign reports disagree and you need help tracing them, ask for an analytics and funnel audit.

FAQ

Where do I find Data Manager in GA4?

Open the GA4 property, select Admin and look for Data Manager under My preferences. If it is missing, verify the selected property and your access. Google says the open beta can change and the Data Manager landing page does not currently support subproperties or roll-up properties.

Should I move an existing CRM connection from Google Ads to GA4?

Keep a working connection in Ads if it already delivers the intended data. Google recommends starting new supported first-party connections in GA4 and keeping existing Ads or Google Marketing Platform connections in their current product. Document the event, destination and goal first if you have a business reason to change the route.

Can a Google Ads CRM import bring qualified leads into GA4?

An import set up in Google Ads does not flow back into GA4 through this Data Manager setup. A supported import that starts in GA4 can flow downstream to linked Ads or Google Marketing Platform accounts. Check the specific data type and the destination’s settings before assuming it can use the event.

Can I use the Data Manager API with an existing website tag?

Google allows some accounts to supplement supported tag events through its allowlisted multi-source API feature. For ordinary lead tracking, choose one sender for each stage. Verify that route and its identifiers with a controlled test. Review the Ads conversion actions separately before changing your bids.

Why do I see two conversions for one lead?

Check whether your form fired twice, whether a CRM retry sent the same stage again, and whether two Ads actions both count that stage. Compare a saved lead record with the event and conversion actions. A submitted enquiry and a later qualification can both be valid when you report them separately.

Free website and CRO audit

Find where your website loses enquiries

We check where visitors drop off and identify page changes to test, then send the fixes in priority order.

Your data is safe. We never share details without permission.

Free growth audit

Find out what's costing you leads

We check your site, ads and tracking and send the fixes that matter most within 24 hours. Your first 15 days are free on a new plan.