Skip to content

Capture Google Analytics data in Drift chats

A Drift conversation shows what a visitor asks, but not always how they found you. Attaching first-visit channel and landing-page detail to each chat closes that gap, so you can see which campaigns, search activity, and content are producing conversations.

Before you install: a short readiness checklist

Use this checklist before you start: confirm who can add site code, decide which CRM or spreadsheet will receive chat data, and agree which channel and landing-page fields your team will report on. That planning prevents a common failure: chats arrive with attribution attached, but nobody owns the downstream field mapping, so the data is never used in a report.

Step 1: Add the attribution snippet to your website

Set up an account with the attribution tool you have chosen, copy the small snippet it provides, and place that snippet on your site. Many website platforms offer a settings or dashboard area where you can paste it; a tag manager such as Google Tag Manager is another option. Installation guides for specific platforms are linked below. Once the snippet is in place, open a test chat and check that the attribution fields appear before you depend on the data.

Step 2: Channel and landing-page detail travels with the chat

When a visitor starts a chat, the snippet records how they first reached the site and attaches that detail to the conversation. In a worked example, a visitor who clicks a Google ad for office cleaning might be recorded as Paid Search, with drill-downs naming Google, the office cleaning campaign, and the night cleaning keyword or ad group. The first page they landed on and its group, such as a services page under /services, are recorded alongside. That combination answers two different questions: which channel brought them in, and which content first attracted them.

Step 3: View the data in Drift and send it onward

The attached detail can be viewed next to the chat in Drift. From there, connect Drift to a CRM such as Salesforce, HubSpot, or Pipedrive so new leads or contacts are created with the attribution fields included, or use an automation tool such as Zapier to create contacts elsewhere or write lead data to a spreadsheet. Map the fields at this stage: channel, drill-downs, landing page, and landing-page group should each have a named destination field.

Step 4: Report on where leads come from

With attribution flowing into your CRM or spreadsheet, build dashboards that compare effort with outcome. Useful starting reports include chat leads from Google Ads, chat leads from Meta Ads campaigns, and new leads from SEO. Review them monthly: if a channel produces many chats but few customers, or a low-spend channel produces most leads, that is a prompt to reallocate budget or test new creative.

What gets passed through: channel versus landing page

Channel is the headline classification, using the same broad categories familiar from Google Analytics, such as Paid Search, Organic Search, Paid Social, and Organic Social. Drill-downs add the specifics underneath it, for example the campaign, ad, or keyword behind a paid click. Landing page is the exact first URL visited, and landing-page group is the broader section it sits in. Together they let you separate a channel problem from a content problem: strong traffic with weak chats may point to the landing page, while strong chats from one campaign point to the ad itself.

Three reports to build first

Three reports cover most early decisions. Leads by Channel counts chats per month per channel, including non-paid sources, so you can spot a mismatch between spend and results. Customers by Facebook Ads Network splits Meta results across Facebook, Instagram, Messenger, and WhatsApp, showing which placement earns customers rather than just clicks. Revenue from Organic Search by Search Engine breaks SEO-driven chat revenue down by Google, Bing, and DuckDuckGo, showing which engine actually pays back. Start with one report, act on it, then add the next.

Wrap up

When channel and landing-page detail is attached to every Drift chat, conversations become evidence about marketing performance. Install the snippet, confirm with a test chat that the fields are carried through, map those fields into your CRM or spreadsheet, and report on leads, customers, and revenue by channel. Trial terms and setup time: check the current plan details and estimate your own setup effort before committing.

Field map for chat attribution data
Field passed with chatWhat it tells youExample use
ChannelBroad source categoryCompare Paid Search vs Organic Search leads
Channel drill-downsCampaign, ad, or keyword detailIdentify which paid campaign creates chats
Landing pageExact first URL visitedSee which page first attracted the visitor
Landing-page groupBroader section of that pageCompare service pages vs blog content

Example values are illustrative from a paid-search office-cleaning scenario, not a claim about any specific business.

Frequently asked questions

How do I attach Google Analytics channel data to a Drift chat?

Add the attribution snippet to your website, let it record how each visitor first arrived, and have it attach that channel and landing-page detail when a Drift conversation begins. You can then view the detail in Drift or pass it onward to a CRM or spreadsheet for reporting.

What data is passed through with each chat?

Two main pieces travel with the chat: the channel that brought the visitor in, with drill-down detail such as campaign or keyword where available, and the first landing page plus its broader landing-page group.

What reports become possible after capture?

Once the data reaches your CRM or spreadsheet, you can report leads by channel, customers by ad network, and revenue from organic search by search engine, then compare those results against where you spend time and budget.