How to Track UTM Parameters in Zoho Analytics
Zoho Analytics can turn stored marketing data into reports and dashboards, but it can only report on what your CRM or data warehouse already holds. To see which channels and campaigns produce leads, customers and revenue, you first need to capture the UTM parameters and related attribution details that arrive with your visitors. This guide walks through the capture and reporting workflow, then explains how a dedicated attribution tool can fill gaps that raw UTM capture leaves behind.
Why capture has to come before reporting
Zoho Analytics is a business intelligence tool that connects with other Zoho products and makes it easier to build reports and dashboards. Like most analytics tools, however, it depends on data that has already been collected and stored. If your CRM or data warehouse does not contain the UTM parameters your leads arrived with, Zoho Analytics has nothing to group by campaign or channel. The practical sequence is therefore: tag your campaigns, capture the attribution data at the point of conversion, store it alongside the lead or customer record, and only then connect that data to Zoho Analytics for reporting.
What an attribution tool adds to the workflow
A small code snippet placed on your site can examine the UTM parameters in the URL each time a visitor arrives. From that information it groups the visitor into a channel such as Organic Search, Paid Social or Paid Search, and stores the grouped data in the visitor's browser as a cookie. When the visitor submits a form, the UTM parameters and other attribution details, including the landing page, can be sent into your CRM or backend tools. From there the data can flow into Zoho Analytics. This is the role an attribution tool plays in the workflow.
The four-step workflow
The workflow has four stages. First, add UTM parameters to existing and future ads and campaigns so the capture tool can identify where traffic originates. This covers social ads on networks such as Twitter, Facebook and LinkedIn, search ads on Google and Bing, and bespoke campaigns in trade publications, email newsletters and similar placements. Second, add the attribution code to your website. A signup provides a snippet that is installed in the same way as a Google Analytics or other marketing tool's code, either through your CMS settings or through a tag management service such as Google Tag Manager. Further installation instructions are available on the tool's help site. Third, send the captured data to your CRM or another backend tool. Fourth, connect that stored data to Zoho Analytics and build reports and dashboards that break key customer acquisition metrics down by channel or campaign.
Choosing how to move attribution data into your backend
Once the code is running, the attribution tool can monitor how each visitor arrived and categorise them into a channel, storing the result in a cookie. To get that data into your CRM or another backend system, there are two practical routes. The first is to add hidden fields to your website forms. The attribution tool writes the UTM parameters and other attribution data into those fields, and when the form is submitted the values travel with the lead's name, email, number and other details. The second route is to retrieve the data from the cookie with a short line of JavaScript. That approach is useful when visitors can sign up through a 'Sign up with Google' or 'Sign up with Facebook' button without completing a form.
A quick decision checklist for the capture method
Use this checklist to choose between hidden form fields and cookie retrieval. Choose hidden fields when every conversion happens through a standard form, when your form builder supports hidden fields, and when you want the attribution values to arrive with the same submission as the lead's contact details. Choose cookie retrieval when visitors can convert without a form, such as through social sign-up buttons, or when you need to read the stored attribution data at a later point in the journey. In either case, confirm that the captured fields are mapped into your CRM or data warehouse before you connect that source to Zoho Analytics.
Worked example: a Facebook Ad that converts on a second page
Imagine a visitor clicks a Facebook Ad and lands on a campaign landing page. After exploring, they click a 'Get A Quote' button and complete the quote request form on a different page. A capture method that only reads UTM parameters from the page where the form is submitted would lose the campaign information, because the form page is not the page the visitor first arrived on. A cookie-based capture tool avoids that loss: it stores the UTM parameters in the visitor's browser, so the values remain available no matter how many pages the visitor views before submitting the form, and they can still be passed into your CRM.
Two different data problems, two different fixes
It helps to separate two failure modes that look similar in reports. The first is messy raw UTM values. If some Facebook ads use UTM_Source=Facebook, others use UTM_Source=facebook and others use UTM_Source=fb, a report built on raw values can show three separate sources and mislead you. A tool designed to expect those inconsistencies can group them into the correct channel. The second problem is missing UTM parameters altogether. Visitors who arrive through Organic Search, Paid Search, Organic Social or Direct may have no UTM parameters in the URL. A capture tool that also gathers attribution information for those channels lets you see where every lead and customer came from, not only those from tagged campaigns.
Landing page data adds a second reporting dimension
UTM parameters are not the only useful attribution field. A capture tool can also record the landing page, such as a specific blog post URL, and its category, such as /blog. With that data in Zoho Analytics you can compare how different sections of your website perform in terms of leads, customers and revenue, and you can also examine an individual page's contribution. This is useful when you want to know how many leads your blog generated or how a particular content piece performed, rather than only which campaign brought the visitor in.
Questions the reports can answer
Once attribution data reaches Zoho Analytics, the reports can address questions such as how many customers Google Ads generated, how the deal size of LinkedIn Ads customers compares with Facebook Ads customers, how much total revenue the blog generated, and what the overall ROI of all campaigns is. More granular questions include how many leads Facebook Ads produced, which LinkedIn Ad campaigns got the most leads, how many sales opportunities came from Twitter Ads, which Facebook Ads campaigns drove the most pipeline, how many customers came from Google Ads, and how much revenue came from SEO efforts.
Field and control map for the capture step
The capture step involves a small set of moving parts. The UTM parameters in the URL are the raw input. The attribution tool reads them and assigns a channel. The channel and related attribution details are stored in a browser cookie. Hidden form fields or a JavaScript read from the cookie move the values into your backend. Your CRM or data warehouse stores the values alongside the lead or customer record. Zoho Analytics then reads that stored data to produce reports and dashboards. Before building reports, check that each field you intend to report on is actually present in the stored data and mapped consistently.
Frequently asked questions
Why can't Zoho Analytics report on UTM parameters by itself?
Zoho Analytics reports on data that has already been captured and stored in your CRM or data warehouse. If the UTM parameters were never recorded with the lead or customer, there is nothing in the connected data for Zoho Analytics to group by campaign or channel.
Should I use hidden form fields or read the cookie?
Hidden form fields suit conversions that happen through a standard form and let the attribution values arrive with the same submission as the lead's contact details. Reading the cookie with JavaScript is useful when visitors can convert without a form, such as through social sign-up buttons.
Why do UTM parameters sometimes disappear before the form is submitted?
A capture method that only reads UTM parameters from the page where the form is completed will lose them if the visitor first landed on a different page. A cookie-based capture tool stores the values in the browser, so they remain available across page views and can still be passed to your CRM.
What happens if my UTM source values use different capitalisation or abbreviations?
Raw values such as Facebook, facebook and fb can appear as three separate sources in a report. A capture tool designed to expect those inconsistencies can group them into the correct channel, which gives you cleaner channel reporting in Zoho Analytics.
Can I report on traffic that arrives without UTM parameters?
Yes, if your capture tool also gathers attribution information for channels such as Organic Search, Paid Search, Organic Social and Direct. That way you can see where every lead and customer came from, not only those from campaigns with UTM tags.