WPForms entries and GA4 events don’t match. What should you check first?

1. Define exactly what each count measures

Record the WordPress form ID, the entry-storage source, the GA4 property and the exact event name. Ask whether the event represents a successful submission, an attempted submission, a button click or a thank-you page view.

GA4’s event count is the number of event triggers, not distinct prospects or qualified enquiries. Its Events report includes events collected within the selected date range. Google’s Events report documentation explains those metrics.

A property-wide event can cover several forms. Narrow the comparison to an equivalent cohort before expecting the reports to describe the same activity. A label such as generate_lead does not itself prove that the intended entry was saved.

2. Confirm that the entry history actually exists

Open an approved test entry in the storage source your comparison uses. Check whether the totals include spam, tests, failures or deleted records, and note when reliable collection started.

WPForms says Lite does not save entries in the WordPress database. Its Lite Connect feature backs them up remotely; that is different from a local entry store available to a monitoring connector. WPForms’ Lite Connect documentation describes this distinction.

For Mellizos Monitor, Lite alone is unsupported. The tested Lite configuration requires the free local Database for WPforms (WPFormsDB) storage add-on. Confirm the exact supported storage route before connecting a site; do not assume every entry plugin or backup service is compatible.

3. Use aligned dates and allow reporting to process

Write down the timezone, start and end dates, and when each report was fetched. Compare complete days rather than today’s partial activity. A collector that started yesterday cannot establish an earlier form history.

Google says processing can take 24–48 hours and report values can change while processing. Realtime visibility therefore does not establish a complete daily report. Google’s data-freshness guidance also describes varying processing intervals.

If a gap disappears after processing, record that result. Avoid changing a working tag solely to make a provisional report look complete.

4. Understand consent and collection differences

A valid enquiry and an analytics measurement follow different collection paths. Google’s basic consent mode blocks tags until consent; advanced mode adjusts tag behavior and can send measurements without cookies when consent is denied. Google’s consent-mode overview explains the implementations.

Review the actual setup with the person responsible for analytics and privacy. Do not weaken consent controls to force matching counts. Changes in consent choices, traffic mix or event configuration can alter the relationship without showing that submissions were lost.

5. Look for an unexplained change in the relationship

Keep the counts beside the percentages. The following example is invented to explain an investigation; it is not customer data, a product threshold or a verified Mellizos Monitor result.

A sharp change deserves review but does not identify its cause. With very low activity, small absolute differences can create large percentages. A responsible comparison needs enough comparable history and volume.

6. Test the real submission path before proposing a repair

With the site owner’s permission, submit one clearly marked test enquiry. Confirm it was accepted and stored, then inspect the intended analytics event using approved debugging tools. Also test a validation failure. Do not send real customer details into a demonstration.

• Check whether a plugin and a Google Tag Manager tag both send the event.
• Check whether a thank-you page reload can trigger it again.
• Check whether recent form changes affected identifiers or confirmation behavior.
• Distinguish disconnected imports from confirmed zero activity.

These are hypotheses to reproduce, not conclusions about your client’s site. Keep a dated record of any approved fix, repeat the test and allow daily reporting to process.

Where ongoing monitoring can help an agency

First ask whether your current tools already cover the job. If manual checks across client websites take meaningful time, ask who owns those checks, how often tracking changes and what evidence would make an alert useful.

Mellizos Monitor is preparing early access for WordPress sites with supported stored WPForms entries and an authorized, mapped GA4 success event. It compares aggregate counts and presents monitoring states and investigation evidence. The connector sends counts, not form answers.

The current pricing hypothesis is US$99/month for up to 10 supported websites, before applicable taxes. There is no free trial. Paid subscriptions are not open and this page collects no payment. A demonstration or early-access request creates no subscription.