Skip to main content

SEO, AEO & Lead Generation

Connecting GA4 and Your CRM: Tracking Which Content Produces Real Enquiries

Analytics shows visits and form submissions; your CRM shows which enquiries became customers. Connecting them, by passing source, campaign and landing page data with each enquiry, lets you invest in the content and channels that produce revenue.

All insights3 min readBy APPNEURAL Editorial

Illustrative marketing team reviewing campaign creative and audience performance reports
Illustrative context image

Quick answer

To connect GA4 and your CRM for lead attribution, capture source, medium, campaign, landing page and referrer on the first visit, store them with consent, submit them with each form as hidden fields, save them on the CRM lead record, mark leads as qualified, won or lost in the CRM and report outcomes by source and landing page. Optionally send qualified and won events back to analytics or ad platforms.

Key takeaways

  • Capture first-touch and conversion-page data with each enquiry.
  • The CRM, not analytics, should hold lead quality and revenue.
  • Consistent UTM naming makes reports reliable.
  • Respect consent rules when storing tracking data.

Who this guide is for

Marketing and sales operations teams who cannot tell which pages, campaigns or channels generate qualified leads.

01

Decide what to attribute

At minimum, record for each enquiry: original source and medium, campaign, first landing page, the page where the form was submitted, referrer and date. Optionally record the number of visits before converting. Agree which model you will report, such as first touch, last touch or both, recognizing that all models simplify complex buying journeys.

02

Standardize UTM parameters

Use consistent UTM parameters on campaign links, emails, social posts and ads, with a documented naming convention for source, medium and campaign. Inconsistent tags like “Facebook”, “facebook” and “fb” fragment reports. Do not add UTMs to internal links within your site, as this overwrites the original source in analytics.

03

Capture data on the website

Use a small script to read UTM parameters, referrer and landing page on the first visit and store them in a first-party cookie or local storage, subject to your consent approach. When a visitor submits a form, add these values as hidden fields. This keeps attribution even if the visitor browses several pages before enquiring.

04

Store attribution in the CRM

Map the hidden fields to CRM lead properties. Ensure integrations, whether native connectors or custom APIs, pass them correctly and do not overwrite original values with later ones. For phone and WhatsApp enquiries, use call tracking numbers or ask how the person found you, and record it manually.

05

Record lead outcomes consistently

The CRM must track lead status: qualified, opportunity, won or lost, with deal value where relevant. Without consistent outcome recording, attribution shows only form counts. Make it simple for sales to update statuses, and audit completeness periodically. Use required closure reasons for lost leads, such as budget, timing or poor fit, because these explain why a source produces many enquiries but little revenue and help marketing adjust targeting.

06

Report on what matters

Build reports showing leads, qualified leads, opportunities and revenue by source, campaign and landing page. Compare content pieces by qualified leads produced, not just traffic. Use GA4 for behaviour analysis and the CRM for outcome analysis. Optionally import qualified or won conversions into ad platforms so their bidding optimizes for quality rather than raw form fills.

07

Handle consent and privacy

In many regions, analytics and marketing cookies require consent. Implement a consent management approach that controls tracking accordingly, and use GA4 consent mode if relevant. Explain tracking in your privacy policy. Attribution data will be incomplete for visitors who decline, so treat reports as directional and supplement with self-reported source questions.

Scope checklist

  • Is there a UTM naming convention?
  • Are source, campaign and landing page captured with each form?
  • Do CRM leads store attribution without overwriting it?
  • Are lead outcomes recorded consistently?
  • Is tracking aligned with consent requirements?
Open the printable preparation checklist or template (new tab) →

Frequently asked questions

How do I track which blog posts generate leads?

Capture the landing page and source on the first visit, pass them with the form submission into your CRM and report qualified leads and deals by landing page.

Can GA4 track CRM deal outcomes?

You can send offline conversion events to GA4 or ad platforms, but the CRM is usually the better place to analyse lead quality and revenue.

Do I need consent to store UTM data?

Requirements depend on jurisdiction and implementation. Cookies and tracking often need consent in regions such as the EU. Seek legal advice for your situation.

Sources and implementation references

Prepared with AI assistance as an engineering decision guide. Examples are illustrative unless explicitly labelled as an internal implementation. No independent expert review or customer outcome is claimed.

Want more qualified enquiries from search and AI answers?

Share your website, main services and target markets. We review technical, content and conversion gaps before proposing scope. Scope, access, dependencies and commercial terms are agreed before delivery. Do not submit passwords, API keys or confidential records.