Track the source of leads from Elementor forms
Elementor makes it straightforward to collect enquiries, but a submission on its own rarely explains which campaign, search result, or social post brought the visitor to the page. Adding attribution at form level closes that gap: each enquiry arrives with channel context, so marketing decisions can be based on leads rather than clicks alone.
Why form submissions need origin context
Elementor is effective for building forms, yet it provides no built-in way to record where a submitter originated. That missing context matters when comparing, for example, paid search against organic search or paid social: without it, every enquiry looks identical in the inbox. The approach below attaches origin information automatically at the moment of submission, using hidden fields that visitors do not need to complete.
Three-step setup and verification checklist
- Place the attribution snippet on the website using the WordPress instructions. 2) Add hidden fields to each Elementor form for Channel and Channel Drilldown 1 through 4. 3) When a visitor submits, the snippet writes the origin values into those fields. 4) The values are stored with the visitor's name, email, phone, and other submitted details. Before relying on the data, submit a test form from a tagged campaign link and confirm every hidden field populates in Submissions.
What the hidden fields capture
Channel gives the broad origin, such as Paid Search or Organic Search. Drilldowns add progressively finer detail: source, campaign, and keyword or term where available. Landing page and landing page group show which page first attracted the visitor and how that page fits into the site structure, for example a single blog post versus the blog section as a whole. Together, these fields let you distinguish a lead driven by a specific ad campaign from one driven by an organic search result.
Where to use the captured data
Once captured, the same values can be reviewed in Elementor Submissions, included in new-lead notification emails, or passed to a CRM such as Salesforce, HubSpot, or Pipedrive via plugins or integration tools. They can also be forwarded to a spreadsheet for reporting. Choose the destination based on where follow-up already happens: if sales work in the CRM, route there; if reporting is spreadsheet-based, route there instead of maintaining both.
Three reports to run each month
Leads by channel shows monthly volume across Paid Search, Paid Social, Organic Search, and other channels. Leads by Google Ads campaign separates campaigns that generate enquiries from those that only generate impressions and clicks. Leads by social network shows which social platforms produce enquiries, helping focus posting effort where it converts. Run these views monthly and compare them with spend and publishing activity to decide where to invest next.
| Field | What it tells you | Example use |
|---|---|---|
| Channel | Broad origin category | Paid Search vs Organic Search |
| Channel Drilldown 1 | Source platform | |
| Channel Drilldown 2 | Campaign or referring domain | Brand Campaign or www.google.com |
| Channel Drilldown 3 | Keyword or term where available | Elementor |
| Landing page | First page visited | A specific blog post |
| Landing page group | Section of that page | /blog |
Examples are illustrative values from the captured evidence, not guaranteed values for every visitor.
Frequently asked questions
Does Elementor track lead source by itself?
Elementor forms alone do not include lead-source attribution, so an attribution snippet and hidden fields are needed to record channel and drilldown values at submission.
What is the minimum setup checklist?
Add the attribution code to the site, add hidden fields for Channel and Channel Drilldown 1-4 to each form, then check that a test submission populates those fields before routing data onward.
Where can the captured lead source data go?
Captured values can be viewed in Elementor Submissions, added to notification emails, or forwarded to a CRM or spreadsheet through plugins or integration tools such as Zapier.