Website Analytics Tools in 2025: Myths, Facts & a Stack That Ties Back to Revenue
A practitioner's guide to choosing analytics tools for US stores - GA4 retention limits, cookieless and CCPA realities, server-side tracking, and warehouse reconciliation.

Image via 123RF
In This Article
Myth-Busting the Default Stack
Tool Categories That Actually Matter
Reconcile to One Revenue Source
Why Most US Stores Misread Their Website Analytics Stack
Most US eCommerce teams do not lack analytics tools - they lack a stack that answers one question: which dollar of spend produced which dollar of revenue? The default setup (GA4 on a Shopify theme, ad platforms reporting their own conversions) produces three different revenue numbers on any given Monday. Four persistent myths keep brands buying dashboards instead of clarity.
Myth #1: GA4 Already Gives You Every Number You Need
The facts on GA4: retention, sampling, and the Universal Analytics break
GA4 is a strong event-based foundation, but its free tier caps data retention and explorations can sample large datasets. Check the current limits in Google's data retention documentation before building year-over-year models on raw event data. Universal Analytics stopped processing standard properties in July 2023, so any UA-to-GA4 comparison is not apples-to-apples - different session logic, attribution, and conversion counting.
If your reporting compares 2022 UA figures against 2024 GA4 figures, your “growth” or “decline” may be a measurement artifact, not a business trend.
Myth #2: Cookieless Analytics Is Automatically US-Compliant
What CCPA/CPRA and the new state laws actually require from your analytics
Cookieless tools like Plausible and Fathom reduce consent friction and are useful for aggregate traffic insight, but “no cookies” does not equal “no personal data.” Under the CCPA/CPRA and the Virginia, Colorado, Connecticut, and Utah laws, you still need a working opt-out path for sale/sharing, a stated retention policy, and no PII (emails, names, order IDs mapped to people) in analytics events. A cookie banner is not an opt-out mechanism.
Common US pitfalls we audit for: PII in event parameters, no consent-mode signals to Google, and cross-platform conversions double-counted between Shopify and ad platforms.
Myth #3: More Tools Means Better Data
The four website analytics tool categories that cover a real funnel
Four categories map to a funnel: web analytics (aggregate behaviour), product analytics (on-site event depth), tag management and server-side collection (reliability), and warehouse/BI (reconciliation). Buy one strong tool per category rather than three overlapping ones.
| Category | Example tools | Best fit | Rough monthly cost (USD, estimate) |
|---|---|---|---|
| Web analytics | GA4, Matomo, Plausible | Baseline traffic and channel view | GA4 free; Plausible/Fathom ~10-100; Matomo cloud from low tens |
| Product analytics | Amplitude, Mixpanel, PostHog | Funnel and feature-level behaviour | ~50-500+ by event volume (estimate) |
| Tag / server-side | GTM server-side, Meta CAPI | Data reliability post-cookie deprecation | Tag manager free; hosting ~20-100 |
| Warehouse / BI | BigQuery, Segment, Looker Studio | Reconciling CAC, MER, LTV | Usage-based; Adobe Analytics custom often six figures |
Where client-side-only tracking quietly loses your revenue
Ad blockers, ITP on Safari, and iOS privacy changes erode client-side event capture. When a purchase event never fires, GA4 and Meta both under-report, and your real CAC looks better than it is - a silent profitability leak that Prebo Digital's analytics and tracking services are built to close with server-side collection.
Myth #4: Platform-Reported ROAS Is the Truth
Every platform claims credit for the same sale. Meta, Google, and TikTok each report their own conversions, and Shopify's native reports report the order. None are wrong; they measure differently. The fix is a single revenue source of truth - usually the warehouse - plus a MER (marketing efficiency ratio) view comparing total spend to total revenue.
Reconciling GA4, Shopify, and ad platforms to a single revenue source
Practically: export GA4 events via BigQuery, join to Shopify order data on a de-duplicated order ID, and compare channel-reported conversions against warehouse revenue weekly. If Google Ads reports 40 orders and the warehouse shows 34, you have a tracking gap, not a dispute.
What server-side tracking changes for attribution and CAC
Server-side GTM (see Google's server-side tagging documentation) moves tag firing to a controlled container, reducing client-side script load and improving event reliability as third-party cookies deprecate. Paired with Meta Conversions API, purchase events persist even when the browser blocks them - which is how CAC and LTV stop drifting.
A minimal consent-mode example for US sites using Google tags:
gtag('consent', 'default', {
ad_storage: 'denied',
analytics_storage: 'denied',
region: ['US-CA', 'US-VA', 'US-CO', 'US-CT', 'US-UT']
});
// update on opt-in from your consent banner
gtag('consent', 'update', { analytics_storage: 'granted' });
A practical consent-mode and opt-out checklist for US sites
- Consent defaults set before tags fire; updates only on explicit opt-in.
- Working “Do Not Sell or Share My Personal Information” link where state law requires it.
- No PII in event parameters - hash emails or omit them entirely.
- Documented retention policy matching your GA4 setting.
- Quarterly reconciliation of platform conversions against warehouse orders.
Which website analytics stack suits your stage?
Starter: pre-revenue to ~USD 1M annual revenue
GA4 plus a simple consent banner and a Plausible or Fathom backup for ad-blocker-resistant traffic. Skip Amplitude and BigQuery until volume justifies them; get event naming and purchase tracking clean now, because retrofit is expensive.
Scaling Shopify/WooCommerce: USD 1M-USD 20M with paid media
GA4 plus server-side GTM, Meta CAPI, and a lightweight BigQuery export via Segment or RudderStack. Add PostHog or Amplitude only if you genuinely analyse funnel depth. This tier is where MER and CAC dashboards pay for themselves.
Enterprise and multi-brand: warehouse plus BI and a data owner
Centralised warehouse, ETL, Looker or a BI layer, and a named analyst. Adobe Analytics and Matomo self-hosted appear here for regulatory or custom needs. Without a data owner, this tier rots within two quarters.
How to audit your current analytics stack in one afternoon
Pull GA4 revenue, Shopify orders, and Meta/Google reported conversions for the same seven-day window and note the percentage gap on each. Then check one purchase event in GTM preview and confirm it fires server-side. If those steps surface discrepancies above a few percent, see how this applies to your store with a focused review from Prebo Digital's tracking team.

