If your GA4 conversions are not tracking, the problem is usually not your website. The cause is duplicate tags firing twice or triggers that are set up the wrong way. The good news is that both problems are easy to find and fix once you know where to look. This guide walks you through the checks, step by step. If you are new to this, start with our explainer on what conversion tracking is and why it matters.
In This Article
- How to Tell What Is Actually Going Wrong
- Why Duplicate Tags Break Conversion Tracking
- Google Tag Manager plus a hardcoded tag
- Two GA4 configuration tags in one container
- Step 1: Find and Remove Duplicate Tags
- Step 2: Fix Your Triggers
- The thank-you page that never loads
- Triggers that are too broad or too narrow
- Step 3: Mark the Right Events as Conversions
- Step 4: Test Everything Before You Call It Fixed
- Other Reasons GA4 Conversions May Not Track
- Frequently Asked Questions
- How long do GA4 conversions take to appear in reports?
- Why are my GA4 conversions double the real number?
- Do I need Google Tag Manager to track GA4 conversions?
- Can a cookie consent banner stop GA4 conversions from tracking?
How to Tell What Is Actually Going Wrong
Before you change anything, take five minutes to describe the symptom. Open GA4 and go to Admin, then Events, and look at the list. Then check Reports, then Engagement, then Conversions. Which of these sounds like your situation?
- Zero conversions, even though you received orders, form submissions, or signups. This usually means the event never reaches GA4, or it arrives under a different name and was never marked as a conversion.
- Conversions that are far too high, for example double the number of real orders. This is the classic sign of duplicate tags: the same event is being sent to GA4 twice.
- Conversions that appear in testing but not in reports. Events can take 24 to 48 hours to show up in standard reports, so what looks like broken tracking is sometimes just a delay.
Knowing which of these matches your problem saves you from fixing the wrong thing. A zero-count problem needs different steps than a double-count problem.
Why Duplicate Tags Break Conversion Tracking
A tag is the small piece of code that sends data to GA4. When two tags do the same job, GA4 receives every event twice. Duplicate tags are one of the most common reasons for messy conversion data, and they are almost always installed by accident.
Google Tag Manager plus a hardcoded tag
This is a frequent setup. A business installs the GA4 tag directly in the website code or through a plugin, and later someone adds the same GA4 tag inside Google Tag Manager. Now every pageview and every event fires twice. If you use Tag Manager, it should be the only place your GA4 tags live. If you have not set it up yet, see our guide on how to set up Google Tag Manager.
Two GA4 configuration tags in one container
Inside Google Tag Manager, look for GA4 Configuration tags. You should have exactly one per GA4 property, firing on the All Pages trigger. If you find two configuration tags with the same measurement ID, delete one. The same goes for duplicate event tags, for example two purchase tags that both fire on the order confirmation page.
Step 1: Find and Remove Duplicate Tags
Work through this checklist in Google Tag Manager:
- Open your container and search for every tag with Google Analytics or GA4 in the name.
- Count the GA4 Configuration tags. There should be exactly one for each property you track.
- Check your website code, theme settings, and plugins for a separately installed GA4 or gtag.js snippet. If Tag Manager is already handling GA4, remove the extra one.
- Look for duplicate event tags, such as two form submission tags or two purchase tags pointing at the same measurement ID.
- After removing duplicates, click Submit in Tag Manager to publish the clean version.
If you are unsure which tag to keep, keep the one inside Tag Manager and remove the hardcoded one. Tag Manager gives you testing tools and version history, which makes future fixes much easier. If the setup feels overwhelming, getting help from professional analytics services can save hours of trial and error.
Step 2: Fix Your Triggers
A trigger decides when a tag fires. Even with clean tags, a bad trigger means the conversion event never happens. Two mistakes cause many trigger problems.
The thank-you page that never loads
Many guides tell you to fire a conversion tag on the thank-you page. That works only if the form actually sends visitors to a new page. Modern forms often submit in the background and show a success message on the same page. In that case the thank-you page never loads, the trigger never fires, and GA4 conversions are not tracked. For these forms, use Tag Manager’s Form Submission trigger (see our guide on how to track form submissions in Google Analytics 4) or a custom event instead of a pageview trigger.
Triggers that are too broad or too narrow
Check these common trigger errors:
- A purchase tag firing on every page instead of only on the order confirmation page.
- A trigger set to fire on Page Load when the button click is what matters. Use Click triggers for buttons and links.
- A trigger that points to an old page URL after the site was redesigned and the URLs changed.
- A trigger that is paused, or set to fire only in a specific environment such as staging.
Open each conversion-related tag, read its trigger out loud, and ask: does this trigger fire at the exact moment the conversion happens? If you cannot answer yes with confidence, rewrite the trigger.
Step 3: Mark the Right Events as Conversions
In GA4, conversions work differently than in the old Universal Analytics. GA4 collects events first, and then you mark chosen events as conversions. If you skip the marking step, your data looks like GA4 conversions are not tracking when they are simply not labeled.
- Go to Admin, then Events. Find the event name you want to track, for example generate_lead or purchase.
- Turn on the Mark as conversion toggle for that event.
- If your event does not appear in the list, it has not fired yet. Go back to Step 2 and check your triggers, or use the Create event feature to build it from an existing event.
- Mark only events that represent real business value. Do not mark page_view or session_start as conversions. They will flood your reports with meaningless numbers.
Menu labels in GA4 change from time to time, so if a label looks slightly different, look for the closest match. For the full walkthrough, see our guide on how to track conversions in Google Analytics 4.
Event names are case sensitive. A form that sends Form_Submit will not match a conversion marked on form_submit. Keep names lowercase with underscores to avoid this silent mismatch.
Step 4: Test Everything Before You Call It Fixed
Never trust a fix until you have watched the event arrive. Google gives you two free testing tools.
- Tag Manager Preview mode: click Preview, enter your site URL, and complete the conversion yourself. The preview panel shows exactly which tags fired and which did not, in real time.
- GA4 DebugView: in GA4, go to Admin, then DebugView. Enable debug mode and repeat the conversion. You should see your event arrive within seconds.
Once the event shows in DebugView, remember that standard reports take 24 to 48 hours to update. Test today, verify tomorrow. Google’s official GA4 setup and event documentation is worth bookmarking for reference while you work.
Other Reasons GA4 Conversions May Not Track
If your tags and triggers are clean, check these remaining causes:
- Cookie consent banners: if your banner blocks analytics until the visitor accepts, and many visitors decline or ignore it, your conversions will undercount. This is expected behavior, not a bug.
- Ad blockers: some visitors block GA4 entirely. You cannot fix this for those visitors. Focus on getting clean data from the rest.
- Wrong property or stream ID: the measurement ID in your tags must match the property you are reading reports from. One mistyped character sends all your data to the wrong place.
- Internal traffic filters: if you filtered out your office IP address (see our guide on how to filter internal traffic in GA4) and then test from the office, your own test conversions will never appear.
- Testing the wrong container: make sure you published the Tag Manager workspace you tested, not a draft sitting in another workspace.
Work through this list, testing after each change. In many cases, one of these items is the culprit. If you are starting from scratch, run through our GA4 setup checklist for small business first. For more plain-language walkthroughs, browse our analytics and marketing guides, or get in touch if you would rather have an expert fix it for you.
Frequently Asked Questions
How long do GA4 conversions take to appear in reports?
Events you send today usually appear in standard reports within 24 to 48 hours. If you need to confirm a fix right now, use DebugView in GA4 or Preview mode in Tag Manager. Both show events in real time, so you do not have to wait a day to know your fix worked.
Why are my GA4 conversions double the real number?
Double counting almost always means duplicate tags. Check for a GA4 tag installed both in your website code and in Google Tag Manager, or two configuration tags inside the same Tag Manager container. Remove the duplicate, publish, and test again.
Do I need Google Tag Manager to track GA4 conversions?
No, but it makes life easier. You can install GA4 directly with the gtag.js snippet and send events with code. Tag Manager is recommended because it lets you add, test, and fix tags without touching website code, and its Preview mode makes debugging much faster.
Can a cookie consent banner stop GA4 conversions from tracking?
Yes. If your consent setup blocks the GA4 tag until a visitor accepts cookies, visitors who decline will not be tracked. Review your consent banner settings and your consent mode configuration so that the behavior matches what you intend.
