Skip to content

Capture Google Analytics Attribution in Elementor Forms

Elementor Forms can record who submitted a form, but not reliably where that person first came from. Adding attribution data at submission closes that gap for lead-driven sites: each enquiry arrives in your CRM with the channel, campaign detail and landing page that produced it, so later pipeline and revenue reporting can be tied back to marketing activity.

Why attribution needs to travel with the form submission

Google Analytics shows visits and channels at site level, yet it does not naturally follow a visitor through the sales conversation. For a business that sells through enquiries rather than an online checkout, that leaves a practical blind spot: you can see traffic, but not how many enquiries, qualified opportunities, customers or pounds of revenue each channel created.

The fix is to store attribution in the browser when the visitor arrives, then copy it into the form when they submit. The form therefore carries two kinds of information together: the contact details the person typed, and the origin data collected earlier. Once both are sent onward, reporting can answer commercial questions rather than only traffic questions.

How the capture works

A small snippet placed on the site examines the technical signals associated with the visit — the same broad signals analytics tools use — and classifies the origin, such as Paid Search, Paid Social, Organic Search or Email Marketing. That classification is kept in the visitor's browser.

When an Elementor form is completed, the stored values are written into hidden fields on that form. The visitor does not see or edit them, but they are submitted alongside name, email and phone. From there, a plugin or a tool such as Zapier can pass the complete record into a CRM such as Salesforce, Pipedrive or Zoho, or into another sales and marketing system.

Set up the hidden fields

Add these hidden fields to each Elementor form you want to measure:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

Channel gives the broad origin. The three drilldown fields add progressively finer detail, which is where campaign, ad group, keyword or network information can sit depending on the channel. Landing Page records the first page viewed, and Landing Page Group records its category, such as Features or Blog.

Checklist before you publish the form:

  • Every hidden field above is present and correctly named
  • The attribution snippet is installed on the pages containing the form
  • A test submission shows values in all six fields, not blanks
  • The downstream CRM or spreadsheet maps each hidden field to its own field, rather than overwriting contact fields
  • Reports are built from the stored fields, not from a separate analytics session

Worked example: a paid-search enquiry

Consider a visitor who arrives from a branded Google Ads campaign. On submission, the fields might be populated like this:

  • Channel: Paid Search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand Campaign
  • Channel Drilldown 3: Olmo
  • Landing Page: www.olmo.com/features/productivity
  • Landing Page Group: Features

That single record now lets you distinguish a branded paid-search enquiry that landed on a Features page from, say, an organic blog enquiry. Without the drilldowns and landing-page group, both would simply look like unnamed leads.

What the captured data covers

Attribution here rests on two questions. First, how did the person reach the site? Second, which content attracted them? Channel data answers the first, including extra detail per channel — for Paid Search, that can include campaign name, ad group name and keyword. Landing-page data answers the second, recording both the exact first page and its category.

Together they support reporting at two levels: the whole category, such as Blog, and the individual asset, such as one blog post. That distinction matters because a category can perform well overall while only a few pages do the real work.

Four reports worth building first

Once the fields reach your CRM or a spreadsheet, four reports are especially useful:

  • Leads by Channel: monthly lead volume split across Organic Search, Paid Search, Organic Social and other channels. Use it to spot a mismatch between where leads actually come from and where budget is going.
  • Opportunities by Google Ads campaign: sales opportunities per month broken down by campaign. This separates campaigns that generate genuine sales interest from campaigns that mainly generate traffic.
  • Customers by Facebook Ads Network: customers split across the Meta networks where ads appeared, such as Facebook, Instagram, Messenger and WhatsApp. This shows which network produces buyers, not just clicks.
  • Revenue from Organic Search by search engine: revenue attributed to SEO, split by search engine. Comparing it with Paid Search revenue helps judge whether organic investment deserves more support.

A practical decision rule: start with Leads by Channel for the budget conversation, then drill into Opportunities and Customers before moving money, and use SEO revenue to make the longer-term case.

Wrap up

Capturing attribution inside Elementor Forms turns each submission into a measurable marketing record. The hidden fields carry channel and landing-page detail into your CRM, where it can be joined to opportunity and revenue data. Before committing to a tool, check its current trial length, plan limits and setup requirements directly, and confirm that the six hidden fields map cleanly to your CRM before you rely on the reports.