Skip to content

Capture Google Ads Data in Drift Chats

Visitor counts alone do not show which campaigns produce leads or paying customers. This guide explains how campaign information can travel with a Drift conversation, so reporting can connect chats to the advertising that prompted them.

Why attach campaign data to a chat?

Analytics tools commonly record visits without showing which of those visitors later became leads or customers. Attaching campaign information to each Drift chat closes that gap: the conversation record can show how the visitor originally found the site, and downstream reporting can group leads and customers by campaign.

Four-step setup checklist

Follow these four steps in order:

  • Add UTM parameters to Google Ads URLs. Use paidsearch for medium, google for source, the campaign name for campaign, the ad group name for term, and the specific ad for content.
  • Install the attribution snippet on the website, either through the site's settings or custom-code area or through a tag manager such as Google Tag Manager.
  • Let the attribution pass campaign details through when a visitor opens a Drift chat.
  • Use the captured details in Drift, send them to a CRM, export them to a spreadsheet, or connect them to a reporting tool.

A useful check is to click a tagged ad, browse to another page, and then start a chat. The chat should still show the original channel and campaign drilldowns rather than a blank or direct source.

How the UTM pattern maps to Drift fields

UTM parameters are short labels appended to a URL. They identify the campaign, ad group and ad behind a visit. A consistent naming pattern matters more than the exact values: keep medium, source, campaign, term and content consistent across ads so reports group results cleanly.

For example, a campaign named brand-campaign can be identified with paidsearch as the medium and google as the source. When that visitor later starts a chat, the passed-through fields can read as Paid Search, Google, the campaign name, and the specific ad name.

Why stored attribution and landing-page data matter

The attribution layer remembers the original UTM values as the visitor navigates. That distinction matters because the landing page often contains no campaign labels after the first click. Without stored attribution, a chat started several pages later can lose its advertising source.

The same layer can also record the first page visited and the group that page belongs to. A blog URL, for example, can be stored both as the full landing page and under a blog group, making it possible to compare performance by section or by individual page.

Three reports to build from the captured data

Once campaign data sits beside each chat, three practical reports become possible:

  • Leads by channel: compare monthly lead volume across paid search, paid social, organic search and other channels, then check whether spend matches the channels producing leads.
  • Customers by Google Ads campaign: separate campaigns that create paying customers from campaigns that mainly create visits.
  • Revenue by keyword: connect new-customer revenue to the search term behind the click, so budget can follow terms that produce income rather than only traffic.

These reports answer different questions. Channel reporting guides overall budget mix, campaign reporting guides which ads to scale, and keyword reporting guides which search terms deserve more investment.

Coverage beyond Google Ads and a customer example

Attribution is not limited to Google Ads. The same approach can record sources such as Facebook Ads, organic search and LinkedIn posts, giving a fuller view of where leads originate. That broader coverage helps compare channels on a consistent basis instead of treating chat leads as unattributed. It also makes channel comparisons fairer, because every lead carries a source rather than only the ones that arrived through a tagged ad campaign. A useful evaluation question is whether chat-originated leads currently appear in reporting with a source at all, or whether they sit in a separate bucket that never gets compared with other channels. If they do sit apart, the first improvement is usually to apply the same source fields to every chat, not just to paid campaigns.

Getting started

Start by tagging ads consistently, installing the snippet, testing a chat after browsing, and confirming that campaign fields appear in Drift and in the chosen CRM or reporting destination. A short test plan helps: click a tagged ad, move to a second page, open a chat, and check that the original channel and campaign values are still present. Then repeat the check in the CRM or reporting tool to confirm the fields arrive intact. Before publishing any offer, confirm the current trial duration, setup time and signup process, since these terms can change.

Frequently asked questions

What is the basic setup for capturing Google Ads data in Drift?

Add UTM parameters to the ad URL, install the attribution snippet on the site, and let it pass the stored campaign details into Drift when a chat begins. The details can then be viewed in Drift or sent onward to a CRM, spreadsheet or reporting tool.

Does the campaign data survive browsing before the chat?

Yes. The attribution is retained while the visitor moves through the site, so a chat started after browsing several pages can still carry the original campaign information.

Where can the captured Drift data be used?

The captured details can be viewed beside the conversation in Drift, sent to a CRM such as Salesforce, Pipedrive or HubSpot for dashboards, exported to a spreadsheet, or connected to a reporting and visualisation tool.