A factual, no-fluff guide to installing GA4 correctly in Framer, avoiding the mistake that silently breaks tracking, and understanding what GA4 can and can't yet tell you about AI referral traffic.
Ayesha Ikram
GA4, Framer, GEO Tracking
EXECUTIVE SUMMARY
GA4 replaced page-count tracking with an event-based model that captures clicks, downloads, video plays and scroll depth. Framer makes installation genuinely simple: one Measurement ID, pasted into one field, published once. The mistake that quietly breaks this setup for most sites is pasting a Google Tag Manager container ID into a field that only accepts a native GA4 Measurement ID, which fails silently and leaves you reporting on empty data for weeks. On the GEO side, GA4 added a native AI Assistant channel on 13 May 2026 that automatically separates ChatGPT, Gemini, Copilot and Grok traffic from ordinary Referral, but Perplexity and Claude are still not on that list and need a custom channel group to surface. Correct setup isn't optional infrastructure. It's the only way to know if any of your GEO or SEO work is actually working.
Why Most Coaching Sites Are Flying Blind
A site can look fully tracked and still be collecting nothing useful. The most common cause isn't a missing script, it's the wrong ID in the right field.
Framer has a native "Google Analytics Measurement ID" field under Site Settings, and it only accepts a GA4 Measurement ID in the format G-XXXXXXXXXX. If a Google Tag Manager container ID (GTM-XXXXXXX) gets pasted in instead, nothing errors, nothing warns you, and the dashboard simply stays empty. Plenty of site owners don't discover this for months.
What GA4 Actually Tracks
GA4 runs on an event-based model rather than counting page loads. It captures individual interactions: button clicks, file downloads, video plays, scroll depth, and any conversion action you define.
That matters for three practical reasons. You can see exactly where your best traffic is coming from (direct, organic search, social, referral). You can watch where people actually drop off inside a funnel, rather than guessing. And you can make layout or content decisions based on what visitors do, not on assumption.
The Setup: Three Steps
Get your Measurement ID. In Google Analytics, go to Admin → Data Streams → Web Stream, and copy the ID in the format G-XXXXXXXXXX.
Paste it into Framer. Open Site Settings → General, find the field labelled "Google Analytics Measurement ID," and paste it in. There's no custom code required.
Publish. Click Publish in the top right to push the connection live.
That's the whole native integration. Anything beyond a single GA4 property (multiple pixels, conditional firing, third-party tools like Meta Pixel) needs Google Tag Manager instead, added through Framer's Custom Code section, which is a separate setup.
Setup Mistakes Worth Checking Now
Container ID in the GA4 field. Covered above. If your dashboard has been unusually quiet, this is the first thing to check.
HTTP instead of HTTPS on the data stream. When you create the Web Data Stream, make sure the URL is set to https://. Getting this wrong won't always break tracking outright, but it can cause mismatches between what Framer serves and what the stream expects.
Panicking over single-session hits from unexpected countries. A one-off session from an unfamiliar location is usually a bot or automated scanner, not a real visitor. It's normal and not something to chase down.
GEO Tracking: What GA4 Can and Can't See Yet
This is the part that's changed recently, and where most existing guides (including AI-generated ones) are already out of date.
As of 13 May 2026, GA4 added a native "AI Assistant" channel to its default channel grouping. It automatically recognises and separates traffic from ChatGPT, Gemini, Copilot, Grok and DeepSeek, no setup required.
It's also incomplete. Perplexity and Claude are not on Google's recognised list and still land under generic Referral, mixed in with everything else. A meaningful share of AI-referred visits also arrive with no referrer at all and get logged as Direct, regardless of which platform sent them.
For full visibility, the AI Assistant channel isn't enough on its own:
Workflow 1: Confirm the native channel is populating. Reports → Acquisition → Traffic acquisition → Session default channel group, and check for an "AI Assistants" row.
Workflow 2: Build a custom channel group for what's missing. Admin → Data display → Channel groups, matched on Source (not Medium) against a pattern covering perplexity\.ai and claude\.ai, positioned above the Referral rule so those sessions get intercepted first rather than falling through to generic Referral.
Workflow 3: Accept the Direct-traffic gap. Some AI-referred sessions will never carry a referrer, particularly from native apps. There's no full fix for this yet, only a known blind spot worth factoring in when a site's Direct traffic spikes without explanation.
GA4 doesn't influence rankings in either traditional SEO or GEO. What it does is show, honestly, whether the work behind either strategy is reaching anyone: organic landing page performance for SEO, and now, partially, which AI platforms are actually sending you visitors for GEO. If you are actively building out a broader Generative Engine Optimization strategy to capture AI search citations, these custom analytics channels are how you prove the investment is paying off.
Where This Leaves You
None of this requires a developer or an agency retainer to set up correctly. It requires getting the right ID in the right field, and knowing which AI platforms your analytics can and can't see yet.
Get the base tracking right first. The channel groups and deeper GEO measurement only mean anything once the foundation underneath them is actually collecting real data.
If you'd rather have your entire site's technical infrastructure, AI citations, and lead capture systems evaluated end-to-end, explore our custom Qasimo Systems Architecture or book an AI Automation Audit.
