GA4 Not Tracking Conversions: How to Find the Cause

When GA4 is not tracking conversions, first check that the event is arriving at all in Realtime or DebugView. Then confirm it is marked as a key event, that the tag fires on the right action, and that consent settings or filters are not blocking it. Most cases are a tag that stopped firing after a site change.

Is the event reaching GA4 at all?

Start here, because it splits the problem in two. If the event arrives, the fault is in GA4’s settings. If it does not, the fault is on your site or in your tags.

One note on wording first. GA4 renamed conversions to key events: an event is any action GA4 records, and a key event is an event you have marked as important to the business. “Conversions” is now the term Google Ads uses. This post uses both to mean the same thing.

How to check if conversion tracking is working, as of October 2026:

1. Open your site in a normal browser window and complete the conversion yourself: submit the form, tap the phone number, or place a test order.
2. In GA4, open Reports, then Realtime. It shows activity from the last 30 minutes. Look for your event name in the event count card.
3. For more detail, turn on Google Tag Manager Preview mode or the Tag Assistant extension, repeat the action, and open Admin, then DebugView. It lists each event from your own device in order, with its details.
4. Check that the name matches exactly what you expect, for example generate_lead or purchase.

Is the event marked as a key event?

If the event arrives but GA4 shows no conversions, it is probably not marked as a key event. GA4 does not do this for you, except for purchases.

Go to Admin, then Data display, then Events. Find the event and click the star next to it. Three details explain most “GA4 key events not recording” cases:

• It is not retroactive. Marking an event changes reports from that point forward. Past events stay as plain events.
• It takes time to show. Allow up to 24 hours for a new key event to appear in standard reports. Realtime shows it within minutes.
• Names must match exactly. Generate_Lead and generate_lead are two different events. If a developer renamed the event, the old key event keeps waiting for a name that no longer arrives.

A standard GA4 property allows up to 30 key events, so the limit is rarely the cause. Having too many is a different problem: see what conversions you should track.

Is the tag firing on the right action?

If the event never reaches GA4, the tag is not firing, or it fires on the wrong thing. This is the most common cause, and it almost always follows a change to the site.

A tag is the small piece of code that sends the event. A trigger is the rule that tells it when to fire. Triggers break when the thing they watch changes:

• The thank-you page got a new URL, so a trigger watching for /thank-you/ never matches.
• The form was replaced or updated, and it no longer sends the signal the trigger listens for.
• The form now shows a message on the same page instead of redirecting.
• A theme or plugin update removed the Google Tag Manager code from some pages.
• A cache or script-optimization plugin delays or strips the tag.
• Someone edited the Tag Manager container and did not publish, or published the wrong version.

To test, open Tag Manager Preview mode, complete the conversion, and see whether the tag is listed under “Tags Fired”. If it is not, click the tag to see which trigger condition failed. The full method is in Google Tag Manager not working: how to test and fix tags.

Also check for the opposite fault. If GA4 is installed twice, once through a plugin and once through Tag Manager, every conversion counts double and the numbers look wrong in the other direction.

Are consent settings or filters blocking data?

If the tag fires for you but reported conversions are low, something is dropping data between the visitor and the report. The usual suspects are the consent banner and GA4 data filters.

Consent banner

A consent banner is built to stop tags until the visitor agrees. If it is set up wrongly, it stops them for everyone, or GA4 fires before consent is read and then gets blocked. Test in a private window: decline cookies and convert, then accept cookies and convert, and compare what reaches DebugView. A sharp drop that starts the day a banner went live points here. See Consent Mode v2 explained for how GA4 is meant to behave in each case.

Data filters

In Admin, under Data collection and modification, open Data filters. An active internal traffic filter removes visits from the IP addresses you listed. If your whole office tests from one of those addresses, your tests vanish. Once a filter is active, the excluded data is gone for good, so check the rule before blaming the tag.

Ad blockers and browsers

Some visitors block analytics outright. This causes a steady, modest shortfall, not a sudden drop to zero. If your numbers fell off a cliff, look elsewhere.

Why does GA4 show traffic but zero conversions?

Because GA4 is counting visits correctly but cannot see the action that counts. Either the conversion happens off your site, or it is recorded under a name GA4 is not treating as a key event.

What that looks like by business type:

• Local service business: the booking runs through a third-party scheduling widget or an embedded form in an iframe (a page inside your page). The visitor books, but your site never sees a submission.
• Ecommerce store: checkout or payment happens on another domain. The buyer leaves, pays, and either never returns to a page with the tag or comes back as a new visit from the payment provider.
• B2B or lead generation: the form posts to a CRM or marketing tool that shows its own thank-you message, so no thank-you page loads and no event is sent.
• Phone-led business: most leads call. GA4 cannot hear a call unless a click-to-call event or call tracking tool sends one.

Two other causes are worth a minute. You may be looking at the wrong GA4 property: compare the Measurement ID (the code starting with G-) on your site with the one in Admin under Data streams. Or you may be looking too soon: GA4 data processing can take 24 to 48 hours, so yesterday’s numbers can still change.

If conversions appear in GA4 but the source looks wrong, with sales credited to a payment provider or to “direct”, that is an attribution problem, not a tracking failure. Add the payment domain under Admin, Data streams, Configure tag settings, List unwanted referrals. If the gap is between GA4 and your ad account, read why GA4 and Google Ads conversions do not match.

How do you stop conversions from breaking again?

Treat tracking as part of the website, so every site change includes a tracking test. Most repeat failures come from a change nobody connected to tracking.

☐ Keep a one-page list of every conversion: event name, what triggers it, and where it is sent.

☐ After any change to forms, checkout, theme, plugins or the consent banner, run a test conversion and confirm it in Realtime.

☐ Once a month, compare GA4 key events with real leads or orders from your CRM or store.

☐ Name and describe every Tag Manager version you publish, so you can see what changed and roll back.

☐ Limit who can publish in Tag Manager and who has Editor access in GA4.

☐ Set a GA4 custom insight to email you when a key event drops sharply.

☐ Before a redesign or platform move, follow a website migration tracking checklist.

If you run Google Ads, this matters twice over. Automated bidding learns from the conversions it receives, so a week of missing conversions is also a week of the campaign learning from bad data.

A fuller review of the property is in our GA4 audit checklist. If you would like someone to find the cause for you, our tracking and analytics team will check your setup in a free audit and tell you exactly what is broken.