How to capture Google Ads data in Elementor forms
Analytics can tell you how many sessions a campaign produced. It rarely tells you which campaign produced the enquiry, the opportunity or the closed customer. This guide closes that gap for Elementor sites: tag your ads, add a small set of hidden fields, let an attribution layer fill them, and confirm the values arrive with each submission. You will also find a pre-flight checklist, a worked example and three reports worth building once the data is flowing.
What you are actually building
The goal is a chain with four links. First, every ad carries a tagged destination URL. Second, each Elementor form contains hidden fields with fixed names. Third, an attribution tool reads the tags and writes values into those fields before submission. Fourth, the submitted record carries both the visitor's contact details and their acquisition details into email notifications, a CRM or a spreadsheet.
If any link is missing, the chain breaks quietly. An untagged ad produces no campaign value. A form without the hidden fields has nowhere to store it. A tool that only reads the current page URL loses the data the moment a visitor navigates. And a record that never leaves Elementor cannot be reported on. Treat the checklist below as a chain test, not a list of chores.
Step 1: Tag every ad URL
UTM parameters are short text fragments appended to the URL you send paid traffic to. They tell analytics and attribution tools where the visitor came from. A tagged destination looks like the base page followed by a question mark and key-value pairs, for example a medium of paidsearch, a source of google and a campaign name of brand-campaign.
The values are yours to choose, but consistency matters more than cleverness. A workable convention for Google Ads is:
- UTM Medium: paid search
- UTM Source: Google
- UTM Campaign: the Google Ads campaign name
- UTM Term: the ad group the ad belongs to
- UTM Content: the specific ad
Free URL builders exist to assemble these strings without typos. For keyword-level reporting, the keyword can be passed through a tracking template rather than typed into each ad.
Step 2: Add the hidden fields to your Elementor forms
Create these six hidden fields in every lead capture form, using the names exactly as written so the attribution tool can match them:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Adding hidden fields in Elementor is a short, mechanical task; a step-by-step walkthrough is available if you have not done it before. Do it on every form, not just the main contact form — a quote request, a demo booking and a newsletter signup can all be the first meaningful conversion.
Step 3: Let the attribution layer fill them
Once the fields exist, the attribution tool watches where visitors arrive from. When someone submits a form, it writes the source information into the hidden fields.
Here is how that plays out for a typical paid-search visit. A visitor clicks an ad in a brand campaign, and the ad carries the recommended tags. The three drilldown fields then hold the channel, the source and the campaign name, while the third drilldown records the specific ad. The two landing-page fields separately record the first page the visitor saw — for example a cloud-storage features page — and its parent group, such as /features. Keeping those two fields distinct is what later lets you report at both the section level and the individual page level.
Step 4: Confirm the data lands with the submission
On submit, the values written into the hidden fields are captured alongside the lead's name, email and other answers. From there you can:
- Include the fields in each new-lead notification email, so whoever picks up the enquiry sees the source immediately.
- Push the record to a CRM such as Salesforce, Pipedrive or Keap, so the sales team sees acquisition context on the contact or opportunity.
- Feed the values into reports that connect campaigns to leads, customers and revenue rather than to sessions alone.
Pre-flight checklist before you trust the numbers
Run this once per form, and again after any template or plugin change:
- Open a tagged ad URL in a clean browser session and confirm the parameters appear in the address bar.
- Navigate to a different page, then open the form there. This is the step that exposes page-only capture.
- Submit a test enquiry with a recognisable name.
- Check the notification email: do Channel and the drilldowns show the expected campaign, ad group and ad?
- Check the CRM or spreadsheet record: did the same values survive the handoff?
- Check Landing Page and Landing Page Group: do they reflect the first page visited, not the form page?
- Submit a second test from an organic search visit and confirm it is classified as an organic channel rather than left blank.
If step 2 or step 6 fails, the problem is capture persistence, not your UTM naming. If step 4 passes but step 5 fails, the problem is the integration mapping.
Why cookie-based capture beats reading the current URL
A common shortcut reads UTM parameters from the URL of the page the form sits on. That works only when the form and the landing page are the same page. Picture a visitor who clicks a pricing-page ad, scans the plans, then follows a 'Book a demo' button to a separate booking page where the form lives. The tags were attached to the pricing URL; by the time the booking form renders, that URL is a page back in the visitor's history and the parameters are no longer in scope. The lead is recorded with no campaign.
A tool that stores the parameters in a cookie in the visitor's browser avoids this. Whatever page the form lives on, the original tags are still available at submission, which is what makes campaign-to-customer reporting credible rather than approximate.
Why raw UTM values create messy reports
Capturing tags verbatim seems harmless until you report on them. Suppose one team tags a source as google-ads, a contractor tags the same traffic as GoogleAds, and an older campaign still carries g-ads. A raw capture treats those as three unrelated sources, so any report built on the field splits one channel into fragments that someone has to reconcile by hand before the numbers mean anything.
Normalising at capture time collapses those variants into a single Paid search channel, so the report reflects reality on the first pass. The same logic applies to capitalisation and other inconsistencies across campaigns, ad groups and landing pages.
Three reports worth building
Leads by Channel. Because the setup captures every channel, not only paid search, you can chart monthly lead volume split by channel. This is the view that tells you where to put budget and headcount, rather than which ad has the best click-through rate.
Opportunities by Google Ads campaign. If several campaigns run at once, chart monthly sales opportunities by campaign. Campaigns that generate visitors but no opportunities become visible candidates for pausing or restructuring.
Customers by Keyword. With the keyword passed through a tracking template, you can chart customers by keyword and raise bids on the terms that actually close.
Where this fits alongside analytics
Web analytics remains the right tool for counting sessions and clicks from your ads. It is the wrong tool for answering which campaign produced a paying customer, because that answer lives in your CRM and your form submissions. Connecting the two is the point of the hidden-field setup: the form becomes the bridge between the click and the customer record.
| Hidden field | What it holds | Example value | Report it supports |
|---|---|---|---|
| Channel | Broad acquisition channel | Paid search | Leads by Channel |
| Channel Drilldown 1 | Source within the channel | Channel breakdown | |
| Channel Drilldown 2 | Campaign name | Brand campaign | Opportunities by Google Ads campaign |
| Channel Drilldown 3 | Ad group or specific ad | Free account ad | Ad-level performance |
| Landing Page | First page the visitor saw | /features/cloud-storage | Content-level lead volume |
| Landing Page Group | Parent section of that page | /features | Section-level rollups |
Example values illustrate how fields populate when ads use the recommended UTM convention; actual values depend on the tags you apply and the attribution tool's normalisation.
| Symptom | Likely cause | Where to check |
|---|---|---|
| Campaign fields blank on every submission | Ad URLs untagged, or tracking template not applied | The destination URL in Google Ads |
| Campaign fields blank only when the form is on a later page | Page-only UTM capture losing parameters on navigation | Whether the tool stores values in a cookie |
| Same campaign appears as several sources | Raw UTM values captured without normalisation | Source values across campaigns |
| Landing Page shows the form page, not the entry page | First-touch landing page not recorded | Landing Page and Landing Page Group fields |
| Values correct in email but missing in CRM | Field mapping in the integration | CRM field mapping settings |
| Organic leads show no channel | Only paid traffic is being classified | A test submission from organic search |
This is a diagnostic aid based on the described capture mechanics, not a record of tested failures on any specific site.
Frequently asked questions
Do I need to add UTM parameters if Google Ads already reports conversions?
They answer different questions. Google Ads conversion tracking counts actions attributed inside Google's system. UTM parameters carried into your form submissions let you see, in your own CRM or spreadsheet, which campaign, ad group and keyword the person who became a customer originally came from.
Why do my campaign values disappear when the form is on a different page from the landing page?
Because the parameters were only ever in the landing page URL. Once the visitor navigates, that URL is gone. A tool that stores the values in a browser cookie keeps them available for later submissions, which is why the multi-page quote-request pattern works.
What is the difference between Landing Page and Landing Page Group?
Landing Page is the specific first page a visitor saw, such as a single blog post. Landing Page Group is its parent section, such as /blog. Recording both lets you report on a content section as a whole and then drill into the individual pages driving the most leads.
Can I capture the actual search keyword?
Yes, by passing the keyword through a Google Ads tracking template so it arrives in the UTM term value. That makes keyword-level customer reporting possible, provided your attribution layer preserves the value through to submission.
How do I know the setup is working before I spend more on ads?
Submit a test enquiry from a tagged ad URL, navigate to a second page first, and then check the notification email and the CRM record. If the campaign, ad group and landing page values match what you tagged, the chain is intact.