Skip to content

Track Instagram Ads in Elementor Forms

Visitor counts alone do not show which Instagram campaign, ad set, or individual ad produced a lead. This guide explains how to attach source data to each Elementor form submission so reporting can start from the lead record rather than from clicks or impressions.

Why form submissions need source data

Analytics tools are generally oriented around visits, while lead reporting needs the marketing source attached to the person who converted. If that link is missing, a form submission may show a name and email but not whether the person arrived from Instagram, another network, search, or a direct visit. Capturing source data at submission closes that gap and makes it possible to compare campaigns by actual leads rather than by traffic alone.

The four-stage workflow

The workflow has four stages. First, tag every Instagram ad destination with UTM parameters. Second, install the attribution snippet and add hidden fields to the form. Third, let the snippet write the visitor's source into those fields when the form is completed. Fourth, read the values from the submitted record. The protected form-controls-contract module governs the exact field contract for step two and should be followed as supplied.

Step 1: Tag each ad destination

UTM parameters are additional text appended to the destination URL. For Instagram, the source recommends a consistent mapping: medium identifies paid social, source identifies Instagram, campaign names the campaign, term names the ad set, and content identifies the specific ad. Consistency matters because those values become the drilldown detail available later. A destination without parameters, or with inconsistent naming across ads, produces weaker reporting even if the form capture works.

Step 2: Install the snippet and add hidden fields

Install the attribution snippet on the website, then add hidden fields to the Elementor form. The hidden fields to include are Channel and Channel Drilldown 1 through 4, and each one should be set to the Hidden field type with a default value so the snippet can populate it. Confirm the exact list against the protected form-controls-contract module before building the form. The snippet is the attribution tool used in this workflow; any trial terms and setup time depend on the provider you choose, so check those details with that provider before you begin.

Step 3: Let the snippet populate the fields

Once installed, the snippet identifies how each visitor arrived and categorises that arrival into a channel, using the same broad channel families seen in analytics tools such as Paid Social, Paid Search, and Organic Search. The values are stored in a browser cookie, so they can survive further browsing or a later return visit. When the visitor completes a form, the stored source is written into the hidden fields, and the submission carries it together with the lead's name, email, phone, and other form answers. The tool is also designed to tolerate inconsistent UTM naming, such as different spellings for the same source, and still assign the lead to the correct channel.

Step 4: Use the captured data

After submission, the source data can be reviewed in Elementor's Submissions section, included in notification emails so every lead shows its origin, passed to a CRM such as HubSpot, Salesforce, or Pipedrive for lead and customer reporting, or downloaded as a spreadsheet for charts in Excel or Google Sheets. Choose the destination based on where follow-up happens: email for immediate handling, CRM for pipeline reporting, and spreadsheet for quick campaign comparisons.

What the submission records

Two groups of values are captured. Channel data records where the lead came from: Channel, followed by drilldowns for network, campaign, and ad creative. Landing page data records the first page the visitor arrived on and that page's category, which makes it possible to see which content sections and individual pages generate leads. In the source's example, a digital-signs business running Instagram ads would see Paid Social, Instagram, the campaign name, and the ad creative for a lead, alongside the landing page and its category.

Three reports to run first

Three reports become straightforward once every submission carries source data. Leads by channel shows which channels drive volume overall and whether spend matches where leads actually come from. Leads by network compares Meta-owned networks such as Facebook, Instagram, Messenger, and WhatsApp. Leads by campaign shows monthly lead counts per Instagram campaign, separating campaigns that generate real leads from those that only generate impressions and clicks. Start with the channel view for budget decisions, then drill into network and campaign views to find the specific ads worth scaling.

Pre-launch checklist

Before launch, check that every ad destination carries the full UTM set, that hidden fields are present and set to Hidden, that a test submission from a tagged Instagram URL populates the channel and drilldown values, and that the values appear in whichever destination you use, whether Submissions, email, CRM, or spreadsheet. Re-test after any change to ad URLs or form fields, since inconsistent tagging is the most common cause of missing or fragmented source data.

Frequently asked questions

What is the basic setup for capturing Instagram ad source in an Elementor form?

Add UTM parameters to each ad destination, install the attribution snippet on the site, add hidden fields to the form, and let the snippet populate those fields before submission. The submitted record then carries channel, drilldown, and landing-page values alongside the visitor's details.

Which fields should the hidden form fields hold?

The captured set includes Channel, Channel Drilldown 1 through 4, the initial landing page, and its category. In the source example, Paid Social and Instagram are followed by campaign and ad-creative drilldowns.

Does attribution still work if someone browses first and submits later?

Yes. Because the attribution values are stored in a browser cookie, they can persist while the visitor browses or returns later, so the form does not need to be completed on the first landing page.

Where can the captured data be used after submission?

Submitted values can be viewed in Elementor Submissions, added to notification emails, sent onward to a CRM such as HubSpot, Salesforce, or Pipedrive, or exported as a spreadsheet for Excel or Google Sheets reporting.