Capture UTM Parameters in ExpressionEngine and Send Them to Your CRM
Knowing which campaigns create leads, customers and revenue is the practical reason to capture campaign tags on an ExpressionEngine site. When attribution travels with a form submission into the CRM, reporting can compare channels on the same basis instead of relying on memory or separate spreadsheets.
1. Tag campaigns consistently
Tag every paid and owned campaign before visitors arrive. Social placements, search ads, trade-publication ads and email sends are all suitable places for consistent UTM values. The tags give the attribution code an explicit starting point for recognising the visit.
2. Add six hidden fields to forms
Add six invisible fields to each lead-capture form. Depending on the form extension, drag in a hidden-field type or mark an existing field as hidden in its properties. The fields are: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; and Landing Page Group. These names are the control map to match in the form builder and in the receiving CRM.
3. Let attribution fill the fields at submission
A small attribution script on the site examines UTM values together with referrer and device signals, groups the visit into a channel such as Paid Search or Organic Search, and stores the result in a browser cookie. At submission it fills the hidden fields, so the values survive a move from a campaign landing page to a separate quote or demo form.
Worked example
Consider a visitor who finds a paid search ad for a CRM product, lands on a comparison page and then opens a demo-request form. The completed record could show Channel as Paid Search, the first drilldown as the search platform, the second as the campaign name, the third as the ad name, plus the exact landing page and its page group. That combination lets a report separate the platform, campaign and creative while still showing which page first earned the lead.
4. Send the record to the CRM and verify it
On successful submission, the hidden-field values are sent with the lead's name, email, company and phone number. ExpressionEngine integrations can forward the record to a CRM or email platform, and a connector such as Zapier can route it to a spreadsheet or another destination. Useful checks before launch: confirm all six fields exist, submit a test lead from a tagged campaign, verify each value in the CRM, then repeat the test from an untagged organic visit.
Why normalised attribution beats raw UTM values
Raw UTM capture alone misses visits without tags, loses values when the form sits on a different page, and can fragment one platform into several spellings. A normalised attribution layer addresses all three: it classifies every visit, remembers the first-touch values in a cookie, and maps inconsistent tag variants to one channel. It also records the landing page and its group, so individual posts and whole content sections can be compared for leads, customers and revenue.
Reporting questions this setup can answer
Once records arrive consistently, the CRM can answer direct questions such as how many leads came from a social campaign, how many customers came from search ads, and how much revenue a professional-network campaign produced. That is the decision value: budget and content effort can follow measured return rather than guesswork. If you want to evaluate a trial, check the current plan details and eligibility directly before relying on any specific duration or terms.
Frequently asked questions
Does this only work for paid campaigns with UTM tags?
No. Attribution can also be inferred from referrer and device information, so organic search, organic social, direct and referral visits can be classified even when no UTM tags are present.
What if the visitor lands on one page but submits the form on another?
Yes, because the attribution values are stored in a browser cookie when the visitor first arrives. They remain available when the form is completed on a later page.
Why not pass raw UTM values straight to the CRM?
Inconsistent tagging such as different capitalisation or abbreviations for the same platform can split one source into several CRM values. Normalising those variants into a single channel avoids manual stitching during reporting.