How to Integrate Google Analytics with Your Headless CMS

What is Google Analytics?

Google Analytics is Google's web and app analytics platform for tracking traffic, user behavior, acquisition channels, conversions, and audience segments. Marketing, product, growth, and editorial teams use Google Analytics 4 to understand which pages bring in visitors, which paths convert, and where users drop off. It's one of the most widely used analytics tools because it connects site behavior to Google Ads, Search Console, BigQuery exports, and reporting workflows.

Why integrate Google Analytics with a headless CMS?

When your analytics setup only knows a URL, your reports stop at page-level traffic. You can see that /blog/ai-buyers-guide got 18,000 views, but you can't easily group performance by content type, author, industry, funnel stage, product line, or campaign unless someone maintains that mapping by hand. That gets messy fast when you're publishing across a website, docs, landing pages, and localized pages.

Architecture overview

A typical Sanity and Google Analytics integration has two flows. First, content flows from the Content Lake to your site or app through GROQ queries. The frontend renders the page and sends user behavior to GA4 with the Google tag, Google Tag Manager, or a framework package such as @next/third-parties. The page_view or custom events include content metadata, such as content_type, author, topic, locale, and funnel_stage, pulled from the same structured content used to render the page.

Common use cases

Step-by-step integration

1. 1

   Set up Google Analytics 4

   Create or choose a GA4 property, add a Web data stream, and copy the Measurement ID, such as G-ABCD1234. If you'll send server-side events, open Admin, Data streams, choose your stream, then create a Measurement Protocol API secret. For frontend tracking, install the Google tag directly, through Google Tag Manager, or with a framework package.

2. 2

   Define the tracking plan

   Decide which content fields belong in GA4. Common fields include content_type, author, primary_topic, locale, funnel_stage, campaign_id, and publish_date. Keep names short and stable because GA4 event parameter names have rules, and custom dimensions take time to appear in reports.

3. 3

   Model the fields in Sanity Studio

   Add schema fields that match the tracking plan. For example, an article document might include title, slug, author reference, topics array, locale, funnelStage, campaignId, and publishedAt. Because the schema is code, developers can review changes before they affect tracking.

4. 4

   Create the sync mechanism

   Configure a Sanity webhook to trigger on publish events for the document types you want to track. Point it at a Sanity Function, Next.js API route, serverless function, or other HTTPS endpoint. Use a webhook secret so the endpoint can reject requests that didn't come from Sanity.

5. 5

   Call Google Analytics

   In the handler, use @sanity/client and GROQ to fetch the published document with joined references, such as author name and primary topic. Then send a GA4 Measurement Protocol request with an event name like content_published and parameters that match your tracking plan.

6. 6

   Test the frontend and reports

   Use GA4 DebugView for client-side events and the Measurement Protocol validation endpoint for server-side payloads. Publish a test document, confirm the webhook fires, check the network request, and verify that custom dimensions populate in Google Analytics after processing.

How Sanity + Google Analytics works

CMS approaches to Google Analytics

Keep building

Explore related integrations to complete your content stack.