Capture UTM Parameters in Intercom
Website analytics can show campaign visits, but chat leads often arrive without the campaign context that explains why they contacted you. Capturing attribution data at the moment a new Intercom conversation starts connects that conversation to its originating channel, campaign and keyword, so the same context can follow the lead into your CRM and reporting tools.
A practical setup checklist
Use this checklist before you start: confirm who owns the website snippet, who owns the Intercom workspace, which CRM or spreadsheet will receive the data, and which channel names you want in reports. Install the snippet through your site settings or a tag manager, then test with a tagged landing page, several internal page views, and a new chat. Check that the chat shows the expected channel, campaign and keyword before sending data onward.
Install the snippet and let it remember the first visit
First, add the small website snippet supplied by Attribution Analytics after account creation. The exact placement depends on your platform and may be done in site settings or through a tag manager. Once installed, the tool records where each visitor came from and groups that origin into channels such as Paid Search, Paid Social, Display and Organic Search. It stores the information in the browser, so moving through pages or returning later does not erase the original campaign context.
Pass attribution data with each new chat
When a visitor opens a new Intercom chat, the stored attribution data travels with that conversation. In the worked example, a visitor who arrived from a Google ad and browsed service pages before chatting would be recorded as Paid Search, with Google as the drilldown source, the campaign name as the next level, and the searched keyword as the following level. That structure lets a sales or support team see campaign context without asking the visitor to repeat it.
Send the data where reporting happens
View the fields directly in the Intercom conversation, send them to a CRM such as Salesforce, HubSpot, Pipedrive or Zoho CRM for lead and customer reporting, or route them through a tool such as Zapier into a spreadsheet for analysis in Looker Studio or Power BI. The key decision is consistency: use the same channel and campaign fields everywhere so chat leads can be compared with form leads.
Why persistence, clean channels and click IDs matter
A URL-only approach fails when parameters disappear after the landing page. Browser storage solves that browsing gap. Normalisation solves a different problem: the same platform may be tagged as Google, google.com or adwords, which would otherwise split one source into three. Click IDs add another layer, allowing offline conversion data to be returned to Google, Microsoft or Meta when a chat becomes a lead or customer. Additional context such as days to first chat and number of visits before conversion helps distinguish quick responders from longer research journeys.
Four reports to build first
Start with leads by channel to see the overall mix, then drill into the Meta network for social placements, customers by Google Ads campaign for budget decisions, and revenue by keyword where keyword values are included in tracking templates. Together these views move reporting from visits to business outcomes: which channels create leads, which campaigns create customers, and which keywords create revenue.
| Field | Example value | What it tells you |
|---|---|---|
| Channel | Paid Search | Broad origin category |
| Channel Drilldown 1 | Platform or source | |
| Channel Drilldown 2 | Office 365 Support Campaign | Campaign name |
| Channel Drilldown 3 | Office 365 Support Providers Near Me | Searched keyword |
Illustrative example from a Google Ads visit; campaign and keyword values vary by account
| Report | Primary question | Decision it supports |
|---|---|---|
| Leads by Channel | Which channels create leads? | Where to focus effort and budget |
| Leads by Meta Ads Network | Which Meta placement creates leads? | Which social platform to prioritise |
| Customers by Google Ads Campaign | Which campaign creates customers? | Where to increase or reduce spend |
| Revenue by Keyword | Which keyword creates revenue? | Where to adjust bids |
Report types described in the source; exact metrics depend on CRM data available
Frequently asked questions
How do UTM parameters get into Intercom?
Install the attribution snippet on your website, let it store first-visit source data in the browser, and pass that data with each new Intercom chat. You can then view it in Intercom or send it to a CRM, spreadsheet, or dashboard tool.
Does this only work for paid ads?
Yes. The approach described covers organic and referral traffic as well as paid campaigns, so reports are not limited to visitors who arrived through tagged ads.
What if a visitor browses several pages before chatting?
Storing the data in the browser helps preserve it when a visitor moves between pages or returns later, instead of relying on parameters still being present in the chat-start URL.
Can click IDs be captured too?
Click identifiers such as GCLID, FBCLID and MSCLKID can be passed with the chat, which can support offline conversion tracking back to the relevant ad platform when a lead or customer conversion occurs.
Why normalise UTM values?
Normalising source variations into a consistent channel reduces manual cleanup when different people or agencies tag the same platform differently.