Google Analytics Conversion Tracking: The GA4 Import Trap

Google Analytics Conversion Tracking: The Import Trap

Four weeks ago a fintech startup forwarded me a screenshot from their Google Ads dashboard. Their cost-per-acquisition had dropped 35 percent overnight. No campaign changes, no budget increase, no new creative. The founder was thrilled. I was suspicious.

It took ten minutes to find the problem. Their marketing manager had linked GA4 to Google Ads and imported the GA4 generate_lead key event as a conversion action -- without realizing a native Google Ads conversion tag already fired on the same form. Every lead was counted twice. Smart Bidding saw double the conversions at half the CPA and started spending aggressively on keywords that were not actually converting.

This is not an unusual situation. Roughly one in three accounts I audit that use both GA4 and Google Ads has some form of double-counting between imported GA4 conversions and native Google Ads tags. The fix is usually straightforward. The damage from months of corrupted bidding data is not.

This post walks through when importing GA4 conversions into Google Ads makes sense, when it does not, and how to set up google analytics conversion tracking so your numbers stay clean.

Why GA4 and Google Ads Count Conversions Differently

Before deciding whether to import, you need to understand what each platform is actually measuring. They are not interchangeable views of the same data.

Google Ads uses its own data-driven attribution model scoped entirely to Google Ads clicks and impressions. It counts conversions on the date of the original click. It includes view-through conversions from Display and YouTube. And it applies its own conversion modeling to estimate conversions lost to consent denial.

GA4 also uses data-driven attribution, but across all traffic sources -- organic, direct, email, social, and paid. It counts conversions on the date the event occurred, not the click date. It has no view-through window. And it applies a separate behavioral model for non-consented users.

The result: the same conversion event appears in both platforms but is attributed differently, counted on different dates, and modeled with different assumptions. I covered the full breakdown in GA4 vs Google Ads Conversions: Why They Don't Match. The takeaway: importing a GA4 conversion into Google Ads does not give Google Ads "better" data. It gives Google Ads GA4's version of the data -- built for cross-channel analysis, not bid optimization.

How to Link GA4 to Google Ads and Import Conversions

If you decide importing is the right path (I will cover when that makes sense below), here is the setup.

Step 1: Link the accounts

In GA4, go to Admin > Product links > Google Ads linking and connect your Google Ads account. Both accounts need to share the same Google account with admin access, or you need the link permissions on both sides.

Step 2: Mark the event as a key event in GA4

Under Admin > Events, find the event you want to import and toggle "Mark as key event." This is the step people forget most often -- I find unmarked events in about a third of audited properties. Without this toggle, the event is invisible to Google Ads imports. For guidance on which events to mark, see GA4 Recommended Events: Which Ones to Implement.

Step 3: Import the GA4 conversion action in Google Ads

In Google Ads, go to Goals > Conversions > Summary, click the plus button, and select Import > Google Analytics 4 properties. Choose the key event you want to import. Set whether it is a primary (feeds into bidding) or secondary (observation only) conversion action.

Step 4: Verify the import

Wait 24-48 hours. GA4 data can lag up to 48 hours before Google Ads picks it up. Check that the conversion action moves to "Recording conversions" and that the numbers are in the expected range.

That is the mechanical process. Now for the harder question.

When Importing GA4 Conversions Makes Sense

There are legitimate scenarios where using GA4 as your google analytics conversion tracking source for Google Ads makes sense.

You cannot install a native Google Ads tag

Some platforms -- locked-down CMSes, third-party booking engines, embedded iframes -- make it impossible to fire a Google Ads conversion tag on the conversion page. If GA4 already tracks the event, importing it into Google Ads is better than having no conversion data at all.

You need cross-platform consistency for reporting

If your reporting stack runs entirely through GA4 and BigQuery, importing the GA4 key event means the conversion definition is identical in both places. One event, one counting method, one set of parameters. For teams that struggle with dashboard reconciliation, this simplifies things.

You track micro-conversions for secondary actions

Importing GA4 events as secondary (observation-only) conversion actions is low risk. These do not feed into bidding. They give you visibility in Google Ads reporting without affecting optimization.

When You Should Not Import GA4 Conversions

In most accounts I work with, the answer is: do not import GA4 key events as primary conversion actions for bidding. Here is why.

You already have a native Google Ads conversion tag

This is the double-counting scenario I opened with. If a native Google Ads conversion tag already fires on the same action, importing the GA4 event creates a second primary conversion. Google Ads adds them together. Your conversion volume doubles. Your CPA halves. Smart Bidding gets a distorted signal.

The fix seems obvious -- remove one. But I have seen teams spend months debugging CPA anomalies before realizing both were active. Google Ads does not warn you about overlap between native tags and imported GA4 events.

You need Smart Bidding to perform well

Native Google Ads conversion tags give Smart Bidding the most complete signal. They use Google Ads attribution (scoped to ad interactions), Google Ads conversion modeling (calibrated on Google Ads data), and report on click date (which is what the bidding algorithm expects). Imported GA4 conversions use GA4 attribution, GA4 modeling, and event-date reporting. Google's own best practices recommend using the Google Ads tag or Google tag for conversion tracking rather than importing from analytics.

In practice, I have seen Smart Bidding take two to three weeks longer to exit the learning phase when fed imported GA4 conversions versus native tag data. A campaign that drove 50 conversions according to the native tag might show 30 in GA4 because GA4 gave partial credit to organic and email. Smart Bidding sees fewer conversions, bids conservatively, and underspends on your best campaign.

Your conversion cycle is longer than seven days on Safari

Safari's ITP caps JavaScript-set first-party cookies at seven days. If a user clicks your ad on Monday and returns eight days later to convert, the GA4 cookie is gone. GA4 attributes that conversion to direct traffic. The Google Ads native tag has better recovery mechanisms -- the GCLID persists independently, and enhanced conversions can match on hashed email. An imported GA4 event inherits GA4's cookie-dependent attribution gap.

The Decision Framework

Here is how I advise clients.

Scenario	Recommendation
Native Google Ads tag already in place	Do not import GA4 events as primary conversions
Cannot install native tag	Import GA4 key event as primary conversion
Want GA4 events visible in Google Ads reports	Import as secondary (observation-only)
Running Smart Bidding (tCPA, tROAS)	Use native tag for primary conversion
Need one source of truth across all channels	Use GA4 for reporting; native tag for bidding

The guiding principle: use Google Ads data to optimize Google Ads. Use GA4 to evaluate your marketing mix. Use your CRM or payment processor to know what actually happened.

How to Avoid Double-Counting

If you want both a native tag and a GA4 import active -- for example, the native tag for bidding and the GA4 event for cross-referencing -- set the GA4 import as a secondary conversion action. Secondary conversions appear in reports but do not feed into bidding. This gives you visibility without corrupting Smart Bidding.

To check for existing overlap:

1. In Google Ads, go to Goals > Conversions > Summary.
2. Look at every conversion action with "Primary" status.
3. If you see both a native tag-based action (source: "Website") and an imported GA4 action (source: "GA4 property") tracking the same business event, you have a double-counting problem.
4. Demote the GA4 import to secondary, or remove it entirely.

If your conversion data has been double-counted for weeks or months, the historical data is compromised. Smart Bidding learned from inflated numbers. Expect a re-learning period of two to four weeks after the fix. If you are not sure whether your setup has this problem, I can audit it for you.

What About Server-Side Google Ads Conversion Tracking?

If your concern with native tags is reliability -- ad blockers suppressing them, consent banners delaying them, Safari cookies expiring -- the better answer is not to fall back to GA4 imports. It is to move the native Google Ads tag server-side.

A server-side Google Ads conversion tag fires from your own server, not the visitor's browser. It bypasses ad blockers, sets first-party cookies from the server (extending lifetime past Safari's seven-day cap), and gives you full control over what data is sent. Native Google Ads attribution with infrastructure-level reliability.

The setup requires a server container, domain configuration, and careful data layer implementation -- but for accounts spending above a few thousand per month, the measurement improvement pays for itself within one billing cycle.

A Quick Audit Checklist

Run these checks in ten minutes to see if your GA4-to-Google-Ads setup is clean.

1. Count your primary conversions. In Google Ads, go to Goals > Conversions > Summary. Filter by "Primary." If two or more actions track the same business event (one native, one imported from GA4), you are double-counting.
2. Compare conversion volumes. Pull last month's conversions from Google Ads, GA4, and your CRM. If Google Ads shows significantly more than your CRM, check for duplicates. If GA4 shows significantly fewer than your CRM, your google analytics conversion tracking has gaps -- likely consent or cookie related.
3. Check the source column. Each conversion action in Google Ads shows its source: "Website" for native tags, "GA4 property" for imports. Know which is which.
4. Verify enhanced conversions. If you are using native tags, confirm enhanced conversions are active. This is the single highest-ROI measurement improvement for most accounts.
5. Test the flow. Open Tag Assistant, walk through a conversion, and confirm the correct tags fire exactly once.

For a deeper review covering cross-domain tracking, consent mode, event parameters, and more, see the GA4 tracking audit checklist.

FAQ

Not sure whether your GA4 imports are helping or hurting your Google Ads performance? Get in touch -- I will audit your conversion setup and tell you exactly what needs to change.