Google Analytics 4

Good fit if…

• ✓Marketing teams running Google Ads or relying on Google marketing ecosystem
• ✓Sites and apps that need event-based measurement at high volume without per-hit SaaS fees
• ✓Organizations comfortable with BigQuery export for custom analysis
• ✓Teams that already have GA4 expertise and reporting workflows

Consider other analytics tools if…

• −Small sites that only need simple traffic stats and want minimal compliance overhead
• −Teams avoiding Google data processing or US cloud jurisdiction concerns
• −Privacy-first positioning without cookie banners — lightweight tools win here
• −Revenue attribution for indie Stripe SaaS without significant GA4 ecommerce setup — DataFast is simpler

GA4 uses an event-based data model — every interaction is an event with parameters. Pageviews, scrolls, purchases, and custom actions all flow through the same pipeline. This replaces Universal Analytics' session/pageview-centric model and requires relearning reports and explorations.

Strength: flexible schema for web + app in one property. Weakness: easy to over-instrument and inflate event counts, making reports noisy without governance.

For marketing sites, start with enhanced measurement defaults and add custom events only where decisions depend on them.

GA4's biggest advantage is integration depth: Google Ads linking, Search Console, Looker Studio, and optional BigQuery export (standard properties get limited free export; 360 unlocks more). If your growth stack is Google-centric, GA4 is the hub.

Non-Google integrations exist via GTM and APIs but are rarely as seamless as native Google links. Teams on Meta Ads or other channels often still run GA4 alongside platform pixels.

Consent Mode v2 and regional settings matter for EU traffic — misconfiguration can skew attribution and create compliance risk.

GA4 is not a privacy-first tool in the Plausible sense. It uses cookies and identifiers, processes data on Google infrastructure, and typically requires consent banners in GDPR jurisdictions.

Google offers data retention controls, IP anonymization options (context-dependent), and user deletion tools — but operational burden falls on you. Several EU regulators have scrutinized Google Analytics transfers; some organizations choose Matomo or EU-hosted alternatives for that reason.

Free does not mean zero compliance cost — legal review and consent UX are part of the total price.

GA4 standard is free for most sites within Google's collection limits. Google Analytics 360 is enterprise-priced (six figures annually) for very large organizations needing SLAs, higher limits, and advanced BigQuery.

Hidden costs: GTM/consulting time, BigQuery storage/query bills, and compliance tooling. At low traffic, GA4 wins on price vs any paid privacy tool; at high traffic, "free" still holds for standard tier but ops complexity grows.

Use our pricing calculator to compare GA4 ($0) against paid alternatives at your pageview level.

Typical setup:

1. Create a GA4 property and web data stream.
2. Install gtag.js or deploy via Google Tag Manager.
3. Configure key events (conversions) and link Google Ads if applicable.
4. Set data retention, internal traffic filters, and consent defaults.
5. Validate with DebugView before trusting reports.

Expect 2–8 hours for a basic marketing site; days to weeks for mature ecommerce or multi-app setups with GTM governance.

Common pitfalls: duplicate tags inflating counts, missing consent mode in EU, treating GA4 like UA reports, and unbounded custom events without naming conventions.

• −Steep learning curve vs Plausible/Fathom — reports are powerful but not simple.
• −Privacy and EU transfer concerns push some teams to Matomo or EU-hosted tools.
• −No session replay or heatmaps natively — pair with Hotjar or PostHog.
• −Revenue attribution for custom Stripe flows requires deliberate ecommerce/event setup.
• −Script weight and performance vary by implementation — benchmark pending on AnalyticsVS.