I used Google Analytics for years. Universal Analytics, then GA4 when Google forced the migration. Like most marketers, I accepted it as the default — free, ubiquitous, “good enough.”

Then I actually tried to answer a simple question: which pages on my site lead to someone booking a call?

GA4 made that surprisingly difficult. So I started looking elsewhere. I landed on Amplitude, set it up through the same Google Tag Manager (GTM) container I was already running, and within a week I had answers that GA4 had never given me.

This isn’t a vendor comparison or a feature matrix. This is what actually happened when I made the switch for my own business — what improved, what I lost, and how I’d help you decide whether it’s worth doing for yours.

The Problem with GA4 (for My Use Case)

Let me be clear: GA4 isn’t bad software. It’s powerful, it’s free, and for large e-commerce operations with dedicated analytics teams, it does the job. But for a freelance consultant running a content site, product funnels, and client work across multiple subdomains, GA4 had specific problems I couldn’t work around.

The interface fights you. GA4 replaced the relatively intuitive Universal Analytics reports with a system where you’re expected to build your own reports from scratch in the Explorations hub. For someone who just wants to know which blog posts drive conversions, that’s a lot of overhead. I’m not alone in this — Search Engine Land documented ten common frustrations that echo exactly what I was experiencing.

Data arrives late. At the time of writing, GA4 processes data with a delay of 12 to 48 hours. When I publish a new landing page or run a short campaign, I need to see what’s happening now — not tomorrow. Real-time in GA4 exists, but it’s limited to a surface-level snapshot.

Cross-domain tracking is clunky. I run three subdomains (main site, blog, offers pages) through a single GTM container. GA4 can handle cross-domain tracking, but configuring it properly and then actually building useful reports across those domains was a recurring time sink.

Funnels are an afterthought. I sell digital products through a multi-step funnel: landing page, sales page, order page, confirmation. In GA4, building a funnel visualisation that reliably tracks users through those steps — especially across subdomains — required custom exploration reports that broke whenever I changed a URL. It shouldn’t be that hard.

The event model is powerful but under-documented. GA4 moved to event-based tracking, which is genuinely better than the old pageview model. But the implementation guidance assumes you have a developer. For solo operators and small teams, the gap between “GA4 can do this” and “here’s how you actually set it up” is wide.

Why Amplitude? What Made Me Look Beyond GA4

I’d been aware of Amplitude for a while — it’s widely used in product analytics for SaaS companies. What I hadn’t realised was how well it fits a marketing use case when your questions are behavioural rather than purely acquisition-based.

The core difference is philosophical. GA4 is built to answer “where did my traffic come from?” Amplitude is built to answer “what did people do after they arrived?” Both questions matter, but for a business selling digital products through a funnel, the second question is where the money is.

Five things sold me:

Event-first architecture that actually works. Amplitude treats every interaction as an event with properties. So blog_post_read isn’t just a pageview — it carries the post title, category, scroll depth, and referring source. I can break that data down by category, source, or scroll depth in a single chart — something GA4 makes painful.

Real-time data, genuinely. Events appear in Amplitude within seconds. When I launch a page, I can watch behaviour as it happens. No 24-hour wait.

Funnel analysis in two minutes. Building a funnel in Amplitude takes about two minutes. Select the events in order, set a conversion window, and you immediately see where people drop off. I can break that down by traffic source, device, or any custom property. This was the single biggest improvement over GA4.

Cohort analysis out of the box. I can group users by behaviour (e.g., “people who read 3+ blog posts before visiting a sales page”) and track how those cohorts convert over time. This is technically possible in GA4 with audiences and BigQuery exports, but Amplitude makes it a first-class feature.

A generous free plan. At the time of writing, Amplitude’s Starter plan gives you up to 50,000 monthly tracked users for free (check current pricing here). For a site at my traffic level, that’s more than enough. I’m not paying anything I wasn’t already paying for GA4 (which is also free), and I’m getting significantly more useful data.

How I Set It Up (GTM + Amplitude — No Developer Required)

This was the part I expected to be painful. It wasn’t. If you’re already running Google Tag Manager, adding Amplitude is straightforward.

Step 1: Create an Amplitude project. Sign up, create a project, grab your API key. Five minutes.

Step 2: Install the Amplitude Browser SDK via GTM. I added a custom HTML tag in GTM that loads the Amplitude SDK and initialises it with my API key. This fires on all pages across all three of my subdomains — same GTM container, no duplication.

Step 3: Define your event taxonomy. This is the important bit. Before you start tracking everything, decide what matters. I defined five Tier 1 events:

• blog_post_read — fires at 60% scroll depth on blog posts
• cta_clicked — fires when someone clicks a CTA button or link
• sales_page_viewed — fires on product sales page loads
• order_page_reached — fires when someone hits the checkout/order page
• opt_in_completed — fires on form submissions

Each event carries properties (page URL, post category, product name, traffic source) that make the data actually useful.

Step 4: Set up identity stitching. This is optional but powerful. I configured a GTM tag that calls amplitude.setUserId(email) when someone submits a form. This links their anonymous browsing session to their known identity, so I can see the full journey from first blog visit to form submission. On the server side, I connected my CRM to Amplitude via n8n (a workflow automation tool) to enrich that profile further.

Step 5: Add bot filters. I added exception triggers in GTM to exclude known bots — GTM preview traffic, headless browsers, and SEO crawlers. This keeps the data clean from day one.

The whole setup took an afternoon. No code deployed to my site outside of GTM. No developer needed.

What I Gained After the Switch

After running Amplitude alongside GA4 for a few weeks, then making Amplitude my primary analytics tool, here’s what concretely improved:

I know exactly what’s being tracked — and I trust it. This is the biggest shift. With GA4, I was never fully confident in what was being captured or how. With Amplitude, I defined five specific events, each with named properties, and I can verify in real time that they’re firing correctly. When I see blog_post_read with post_category: HubSpot and read_depth: 60%, I know precisely what that means. There’s no ambiguity, no inferred data, no modelled metrics filling gaps. The event taxonomy I built — blog_post_read, cta_clicked, sales_page_viewed, order_page_reached, opt_in_completed — covers the full user journey from content engagement through to conversion. Every event carries properties like page URL, post category, product name, and traffic source. I can see the entire pipeline, and I trust every number in it.

I can answer business questions in minutes, not hours. “Which blog category drives the most sales page views?” Used to require a custom GA4 exploration with multiple segments. In Amplitude, it’s a single chart with a breakdown by post_category. Done.

Funnel visibility transformed my optimisation work. I can now see exactly where people drop out of my product funnel, broken down by traffic source. That level of granularity — seeing which sources stall at the sales page versus the order page — changed where I focused my copy improvements. In GA4, getting that view required custom exploration reports that broke whenever I changed a URL.

Identity stitching connected the dots. Before Amplitude, I had anonymous sessions and I had HubSpot CRM contacts, but no reliable bridge between them. Now, when someone submits a form, their entire prior browsing history stitches to their profile. I can see that a lead read four blog posts over two weeks before booking a call. That changes how I think about content ROI.

Clean data from day one. Because I built bot filters into the GTM setup from the start — excluding GTM preview traffic, headless browsers, and SEO crawlers — my Amplitude data has been clean since the first event. No retrospective cleanup, no “well, if you exclude the bots…” caveats. The numbers I see are real.

The dashboards are actually usable. I built a single Amplitude dashboard that shows me: weekly active users by domain, top content by engagement, funnel conversion rates, and form submissions by source. It took 20 minutes to build and I check it daily. My equivalent GA4 setup was three separate exploration reports that I rarely opened because the interface was friction-heavy.

What I Lost (and What I Still Use GA4 For)

This isn’t a one-tool-fixes-everything story. There are genuine trade-offs.

Google Search Console integration. GA4 connects natively to Search Console, giving you organic keyword data alongside your analytics. Amplitude doesn’t have this integration. I still check Search Console directly (and through Search Atlas, my SEO tool), but losing the unified view is a downside.

Acquisition reporting. GA4’s traffic acquisition reports — source, medium, campaign — are genuinely good. Amplitude can track traffic source as an event property, but it doesn’t have GA4’s depth of channel grouping and attribution modelling out of the box. For paid campaign analysis specifically, GA4 (and its Google Ads integration) is still stronger.

Familiarity and ecosystem. Every marketer knows GA4. Every tutorial references it. Every client expects it. I still keep GA4 running passively on my sites — the GTM container fires both Amplitude and GA4 tags. GA4 serves as a backup and a common reference point when I’m discussing analytics with clients who use it.

Historical data. My GA4 property has years of historical data. Amplitude starts fresh from the day you install it. You can’t migrate historical GA4 data into Amplitude in any practical way. This is a real consideration — if year-over-year comparisons matter to your reporting, you’ll want to run both tools in parallel for at least 12 months.

Should You Switch? A Decision Framework

Rather than a blanket recommendation, here’s how I’d think about it based on what your business actually needs:

Amplitude is likely a better fit if you:

• Sell digital products or run a SaaS and your key questions are behavioural — what do users do, where do they drop off, what content converts
• Need real-time data without a 24-hour wait
• Want funnel and cohort analysis without building custom GA4 explorations
• Already run GTM and are comfortable adding tags
• Get under 50,000 monthly users (Amplitude’s free tier covers you)

Stick with GA4 (or run both) if you:

• Rely heavily on Google Ads and need native campaign integration
• Need organic keyword data in the same tool as your behaviour data
• Work with clients or stakeholders who expect GA4 reports
• Depend on year-over-year historical comparisons
• Are primarily focused on acquisition channels rather than on-site behaviour

The pragmatic middle ground — which is what I actually do — is to run both. GA4 stays installed passively via GTM for acquisition data, Search Console integration, and client-facing reports. Amplitude is my primary analytics tool for everything behavioural: funnels, content performance, user journeys, and conversion analysis.

The cost of running both is zero (both have free tiers) and the GTM overhead is minimal — two sets of tags in the same container.

Final Thoughts

The move from GA4 to Amplitude wasn’t driven by hype or a dislike of Google. It was driven by a specific frustration: I couldn’t easily answer the questions that mattered most to my business. Amplitude solved that.

If you’re a B2B marketer, freelance consultant, or small SaaS operator and you’ve ever stared at a GA4 exploration report thinking “there has to be a better way to see this” — there probably is. Amplitude is worth an afternoon of your time to set up and evaluate.

If you found this useful, I write regularly about marketing tools, CRM implementation, and the infrastructure behind B2B growth systems. You can find more on the blog or get in touch if you’ve got questions about setting up your own analytics stack.