Why GA4 Shows Fewer Conversions Than Webflow Form Notifications

Why it matters

The two numbers answer different questions. Webflow stores submissions in Site settings, then Forms. GA4 counts events that its tag sent after the visitor allowed collection.

Google says consent mode sends full measurement data only when a user grants consent. Where consent is denied in basic mode, nothing is sent. In advanced mode, tags send cookieless pings instead.

Google also says marking an event as a key event affects reports only from that point on. Past submissions do not move into GA4.

How to check it

1. Compare the same dates. GA4 Realtime updates a few minutes after an event. Standard reports can take up to 24 hours.
2. Count stored submissions, not emails. Go to Site settings, then Forms. Notification emails can fail separately. If a form uses a custom form action, Webflow sends no notifications for it.
3. Subtract your own tests. Webflow says a test submission on the published site appears in Site settings, Forms.
4. Check the key event. In GA4, go to Admin, Data display, Events. Open the Key events tab and confirm the event is marked.
5. Check the counting method. On the Key events tab, click the More icon on the event row. Then click Change counting method.
6. Test with consent granted and denied. Use DebugView. Google says events will not appear if client-side privacy controls are in place, or if consent mode is active and you have not consented to Analytics cookies.
7. Check that the event fires. Submit a test form on the live site and watch Realtime.
8. Check spam settings. In Webflow, open Site settings, then Apps and Integrations, then Cloudflare Turnstile spam protection.

How to fix it in Webflow

1. Choose one source of truth. Use Site settings, Forms for the number of submissions. Use GA4 for the visitors it was allowed to measure.
2. Compare from the marking date. Do not compare GA4 with Webflow for dates before you marked the key event. Google says marking is not retroactive.
3. Pick the counting method on purpose. Once per event counts each time the event triggers in a session. Once per session counts it once. Google gives an example of five triggers in one session: once per event counts five, once per session counts one. You need Marketer access or higher. Changes apply to future key events only.
4. Fix the trigger. If you use a Google Tag Manager Form Submission trigger, turn on Check Validation so it fires only when the form is successfully sent. If it is off, it fires whenever a user tries to submit.
5. Test the thank-you path. If you use a thank-you page, confirm the form redirects to it and the key event is made from that page view.
6. Handle consent honestly. Connect consent mode to your existing banner. Google says it provides no banner itself. Accept that GA4 will not see visitors who decline. Google says modeled data fills some gaps, but only when tags meet a data collection threshold.
7. Filter spam in Webflow. Go to Site settings, then Apps and Integrations, then Cloudflare Turnstile spam protection. Turn on spam filtering or bot blocking. Publish the site.
8. Stop counting duplicates. Mark only one event per form as the key event.
9. Compare again after a full day. Check standard reports the next day, not in Realtime.

Checklist

• The same date range is used on both sides.
• Stored submissions are counted, not emails.
• Test submissions are subtracted.
• The key event is marked, and the date is known.
• The counting method is chosen on purpose.
• The trigger fires on successful submissions only.
• Consent mode matches the banner.
• Spam filtering or bot blocking is on.
• Only one key event is marked per form.
• Standard reports were checked after 24 hours.

FAQ

Which number should I trust for leads?

Use Site settings, Forms for submissions. GA4 shows what its tag collected from visitors who allowed it.

Can GA4 show more than Webflow?

Yes. A Tag Manager Form Submission trigger with Check Validation off fires whenever a user tries to submit, even if the form fails.

Why are old submissions missing from my GA4 key event?

Google says marking an event as a key event affects reports only from that time on. It does not change historical data.

Dealing with this on a live Webflow site? It is the kind of work I do in Analytics. Send me your site and I will tell you what I would fix first.