Skip to content

Capture UTM Parameters in Divi Forms

Visitor counts alone do not show which campaigns create enquiries. Adding attribution data to each Divi submission connects a name, email or other submitted detail to the channel, campaign, ad and landing page that brought that person to the site.

How the capture works

A small attribution snippet placed on the site examines UTM values and referrer information, groups the visit into a channel such as Paid Social, Paid Search, Organic Social, Organic Search, Direct or Referral, and stores that result in the browser. When a visitor later submits a form, the stored values are written into hidden fields on that form. The submission therefore carries both the visitor's answers and the attribution context, instead of relying only on the URL of the page where the form happens to sit.

Setup checklist and field map

Use this sequence for each Divi form that should record attribution:

  • Install the attribution snippet on the website, following the installation method that matches the theme and plugins in use.
  • Open the target form in Divi and add six hidden fields, one for each item in the field map below.
  • Confirm that the field names match the attribution values exactly, so the stored channel and drill-down data can populate them.
  • Submit a test enquiry from a tagged campaign link and check that the hidden values arrive with the visible answers.
  • Decide where submitted data should go next, such as a form database, an email notification, a CRM or a spreadsheet.

Field map:

  • Channel: the broad source category, for example Paid Social.
  • Channel Drilldown 1: the platform or network, for example LinkedIn.
  • Channel Drilldown 2: the campaign name.
  • Channel Drilldown 3: the specific ad.
  • Landing Page: the first page the visitor reached.
  • Landing Page Group: the category of that landing page.

In Divi, each field is created by opening the form, choosing Hidden Field in the Type dropdown, and repeating the process for all six fields.

Worked example

Suppose a law firm promotes a business-law consultation through a LinkedIn advertisement. A visitor who arrives from that advertisement and then completes a Divi form could produce a submission where Channel is Paid Social, Channel Drilldown 1 is LinkedIn, Channel Drilldown 2 is the legal consultation campaign, and Channel Drilldown 3 is the business law ad. The landing page fields show where the journey began. That combination makes it possible to see not only that a lead arrived, but which platform, campaign and creative were involved.

Why grouped attribution beats raw UTM values alone

Raw UTM capture has three common weaknesses. First, it may cover only paid campaigns, leaving organic and direct visits unclassified. Second, values are lost when a visitor lands on one page and submits a form on another, unless the values are stored in the browser. Third, inconsistent tagging creates fragmented reporting: Google, google and adwords can appear as separate sources for what is effectively the same activity. Grouping visits into standard channels and normalising formatting avoids that fragmentation. Recording the landing page and its group also shows whether blog posts or other content pages are generating enquiries, rather than only counting traffic.

Reports and next uses for the captured data

Once attribution fields travel with submissions, the same data can support several practical reports:

  • Leads by Channel: monthly lead volume split across Paid Search, Organic Search, Paid Social, Organic Social and other channels, helping decide where to invest next.
  • Leads by Facebook Ads Network: lead volume across Meta properties such as Facebook, Instagram, Messenger and WhatsApp, helping shift spend toward the network producing enquiries.
  • Customers by Google Ads Campaign: closed customers grouped by campaign, showing which campaigns produce revenue rather than only clicks or leads.

Captured submissions can also be reviewed in a form database, included in lead notification emails for immediate visibility, sent to a CRM such as Salesforce, Pipedrive or HubSpot, or exported to Google Sheets or Microsoft Excel for analysis.