Should I Import GA4 Conversions Into Google Ads?

You've linked GA4 to Google Ads, and the conversions screen offers to import your purchase and lead key events in two clicks. Your Google Ads tag already fires on the same thank-you page. A careless import hands Smart Bidding every sale twice, counted under two different sets of rules.

Import them, but not as the conversions you bid on. Keep the native Google Ads tag as the primary action for every goal Smart Bidding optimises toward. Bring GA4 key events in as secondary actions, for comparison and as a fallback. Make an import primary only for an event the Ads tag cannot measure, and never for one it already does.

What happens when you import a GA4 key event?

An imported key event is not a copy of your Analytics conversion. It is a filtered version of it. GA4 hands Google Ads a last-click view of your key events, whatever attribution model you've chosen on the Ads side. Only key events where Google Ads was the last non-direct click become conversions in Ads, and that holds even when a non-last-click model is selected in Ads, per Google's Analytics documentation.

That rule decides more than most teams expect. Picture a customer who clicks a search ad, leaves, comes back three days later through your newsletter and buys. The native Ads tag records that sale against the click. The imported key event does not, because email was the last non-direct touch. If you give Smart Bidding the import as its primary signal, it learns that the keyword which started the journey produced nothing, and it bids that keyword down.

GA4 also has a property setting that controls which channels may receive credit for conversions shared with Google Ads. You can limit it to Google paid channels, or open it to paid and organic channels. Whoever last touched that setting changed what Ads receives, and few teams can tell you which option their property uses.

Some measurement doesn't exist on the import path at all. View-through and engaged-view conversions from video and Display come from the Ads tag. An account that bids only on imported events is blind to them, which matters most for exactly the campaigns that rarely win the last click.

These rules are a large part of why Google Ads and Analytics conversions never match. For the import decision the point is narrower. The conversion you bid on should see paid touches the way Ads sees them.

Why importing alongside the tag double counts

The bigger risk isn't attribution. It's ending up with two conversion actions for one sale.

A native purchase action and an imported GA4 purchase can both fire correctly for the same order. Google Ads still treats them as separate conversion actions. Transaction-ID deduplication works within a single action, so passing the same order ID to both does not merge them. Each one is counting accurately. The trouble is that the two are being added together.

If both actions are primary and both sit in a campaign's goal, Smart Bidding optimises toward their sum. Take a simple illustration with complete overlap: 200 orders at $50 each on $2,500 of spend. One action reports 4x ROAS. Two overlapping actions report 8x, and cost per conversion halves on paper. Revenue is still $10,000. A target ROAS strategy that reads 8x will bid harder for traffic that is actually returning 4x.

Real overlap is rarely that clean, and that makes the problem harder to spot. Consent banners, ad blockers and checkout redirects affect GA4 and the Ads tag differently. The overlap therefore varies by campaign and device. Some campaigns look more productive than they are, and an account-wide duplication ratio hides which ones.

Setting the import to secondary moves the risk rather than removing it. Secondary actions sit in All conversions. A dashboard scorecard labelled "Revenue" that sums All conversion value will quietly add the two together. A secondary action placed inside a custom goal can also still be used for bidding when that goal is applied to a campaign.

When is importing the right call?

Importing earns its place in three situations.

When you can't get the Ads tag in place. Some sites only give you GA4: hosted checkouts, locked-down platforms, a client whose development queue runs for months. A last-click import is a far better bidding signal than no conversion data. Make it primary in that case, and confirm that no native action exists for the same event.

As a secondary comparison. A secondary import shows Analytics' view of the same outcome inside the Ads interface, and you can segment it by campaign. When the two numbers diverge sharply on one campaign but not the others, you have found a tracking question worth chasing. That could be a consent issue, a redirect that drops parameters, or a tag that fires on the wrong page.

As a backup signal. Site releases break tags. A secondary import that keeps recording while the native action flatlines is often the first sign something has gone wrong. It also gives you a temporary signal to switch to while the tag is fixed.

Outside those cases, importing a key event that the Ads tag already measures adds noise to your setup and nothing to your bidding.

None of this settles which figure goes in the monthly report. That is a separate decision with a different answer, covered in which lead count you should report.

How to set up the import without damage

If you import, treat it as a configuration job and not a toggle:

1. Inventory every action that measures the same outcome. For each one, record the source (GA4 or tag), primary or secondary status, goal membership, count setting, conversion windows, value mapping and currency.
2. Check status at campaign level. An account-level default doesn't describe a campaign with its own goals. Older accounts may also have imported actions set to primary, so check each one rather than trusting what the default should be.
3. Set the import to secondary unless it is the only measurement of that event. Check custom goals, because they can pull a secondary action back into bidding.
4. Align settings so the comparison means something. Match the Ads click-through window to the GA4 lookback window. Count leads once per user on both sides. Choose GA4's channel-credit setting deliberately instead of inheriting it.
5. Segment the campaign report by conversion action, and audit any dashboard that sums All conversion value.
6. Validate both against your backend. Match order IDs and amounts to confirmed orders before you decide which measurement to trust.

Step six is the one teams skip, and it is the only one that tells you which source reflects reality.

Conclusion

Importing GA4 key events into Google Ads is useful, but it should not be what you bid on. The import arrives filtered through last click and loses the Ads-only measurement that video and Display depend on. Running it as primary beside a native tag inflates every efficiency metric Smart Bidding reads. Bid on the native tag, keep the import as a secondary cross-check and backup, and promote it only when it is the sole signal you have.

See how Companion answers performance questions from your Google Ads and Analytics data in one grounded view, with a daily brief on what changed.