Skip to content

Capture Facebook Ads data in Elementor Forms

Elementor Forms can collect a name and an email address, but on its own it cannot tell you which Facebook ad brought that person in. This guide shows how to attach campaign-level attribution to each submission so you can compare channels, networks and campaigns instead of guessing.

What you are actually building

The setup has four moving parts. First, every Facebook ad link carries UTM parameters that describe the campaign, ad set and ad. Second, a small script on your site reads those parameters when a visitor arrives and stores them in the visitor's browser. Third, your Elementor form contains hidden fields named to match the attribution data. Fourth, when the form is submitted, the stored values are written into those hidden fields and saved alongside the lead's name and email. The result is a lead record that says, for example, that this person arrived from a paid social placement on Facebook under a specific campaign.

Step 1: tag your Facebook ad links with UTM parameters

UTM parameters are text appended to the end of a destination URL. They do not change the page the visitor sees; they only describe how the visitor got there. A typical tagged link looks like the sample below, where the base page is followed by a medium, a source and a campaign name.

A practical UTM convention for Facebook Ads

You can put any values you like behind your ads, but a consistent convention makes later reporting far easier. The following mapping is a sensible default for Facebook, Instagram and Messenger placements.

Step 2: install the attribution script on your site

The attribution script is a small piece of code added to your website. On each visit it inspects a few technical signals about how the visitor arrived and uses them to identify the origin, such as a Facebook ad. When the visitor later submits a form, the script writes the attribution values into the form's hidden fields, and Elementor saves them with the rest of the submission. Installation follows a short set of code-placement instructions provided with the account; the account prerequisite and any trial terms are set by the owner and should be confirmed before publishing.

Step 3: add the hidden fields to your Elementor form

Open the lead-capture form you use for enquiries or demo requests and add the following hidden fields. In Elementor, click the button that adds a new form item, then choose the hidden type from the field-type dropdown. The field names must match exactly so the script can populate them.

Field-to-report map

Each hidden field feeds a different question. Use this map to decide which fields you need before you start building reports.

Step 4: confirm the data lands in the submission

When a visitor arrives from a tagged Facebook ad, the script stores the UTM parameters in a cookie in that visitor's browser so they are not forgotten as the visitor moves around the site. When the visitor eventually submits the form, the script writes the derived Facebook Ads data into the hidden fields, and Elementor captures it together with the name, email and any other visible fields. Test this by clicking a tagged ad link, navigating to a different page, then submitting the form and checking the saved entry.

Where the captured data can go next

Once the values are saved in Elementor, you can forward them using Elementor's native integrations or a connector such as Zapier. Common destinations include a CRM for pipeline and revenue reporting, a spreadsheet for lighter analysis, a lead-notification email, or a billing platform for revenue attribution.

Why a cookie-based attribution layer matters

Page-only UTM capture has a structural weakness: it depends on the tagged URL still being in the address bar at the moment the form is submitted. Picture a visitor who clicks a campaign ad, reads the landing page, then follows a separate quote or contact link to complete the request. The form page never saw the original parameters, so the submission arrives with no ad context. A cookie-based layer sidesteps this by writing the parameters to the browser on arrival and reading them back at submission time, wherever that form happens to live.

Handling inconsistent UTM values

Tagging discipline drifts over time. One campaign may ship utm_source=facebook while a later one uses utm_source=facebook.com, and both describe the same placement. A recognition layer that understands these variants can fold them into a single channel assignment — paid social in this case — so the report does not split one source into two competing rows.

Landing page data alongside ad data

The same capture can also record the first page a visitor saw and a grouped label for that page, such as a blog section. That gives you a second lens on pipeline: how much arrives through content rather than paid placement, and which individual articles are doing the work of attracting leads.

Three reports worth building

If the captured data reaches a CRM or spreadsheet, three reports answer most Facebook Ads questions. A leads-by-channel report compares paid social against organic search, organic social, referral and direct. A leads-by-network report separates Facebook, Instagram and Messenger placements. A leads-by-campaign report tracks monthly lead volume per campaign so you can decide where to increase budget.

Pre-launch checklist

Before you rely on the numbers, confirm each item: every active ad link carries the agreed UTM values; the attribution script is present on all pages that host a form; the hidden field names match the expected list exactly; a test submission from a tagged link shows the expected channel and campaign values; and the destination CRM or sheet displays those values in the same fields you plan to report on. If a test submission shows blank attribution, check first whether the ad link was tagged, then whether the script loaded on the landing page.

Hidden field to report mapping
Hidden fieldWhat it answersExample report
ChannelWhich broad channel produced the leadLeads by channel
Channel Drilldown 1First level of detail within the channelLeads by network
Channel Drilldown 2Second level of detailLeads by campaign
Channel Drilldown 3Third level of detailLeads by ad set
Channel Drilldown 4Fourth level of detailLeads by ad
Landing PageExact page the visitor first landed onLanding page performance
Landing Page GroupGrouped section of the siteContent group performance

Field names are exact and must match the attribution script. Report names are illustrative examples of what each field can support.

Frequently asked questions

Do I need to add UTM parameters to every Facebook ad?

Yes, if you want campaign-level attribution. Without UTM parameters the script has nothing to read, so the submission will not carry the campaign, ad set or ad details. Add the agreed values to every active ad link before launch.

Why does the form submission show blank attribution even though the ad link was tagged?

Check two things in order. First, confirm the attribution script is loaded on the landing page the ad points to. Second, confirm the hidden field names in the Elementor form match the expected list exactly. A mismatch in either place prevents the values from being written.

Does this work if the visitor submits the form on a different page from the one they landed on?

Yes. The attribution script stores the UTM parameters in a cookie in the visitor's browser, so the values remain available across pages until the form is submitted.

Can I capture Instagram and Messenger ad data as well as Facebook?

Yes. The UTM source value can be set to Instagram or another network, and the leads-by-network report then separates performance by placement.