Capture UTM Parameters in TYPO3 and Pass Them to Your CRM
If you cannot see which campaigns create leads, you cannot judge which marketing work is paying off. This guide explains how to capture campaign tags from a TYPO3 visit, keep them attached to a lead form submission, and send them onward so channel reporting in your CRM reflects the visit that started the journey.
Start with tagged campaigns
Tracking starts before the form. Add UTM parameters to every campaign you run — paid search, paid social, email, display and social posts — so the arriving visit carries a consistent description of its origin. Without tags on a campaign, later reporting has to infer the source from other signals and will be less precise.
Once tags are in place, the goal is not simply to record a page view. It is to attach the origin to the eventual enquiry, so a lead created days or pages later can still be grouped by the campaign that brought the person to the site.
How the attribution values are preserved and filled in
A small attribution script placed on the site reads signals on arrival — UTM parameters, referrer and device among them — groups the visit into a channel such as Paid Search, Organic Search or Paid Social, and stores that result in a browser cookie.
When a visitor later submits a form containing the hidden fields, the script writes the stored attribution values into those fields. Because the values are held in a cookie rather than read only from the current URL, they survive a move from a campaign landing page to a separate quote or contact page. That distinction matters: a method that only reads parameters on the form page loses the origin whenever the form sits on a different page from the entry page.
Worked example: from ad click to submitted lead
Consider a visitor who finds a paid search ad, lands on a feature page, then completes a quote form elsewhere on the site. The submitted record could show:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand Campaign
- Channel Drilldown 3 = Dropbox
- Landing Page = www.dropbox.com/features/share
- Landing Page Group = Features
The first four values describe how the visitor arrived; the last two describe which content they first saw. Together they let you report on both campaign performance and the pages that introduce people to your offer, rather than on clicks alone.
Send the values to your CRM and report on them
On submission, the hidden-field values are sent alongside the lead's name, email or phone. From there, TYPO3's native integrations or a connector such as Zapier can forward the record to a CRM or other tool — examples named in the underlying material include Salesforce, HubSpot, Pipedrive and Zoho CRM.
With that data in place, reports can answer practical questions: how many leads came from a social ad, how many customers originated in paid search, and how much revenue is associated with organic search work. Landing-page fields extend the same idea to content, showing whether blog posts or other pages generate leads and customers.
Why channel grouping beats raw UTM values alone
Raw UTM values alone can fragment reporting. If some campaigns use one spelling for a source and others use a synonym, the same channel appears as several separate sources in a CRM report. Grouping visits into standard channels first — for example, treating variant paid-search labels as Paid Search — produces cleaner totals.
Attribution capture also covers visits without UTM parameters, such as organic search, organic social, direct and referral traffic. That gives a fuller picture of productive channels instead of only ranking the paid campaigns you happened to tag.
Before you rely on the reports, run a short end-to-end check: visit through a tagged campaign link, navigate to a different page, submit a test form, and confirm that Channel, the three drilldowns, Landing Page and Landing Page Group all arrive in the CRM record. Then repeat with an untagged organic visit to confirm it is classified rather than left blank.