Track Elementor form submissions as conversions in Google Analytics
A visitor fills out your Elementor form, but Google Analytics only shows you the visit — not the lead. This guide walks through a no-code route that turns each Elementor form submission into a GA4 event, verifies it in Realtime, and then promotes it to a key event so it can appear in acquisition and funnel reporting. It also covers the optional next layer: capturing attribution data alongside the submission so you can see which channel produced each lead.
Why form submissions disappear from default GA4 reporting
GA4 is good at counting sessions and page views out of the box. It is not automatically configured to treat an Elementor form submission as a conversion. Without an event that fires on submit, you can see traffic but not the leads that traffic produced. The technical routes — watching page elements through Google Tag Manager, or sending data via the Measurement Protocol — work, but they usually demand comfort with tag configuration, CSS selectors, or API calls. The path below avoids that by using a no-code conversion tool to listen for the Elementor submit and forward an event to GA4.
The four-step setup
The setup has four stages: build the conversion flow, place the snippet, test in Realtime, and mark the event as a key event. Each stage answers a different question — does the trigger exist, does the browser receive it, does GA4 record it, and does GA4 treat it as a conversion. Skipping the test stage is the most common way to end up with a key event that never fires.
Step 1 — Build the conversion flow
In the conversion tool, choose a trigger (an Elementor form submission) and an action (send a conversion event to Google Analytics). The flow is a two-part definition: what happens, and what should follow. Once saved, the tool produces the snippet used in the next step. The same flow can also target Google Ads, Meta Ads, and similar destinations, but for this guide the GA4 destination is the one that matters.
Step 2 — Add the snippet to the site
The tool returns a small snippet. Its job is to listen for Elementor form submissions and forward the event data to GA4 (and any other destination configured in the flow). On WordPress, three placement options are practical: the theme's Scripts or Header settings, a header/footer insertion plugin, or Google Tag Manager. Whichever route you pick, the snippet needs to load on the page that contains the form — otherwise the listener never attaches.
Step 3 — Verify the event in Realtime
Open the site in an incognito window, navigate to the form page, and submit a test entry. Then open GA4, go to Realtime Overview, and check the Recent Events panel. A row labelled form_submit (or whatever event name you configured) confirms two things at once: the listener fired on submit, and the data reached the property you linked. If the row is absent, the problem is upstream — snippet placement, trigger configuration, or the wrong GA4 property — not the key-event setting.
Step 4 — Mark the event as a key event
In GA4, open Admin → Events under Data Display, switch to the Recent Events tab, locate form_submit, and click the star to mark it as a key event. That designation is what lets the submission appear in acquisition reports and in funnel or path exploration. Two practical caveats: new events can take a few hours to appear in the Recent Events panel, so a missing row right after setup is not automatically a failure; and the counting method deserves a deliberate choice. For lead-generation sites, Once Per Session is usually the better fit — it prevents one visitor who submits the form twice in a single visit from being counted as two conversions. An eCommerce store, by contrast, may want every purchase counted. Change the method via the three-dot menu next to the event, then select Once Per Session.
Decision checklist: which failure are you actually seeing?
Use this checklist to separate the three common symptoms before changing any settings.
- No form_submit row in Realtime Overview → the event is not reaching GA4. Check snippet placement, the trigger definition, and that the linked property is the one you are viewing.
- form_submit appears in Realtime but not in Recent Events → likely reporting latency. Recent Events can take a few hours to populate; wait before reconfiguring.
- form_submit appears in Recent Events but not in acquisition reports → the event has not been marked as a key event, or the counting method is producing unexpected totals.
- Conversions look inflated for a lead-gen site → the counting method is probably set to count every submission rather than once per session.
Optional layer: capture attribution data with each submission
Sending a conversion event tells GA4 that a form was submitted. It does not tell you, inside the form record itself, which channel produced that lead. A second layer solves this: a script inspects how the visitor arrived, groups the visit into a standard marketing channel (Organic Search, Paid Search, Paid Social, and similar categories), and stores that classification in the browser. When the visitor submits the Elementor form, the stored values are written into hidden fields on the form. The submission then carries the attribution data with it — into CRM records, email notifications, spreadsheet exports, or downstream reporting. That is the mechanism the source product is built around, and the linked walkthrough covers the field-level setup.
Three reports worth running once the event is live
Once form_submit is a key event, three GA4 views become useful for judging marketing performance.
- Conversions by channel. Shows how many form submissions arrived from each channel — Organic Search, Paid Search, Paid Social, Organic Social, and others. Useful for a quick read on which channels are producing leads and which are not.
- Conversions by Meta Ads network. If you advertise through Meta, placements can span Facebook, Instagram, Messenger, and WhatsApp. This view breaks conversions out by network so you can see which placement is actually delivering.
- Conversions by Google Ads campaign. When multiple campaigns run — different products, brand versus non-brand keywords, different geographies — this view shows which campaigns are producing conversions, so budget can follow results.
What you end up with
After the four steps, every Elementor form submission sends an event to GA4, and the key-event designation makes that event usable across acquisition and funnel reporting. The optional attribution layer extends the same submission with channel data that can travel into a CRM. Either path — event only, or event plus attribution — gives you a clearer picture of which marketing activity is producing leads rather than just traffic.
Frequently asked questions
Do I need to write code to track Elementor form submissions in GA4?
Not with the no-code route described here. A conversion tool listens for the Elementor submit and forwards an event to GA4; you place a snippet and configure a flow. The alternative routes — Google Tag Manager element triggers or the Measurement Protocol — typically require more technical familiarity.
Why is my form_submit event not showing in GA4 Recent Events?
Two different causes produce the same symptom. If the event is missing from Realtime Overview as well, the event is not reaching the property — check snippet placement, the trigger, and the linked property. If it appears in Realtime but not in Recent Events, it may simply be reporting latency; new events can take a few hours to populate that panel.
Should I use Once Per Session or every submission for counting?
For lead-generation sites, Once Per Session is usually the better fit: a visitor who submits the form more than once in the same visit is still one lead. For eCommerce, where a single visitor may make several purchases, counting each one is generally preferable. The setting is changed from the three-dot menu next to the event.
What does marking the event as a key event actually change?
It tells GA4 to treat the event as a conversion. That unlocks its appearance in acquisition reports and lets it be used in funnel or path analysis. Without the designation, the event is recorded but is not treated as a conversion in those views.