Capture UTM Parameters in Drift and Send Them to Your CRM
When a visitor starts a Drift chat, the campaign details behind that visit are often missing from the conversation. Without them, you cannot tell whether the lead came from a paid search ad, a social campaign, organic search, or a referral. Capturing attribution at chat start closes that gap and lets you report on lead and customer sources inside your CRM and dashboards.
Why chat attribution goes missing
Without source data attached to a chat, ad spend looks disconnected from pipeline. A visitor may click an ad, read several pages, and only then open chat. If attribution depends on parameters still being present in the address bar at that moment, the origin is lost. A browser-stored attribution record solves this by preserving the first-visit details until the conversation begins.
Four-step workflow
Install a small site snippet through your site settings or a tag manager. The tool then records each visitor's channel on arrival, grouping sources into categories such as Paid Search, Paid Social, Display, and Organic Search. That record stays in the browser while the person browses, leaves, or returns. When a new Drift chat opens, the stored channel, drill-downs, UTM values, and click identifiers are passed into the conversation.
What a passed-through record looks like
Example: a visitor arrives from a branded paid search click, views multiple pages, then chats. The attached data could read: Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = EcoTech Solutions. The same pattern applies to other channels, with drill-downs reflecting the network, campaign, and term or creative that drove the visit.
Decision checklist
Check these points before relying on reports: 1) Does the snippet load on every page where chat can start? 2) Is first-visit attribution retained across page views and return visits? 3) Are non-UTM sources such as Organic Search, Organic Social, Direct, and Referral also classified, rather than only paid clicks? 4) Are inconsistent source spellings normalised into one channel? 5) Are click IDs such as GCLID, FBCLID, and MSCLKID captured for offline conversion uploads? 6) Does the data appear in the chat view and flow onward to your CRM or spreadsheet?
Cleaner data and full coverage
Raw UTM capture alone can fragment reporting. Variants such as Google, google.com, and adwords would look like three sources. Normalisation maps those variants to a single Paid Search channel. Capturing all traffic also matters: a report limited to tagged paid clicks understates organic and referral contribution and makes budget comparisons unreliable.
Reports to build after capture
Once chat data reaches a CRM such as Salesforce, HubSpot, Pipedrive, or Zoho CRM, build reports by channel, by social network, by search campaign, and by keyword. Channel reports show where leads originate each month. Network reports separate Facebook, Instagram, Messenger, and other placements. Campaign reports link customers to individual Google Ads campaigns. Keyword reports, when keywords are included in UTM tagging, show which search terms produce revenue and may justify higher bids.
Spreadsheets, dashboards, and offline conversions
Alternatively, send chat records through a connector such as Zapier to Google Sheets or Excel, then visualise them in Looker Studio or Power BI. Also use click IDs to send qualified leads and paying customers back to ad platforms as offline conversions, and review time-to-convert and visit count before the first chat to understand buying effort.
| Check | What to verify | Why it matters |
|---|---|---|
| Snippet coverage | Code present on all chat-entry pages | Prevents missing attribution on landing pages |
| Persistence | First-visit data survives browsing and return visits | Parameters are often gone from the URL by chat start |
| Channel classification | Paid and unpaid sources grouped consistently | Enables full lead-source reporting |
| Click IDs | GCLID, FBCLID, MSCLKID captured when present | Supports offline conversion uploads |
| Destination | Data visible in chat and synced to CRM or sheet | Makes reporting possible without manual entry |
Use as an implementation checklist; confirm field names in your own CRM and chat setup.