Track the source of leads in Divi forms
A Divi form submission normally tells you who contacted you, but not how they found you. Adding attribution data to the form lets you connect each enquiry to the channel, campaign and landing page that produced it, so reporting can show which activity is generating leads and customers rather than just counting submissions.
Three steps to capture lead source data
The workflow has three parts. First, install the attribution code on the website and add hidden fields to the Divi form. Second, the tool records where the visitor came from and fills those hidden fields when the form is completed. Third, Divi captures the hidden values together with the visible answers, such as name, phone number and email address.
Checklist before you start:
- The site snippet is installed on every page where a tracked form can be submitted.
- Each Divi form has the hidden fields listed below, using the Type value Hidden Field.
- A test submission confirms the hidden values arrive in the destination you will actually use, whether that is the WordPress entries table, a notification email, a CRM or a spreadsheet.
- Hidden fields add no extra questions, so visitors do not need to complete anything additional.
Hidden fields and the data they carry
Add one hidden field for each of these names: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. In Divi, open the form, add a field, choose Hidden Field from the Type dropdown, and repeat until all five are present.
What the fields mean in practice:
- Channel gives the broad source, for example Paid Search or Organic Search.
- Drilldown 1 narrows it to the platform, for example Google.
- Drilldown 2 can carry the campaign name or the search domain used.
- Drilldown 3 can carry the keyword or other campaign detail, depending on the source.
- Drilldown 4 provides an additional level of detail when the earlier fields are not specific enough.
Example — a paid search visit: Channel is Paid Search, Drilldown 1 is Google, Drilldown 2 is the campaign name, and Drilldown 3 is the keyword that was searched.
Example — an organic search visit: Channel is Organic Search, Drilldown 1 is Google, Drilldown 2 is the Google domain used, and Drilldown 3 is the keyword used to find the site, where that information is available.
Landing-page data is captured separately: the first landing page URL and the group that page belongs to. If a visitor first arrives at a blog post, the URL identifies that post and the group can roll it up to the blog section, making it possible to compare sections of the site as well as individual pages.
Where the captured data can go
Once the hidden values are submitted with the form, choose one or more destinations:
- WordPress dashboard: view the values in the entries or submissions table, using a plugin that stores and displays Divi submissions.
- Notification emails: include the attribution fields in the email Divi sends on each submission, so the recipient sees the source without opening another system.
- CRM: send the fields to a CRM such as Salesforce, HubSpot or Pipedrive, where they can be stored against the lead record.
- Spreadsheet: export through an add-on or a tool such as Zapier for analysis outside the CRM.
A common failure is treating a successful test in one destination as proof for all of them. Test each destination separately, because a field that appears in the WordPress table may not be mapped into the email template or the CRM record.
Three reports to run first
With attribution fields stored on every lead, three reports are a useful starting point:
- Leads by channel: count leads per month across channels such as Paid Social, Organic Search and Paid Search. Compare that pattern with spend; if most leads arrive through one channel while most budget goes to another, the allocation deserves review.
- Leads by Google Ads campaign: count leads per month by campaign. This shows which campaigns produce enquiries, not just clicks, and where budget should be focused.
- Leads by social network: break social leads down by platform, such as Facebook, Twitter or LinkedIn. Post more often on the networks that produce leads and investigate the ones that do not.
Start with the channel report to set direction, then use campaign and network reports to decide where to act.
Wrap up
Hidden attribution fields turn a basic Divi submission into a record of where the lead came from. Install the site code, add the five hidden fields, test a submission end to end, and route the data to the dashboard, email, CRM or spreadsheet you will report from. Before publishing any trial or pricing call to action, confirm the current package details and trial terms, since those commercial specifics are not established here.