Illustration of the path from website enquiry to an analytics event.
Your website received a real enquiry. Elementor shows it in Submissions, but your Google Analytics report shows no lead. Before changing the form or adding a new tag, trace an accepted submission from the browser to the correct GA4 property. The first missing step tells you whether the problem is the trigger, consent, the data stream or reporting.
Establish what counts as a lead
Write down the action you want to measure. For a contact form, I use the successful acceptance of an enquiry as the starting point. A visitor may press Submit twice, miss a required telephone field or lose their connection. Each of those interactions can look like activity without producing a new lead.
Check that the intended form has a way to confirm acceptance. Where Elementor collects submissions, compare the saved entries with the on-page success state. Email delivery and CRM routing can be tested as separate outcomes. If the visitor sees an error or no entry is saved, diagnose the form itself first. Elementor explains the available actions and where to review captured entries. Actions After Submit and Form Submissions.
Find where the success signal goes
List the form name, landing-page URL, the installed analytics integration and the intended measurement ID. Follow the event from the actual success handler to its analytics destination. A site can have GA4 loaded by more than one integration, or retain an older container after a redesign.
Google recommends generate_lead when a lead has been generated. Agree on the conversion event for the form and the key-event configuration in the receiving property. Include a non-personal form label if it helps you distinguish campaigns or service pages. Keep names, email addresses, phone numbers and form messages out of event parameters and URLs. Google Analytics event reference.
Reproduce the gap on an approved test setup
Use your staging or approved testing flow and compare one attempt at a time. In DebugView, look for the event on the correct device and stream. If it is absent, check whether the browser was permitted to record analytics under your consent setup, whether the tag loaded and whether the success condition was met. An empty debug view alone cannot distinguish those causes. Google Analytics DebugView.
| Test | Expected result |
|---|---|
| Required mobile field omitted | The form shows validation. No new lead is recorded for the attempt. |
| One approved test is accepted with analytics permitted | One test record and one lead event reach the agreed destinations. |
| The confirmation page is refreshed | The original record remains and a second lead event is not counted. |
| Analytics consent is denied | The form follows its normal acceptance flow. Analytics follows the approved consent configuration. |
Give one integration ownership of the event
Consider a fictional service page where the Elementor success handler sends one event and the thank-you template sends a second event on page load. A single valid enquiry can register twice, and opening the confirmation URL again can add more. Choose one trigger that can reliably identify acceptance for this form. If a confirmation route is the agreed trigger, scope a way to tie it to a successful request and handle reloads.
Check older submit-click triggers and GA4-created events on the same path. Keep any useful engagement signals distinct from the event you use for leads. Compare the right date range and property once the reporting pipeline has processed the event.
Include CRM delivery and reporting in the handover
Keep separate checks for a saved submission, a delivered email or CRM record, and an analytics event. Three passing checks answer different questions. Compare those outcomes after template or tag changes. If you are also changing where enquiries are sent, see the Elementor form-to-CRM guide for field mapping and failed-delivery handling.
Ask for a record of the event name, its trigger, the consent behaviour and the sample checks used to accept the fix. This gives the next person a way to verify the setup after a landing-page edit or tag change.
Share one form URL and the mismatch you can see
Send the landing-page URL, the name of the form and which step works today. A redacted example and the relevant GA4 property name are enough for the first review. I can scope the repair, test it in an approved environment and document where your lead numbers come from.
