Skip to content

Capture UTM Parameters in Joomla and Pass Them to Your CRM

If you cannot tie leads, customers and revenue back to the campaigns that produced them, you cannot tell which marketing work is paying off. The workflow below connects Joomla form submissions to the channel and landing-page context that arrived with the visitor, so reporting in a CRM or spreadsheet can show campaign return rather than just form volume.

Four-step checklist for Joomla

Use this four-step checklist before you build reports:

  • Tag every paid and bespoke campaign link with UTM parameters, including social and search ads, trade-publication placements and email sends.
  • Add the six hidden fields listed below to each Joomla form that should carry attribution data.
  • Confirm the attribution script is present on the site so it can read arrival data and populate those fields.
  • Submit a test form from a tagged link and verify that channel, drilldown and landing-page values arrive in the CRM or spreadsheet alongside name, email and phone.

Tagging only paid links is a common gap. Organic search, organic social, direct and referral visits have no UTM values to read, so a method that depends solely on URL parameters will leave those leads unattributed in reporting.

Hidden fields to add to Joomla forms

Joomla form builders named in the workflow include Convert Form, Proforms, Balbooa and Breezing Forms. Each offers a point-and-click route to a hidden field, either through a dedicated hidden field type or by hiding a standard input field.

Add these fields to the form:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

Hidden fields sit on the form but are not shown to the person completing it. Their values are submitted with the visible answers, which is what allows attribution data to travel with the lead record.

Worked example: from paid search click to CRM record

Consider a visitor who searches for a way to share large files, clicks a paid search result, and then completes a demo-request form. The arrival is classified from the UTM values, referrer and device context, grouped into a channel such as Paid Search, and stored in a browser cookie.

When the form is completed, the stored values populate the hidden fields. In this illustration they would read:

  • 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

On submission, those values are sent with the contact details to the chosen destination. The form builder's native integrations can forward the record to systems such as Salesforce, HubSpot or Microsoft Dynamics, or to a spreadsheet. A connector such as Zapier can route the same record to Google Sheets, Excel and many other destinations.

Why classified attribution differs from raw UTM capture

Raw UTM capture and classified attribution are not the same thing, and the difference matters in three situations.

First, coverage. Raw capture only records visits carrying UTM parameters. Classified attribution also assigns organic search, organic social, direct and referral visits to channels, so CRM reports can account for all leads rather than only paid-campaign leads.

Second, persistence. Raw capture fails when the form page differs from the landing page, because the parameters are no longer in the URL. Storing the classification in a cookie means the values survive navigation to a later page, such as moving from a campaign landing page to a separate quote-request form.

Third, consistency. Raw values preserve every spelling variation. If one campaign uses a capitalised source name and another uses lowercase, a CRM will treat them as separate sources. Classified attribution normalises those variations and assigns both to the same channel, such as Paid Search, which keeps reporting clean when different people or agencies have managed the same account over time.

Landing-page capture adds a fourth distinction. Recording both the exact landing page and its group lets you compare individual pages against whole sections, for example judging whether a blog section as a whole, or one long-form article within it, is generating leads and revenue.

How the attribution flow works, and a final test

The attribution code placed on the site examines UTM parameters, referrer and device information to work out how a visitor arrived. It sorts the visit into channels including Organic Search, Paid Search and Paid Social, stores the result in a cookie, and uses that stored result to complete hidden form fields. When the form is submitted, the attribution values travel with the lead's name, email and phone number to the CRM or other tool.

Before relying on the data, run one end-to-end test from a tagged campaign link, confirm the six hidden fields are populated, and check that the values appear correctly in the destination system. Repeat the test from an untagged organic visit to confirm it is classified rather than left blank.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.