Skip to content

Capture UTM parameters in Zoho SalesIQ and carry them into your CRM

Website analytics can show visits, but not reliably which visit became a chat, lead, or customer. The workflow below preserves campaign attribution from the landing page through a new Zoho SalesIQ chat, then forwards it to reporting tools so channel and campaign performance can be compared on outcomes rather than clicks alone.

1. Install the attribution snippet and record the first visit

Install a small attribution snippet on the website, using the platform settings or a tag manager where applicable. Once present, it records the visitor's arrival source and groups it into channels such as Paid Search, Paid Social, Organic Search, Display, Organic Social, Direct, and Referral. Storage in the browser keeps the original arrival details available after internal navigation or a later return visit.

2. Attach attribution to each new chat

When a visitor opens a new Zoho SalesIQ chat, the stored attribution fields travel with that conversation. In the worked example, a visitor who arrived from a Facebook ad, browsed service pages, and then chatted would carry Paid Social as the channel, Facebook as the first drill-down, the campaign name as the second, and the ad name as the third. That chain lets a sales conversation be traced back to a specific ad rather than only to a platform.

3. Verify the handoff end to end

Checklist before reporting: confirm the snippet loads on landing pages, start a test chat after browsing at least one additional page, verify channel and drill-down fields appear in the chat, confirm the same fields reach the CRM or spreadsheet destination, and test a non-paid arrival such as Organic Search or Direct. Also check that click IDs and visit-count or time-to-conversion fields, where available, are present for offline conversion work.

4. Why persistence and normalisation matter

Browser storage matters because UTM parameters often disappear from the address bar after the first page. A visitor may land from an ad, read several pages, and only then start a chat; relying on the current URL at chat time would lose the original campaign. Remembering the first-visit values across browsing and return visits avoids that gap. Normalising inconsistent tags also helps: variants such as different spellings for the same search source should roll up into one channel instead of fragmenting reports.

5. Use click IDs and journey context for offline conversions

Beyond UTM values, click identifiers such as GCLID, FBCLID, and MSCLKID can be passed with the chat so a lead or later customer conversion can be sent back to the advertising platform for offline conversion measurement. Additional context, including days from first visit to first chat and number of visits, helps distinguish immediate enquiries from longer consideration journeys.

6. Turn chat attribution into four practical reports

Send chat attribution into a CRM such as Salesforce, HubSpot, Pipedrive, or Zoho CRM, or route it through an automation tool to a spreadsheet and then to a dashboard platform. Once stored alongside lead and customer outcomes, four starting reports are useful: monthly leads by channel to spot budget mismatch, leads by Meta network to compare Facebook, Instagram, Messenger and other placements, customers by Google Ads campaign to scale winners, and revenue by keyword when keyword values are included in Google Ads tracking templates.

Starting report map
ReportQuestion it answersDecision it supports
Leads by channelWhich channels produce monthly lead volume?Rebalance spend toward channels producing leads, not only visits.
Leads by Meta networkWhich Meta placement produces the most leads?Shift budget toward the strongest network and reduce weak placements.
Customers by Google Ads campaignWhich campaign produces customers each month?Scale winning campaigns and pause or reduce underperformers.
Revenue by keywordWhich searched terms produce revenue?Raise bids on proven keywords and tighten spend on weak terms.

Use only where chat attribution is joined to lead, customer, or revenue outcomes in the destination system.