This is one issue I’ve faced multiple times throughout my career, and it’s the kind of thing that can be happening on your website without you even realizing it for weeksor sometimes months.
Your form looks fine. Someone fills it in, clicks submit, and sees a confirmation message. You assume the lead has made it to where it needs to go. But somewhere between the form, your tracking, an integration, and your CRM, something may have quietly stopped working.
And that’s the tricky part: you might not notice. Your website is still up, your traffic numbers look normal, and nothing is necessarily throwing an obvious error. You just aren’t receiving the leads you should be.
It isn’t always the form itself that’s broken
Many of today’s WordPress forms submit in the background, often using AJAX, without reloading the page. That’s generally a good thing for the visitor experience, but it can make tracking a little less straightforward.
For example, a Google Tag Manager trigger that relies on the browser’s traditional form submission event may not catch what the form plugin is doing. The plugin might show a success message, but the tracking event never fires. Or the form may work, while the notification email, webhook, Zapier or Make workflow, or CRM handoff fails somewhere along the way.
There are several moving parts, and just because one of them works doesn’t mean the entire path is working.
You don’t need a tech person constantly checking this
Even if you don’t have a developer or technical person looking after your website every day, you can put a few simple checks in place to help you spot a problem early.
Sometimes you can set up alerts for unusual activity, and there are tools that can monitor parts of this process. But you don’t necessarily need to buy an expensive monitoring solution to start protecting yourself. A simple habit of checking that the numbers across your systems make sense can go a long way.
My suggestion is to reconcile the numbers regularly
Once a week, or after any significant website, plugin, tracking, or integration change, I would compare these three things:
- Form submissions: How many entries did the form plugin actually record?
- Analytics: How many lead events (such as
generate_lead) did GA4 record? - Your CRM: How many new leads actually made it into your system?
You don’t necessarily need all three numbers to be identical. There can be legitimate reasons for a differenceduplicate submissions, spam, consent settings, or how a lead is qualified or processed. What you’re looking for is an unexpected gap or a change that doesn’t make sense.
If your form recorded submissions but GA4 suddenly recorded significantly fewer lead events, that’s a good reason to investigate. If the analytics events are there but the CRM isn’t receiving the leads, you have a clue about where to start looking.
Set the alarm according to the volume of leads you receive
I’ve worked with situations where a business was receiving 100 to 500 leads a day. At that volume, it’s usually relatively easy to spot an anomaly. If leads normally arrive throughout the day and suddenly nothing comes in for a couple of hours, that’s enough of a signal to investigate.
But I think the more difficultand potentially more costlysituations are those involving smaller businesses. Imagine a business that generates one qualified lead a day, or perhaps just a couple every few days. If the form stops working and that business receives zero leads, it may not be immediately obvious that something is wrong. And the financial impact of losing those opportunities can be significant.
So the threshold needs to reflect your normal activity. If you usually receive ten leads a day, a day with zero should be enough to trigger a check. If you receive leads every hour, an hour with zero might be your trigger. If you only receive a few leads a week, a daily alert probably isn’t usefullook at a longer period instead.
Some alerting tools can help here, and it’s worth setting them up if you can. Just don’t confuse an alert with a complete solution. You also need a reliable way to maintain your tracking and integration code, understand what changed when something breaks, and restore or fix it without making things worse.
Test the full journey whenever you make a change
Whenever you make a significant change to a form, plugin, theme, tracking tag, or integration, submit a test yourself. Don’t stop at the confirmation message on the website. Check that the submission was recorded, that the analytics event fired, and that the lead reached the CRM or whatever destination you use.
It’s a small habit, but it can save you from discovering a broken handoff much later, when the leadsand the revenue opportunitiesare already gone.
Hope this helps.