Skip to content

How to integrate Google Analytics data into your CRM

Google Analytics shows website traffic by campaign, but it does not by itself show how many of those visitors became leads, opportunities, customers, or revenue. Sending the channel information captured during a visit into your CRM at the moment a form is submitted closes that gap, so reporting can start from the contact record rather than from visits alone.

Decision checklist: is the integration actually working?

Use this checklist before you build reports:

  • Confirm the website snippet is installed and firing on the pages that host lead forms.
  • Confirm every lead form has the hidden fields listed below, with names matching what your CRM expects.
  • Submit a test form from a tagged campaign link and from an untagged organic visit, then check the resulting CRM record.
  • Confirm the form-to-CRM route: a CRM-native form should create the record directly, while a separate form builder needs its existing native integration or a connector such as Zapier or Make.
  • Only then build channel reports, so missing fields are caught as a setup problem rather than misread as zero performance.

Four steps, in order

The workflow has four stages.

  1. Install the capture code on the website. The code supplied for the integration is added through the website builder or admin area, for example WordPress, Webflow, or Wix.
  2. Add hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Form builders such as Gravity Forms, Typeform, and Jotform support hidden fields.
  3. Let the code classify the visit and populate those fields on submission. Classification uses the same signals Google Analytics uses, including UTM parameters and referring domain, and groups visitors into channels such as Paid Search, Paid Social, Organic Search, and Organic Social. The result is stored in a browser cookie until the form is completed.
  4. Send the submitted values to the CRM and report from there. With a CRM-native form, the values appear on the lead or contact record. With a separate form builder, use the same route already used to send leads to the CRM.

Worked example: paid search versus organic search

A fictional company, Olmo Software, illustrates the difference between paid and organic capture.

For a visitor arriving from a Google Ads click, the fields might read: Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign, Channel Drilldown 3 = Olmo Software. The exact drilldown values depend on the UTM parameters used behind the ads.

For a visitor arriving from an organic search result, the fields might read: Channel = Organic Search, Channel Drilldown 1 = Google or the search engine used, Channel Drilldown 2 = the search engine domain such as www.google.com, and Channel Drilldown 3 = Olmo Software or the searched keyword where available.

The practical lesson is that paid capture is only as good as the UTM naming behind the campaign, while organic capture depends on referrer and search-engine signals. Check both paths with test submissions before trusting the reports.

Four reports worth building first

Once channel fields sit on CRM records, four reports become straightforward. Build them in the CRM, or connect a reporting tool such as Google Data Studio, Microsoft Power BI, or Tableau to the CRM.

  • Leads by Channel: monthly lead count by channel. Use it to compare where leads actually come from against where budget is going.
  • Opportunities by Google Ads campaign: monthly deals or opportunities by campaign. Use it to separate campaigns that generate sales-ready interest from campaigns that generate clicks without conversions.
  • Customers by Facebook Ads network: customers by Meta network, such as Facebook, Instagram, Messenger, or WhatsApp. Use it to focus budget and optimisation on the networks producing customers.
  • Revenue from Organic Search by search engine: revenue attributed to organic search over time, split by search engine. Use it to judge whether SEO work is compounding and how it compares with Paid Search or Organic Social.

Why this matters

Visits alone cannot tell you whether marketing produced pipeline. When channel, campaign, landing page, and drilldown values travel with the lead into the CRM, each record carries its own origin story. That makes it possible to answer, from one place, how many leads came from Google Ads, how many opportunities came from Facebook Ads, how much pipeline came from SEO, and how many customers came from organic social posts. Before committing to any tool for this job, check its current trial length, plan limits, and setup requirements directly with the provider, since those commercial terms vary and should be confirmed rather than assumed.