Capture UTM parameters in Avada forms and connect them to leads
Visitor counts alone do not show which campaigns produced enquiries. This guide explains how to attach channel and landing-page data to each Avada form submission, so the resulting lead record can be reviewed in the form inbox, an email notification, a CRM, or a spreadsheet.
Why form submissions need attribution data
Analytics tools can report visits associated with tagged advertising links, yet they do not automatically attach that campaign context to a person who later asks for a quote or signs up. The missing link is the form record itself: when contact details arrive without channel information, later reporting cannot reliably separate paid, organic, referral, and direct enquiries.
A practical workflow closes that gap in four stages. Tag the advertising and campaign links, place attribution fields inside the form, allow stored visitor data to populate those fields, and then send the completed record to the destination where leads are worked. The checklist below keeps each stage separate, which makes testing easier when a value is blank.
Setup checklist: tagging, hidden fields, and a test submission
Begin with consistent tagging across search, social, video, email, and native placements. Consistency matters because the form can only classify what the visit and link provide. Use the same naming conventions for source, medium, campaign, and keyword values so later grouping does not depend on manual cleanup.
Next, open the relevant form in WordPress, add a hidden field element, configure its name, and repeat until all six fields are present. Hidden fields stay out of the visitor's way while still travelling with the submission. After adding them, submit a test form from a tagged link and inspect the stored entry before connecting any downstream destination.
Field map and a worked example
The six fields form a progression from broad to specific. Channel identifies the category, the three drilldown fields add platform, campaign, and ad-level detail, and the landing-page fields record where the visitor first arrived and how that page is grouped. That structure supports both a high-level budget view and a closer look at one campaign.
For example, an Instagram promotion for corporate event planning could be recorded as Paid social, Instagram, Event planning campaign, and Corporate events ad. The landing page might be the corporate-events service page, grouped under services. A different visitor arriving through organic search would still receive a channel value, even though no advertising tag was present, giving a fuller picture of lead origins.
How stored attribution improves on raw UTM capture
A small site script examines UTM values, referrer information, and related signals, assigns the visit to a channel such as Paid Search, Organic Search, or Paid Social, and stores that result in a browser cookie. When a form is completed, the stored values populate the hidden fields. Because the data is held in the cookie, it can survive a move from a campaign landing page to a separate quote page.
Categorisation also reduces messy reporting. If advertising tags vary between Google, google, and adwords, raw capture would create separate sources in a CRM. Assigning those visits to Paid Search keeps them together. Landing-page capture adds another layer: content groups can be compared by the leads, customers, and revenue they generate, not only by visits.
Where to send the data and four reports to run
Once a submission is stored, review it under Avada Forms, include the attribution fields in lead notification emails, or pass the record to a CRM or spreadsheet. The destination choice depends on where follow-up already happens: sales teams usually need CRM fields, while smaller teams may start with a spreadsheet.
Four reports make the data useful. Leads by Channel shows monthly volume across every origin and helps test whether budget matches the channels producing enquiries. Leads by Facebook Ads Network compares placements such as Instagram and Messenger. Customers by Google Ads Campaign separates paying customers from enquiries that never convert. Revenue by Keyword, when keyword values are included in advertising tags, shows which search terms produced income and where bids might be increased.
| Hidden field | What it records | Reporting use |
|---|---|---|
| Channel | Broad source category | Budget allocation by channel |
| Channel Drilldown 1 | First level of campaign detail, such as platform | Compare platforms within a channel |
| Channel Drilldown 2 | Second level of campaign detail | Compare campaigns |
| Channel Drilldown 3 | Third level of campaign detail, such as ad | Compare individual ads |
| Landing Page | First page visited | See which entry pages generate leads |
| Landing Page Group | Category of the first page | Compare content groups |
Field names are as listed in the original workflow; confirm exact field-name spelling in the live form before mapping to a CRM.
| Report | Question it answers | Likely action |
|---|---|---|
| Leads by Channel | Which origins produce enquiries each month? | Rebalance budget toward productive channels |
| Leads by Facebook Ads Network | Which placements drive enquiries? | Shift spend toward stronger networks |
| Customers by Google Ads Campaign | Which campaigns produce paying customers? | Expand strong campaigns and pause weak ones |
| Revenue by Keyword | Which keywords produce revenue? | Raise bids on profitable terms |
Report examples are illustrative; available dimensions depend on the tags and fields actually captured.
Frequently asked questions
What is the shortest setup sequence for Avada forms?
Add UTM parameters to every paid and campaign link first, add six hidden fields to the form, let the attribution code fill those fields from the visitor's stored channel data, then submit a test entry and check the submission, notification email, CRM, or spreadsheet destination.
Why not pass raw UTM values straight into a CRM?
Raw values can split one source into several records when capitalisation or naming differs, such as Google, google, and adwords. Categorising the visit into a standard channel before writing it to the form keeps reporting grouped consistently.
What happens if a visitor lands on one page and submits on another?
Storing the attribution data in a browser cookie means the values remain available when the visitor moves from a landing page to a separate quote or contact page, instead of only working when both happen on the same page.
Which six hidden fields should the form contain?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Together they record the broad channel, progressively more specific campaign detail, and the entry page and its grouping.