Affiliate Analytics

Google Analytics' Limitations for Affiliate Sites (2026)

62%+18%

GA4 is a genuinely capable analytics tool, and this isn't a hit piece. But for affiliate sites specifically, it has a structural blind spot that no amount of configuration closes — and a handful of quieter limitations that hit affiliates harder than anyone. Knowing exactly where GA4 stops is what keeps you from trusting numbers it was never built to produce.

The structural gap: your money is off-site

GA4 sees the click, never the earningGA4 sees the click \u2014 never the earningYour site \u2014 GA4 seesPageviewScroll & engagementOutbound click \u2713off-site boundaryMerchant \u2014 GA4 is blindLands on productAdds to cartBuysCommission earned $The one number that matters \u2014 what a click earns \u2014 lives on the far side of the wall.
GA4 is an on-site analytics tool, but affiliate revenue is earned off-site, on the merchant. GA4 can record that a visitor clicked out, but the add-to-cart, the purchase, and the commission all happen where it can't follow. That's not a bug to configure away \u2014 it's the structural reason GA4 alone can never tell an affiliate what a click, page, or source actually earns.

Here's the root of it. GA4 is an on-site analytics tool — it measures what happens on your pages. But affiliate revenue is earned off-site, on the merchant. GA4 can record that a visitor clicked an outbound link, and then its vision ends at your domain's edge. The add-to-cart, the purchase, the commission — all of it happens on Amazon or the merchant, where GA4 simply cannot follow.

So the single most important number to an affiliate — what a click earns — is invisible to GA4 by design. It can tell you a link was clicked; it can never tell you that click made you $2.40. Without revenue, there's no EPC, no RPV, no per-page earnings — the whole affiliate scorecard is missing its most important column. You can bolt on outbound-click events and manually import earnings to stitch them together by tag, but at that point you're rebuilding an affiliate analytics tool inside GA4.

The affiliate-specific breakage

Beyond the structural gap, GA4 quietly mangles affiliate data in ways most people never notice:

  • Attribution thresholds dump your data into "direct." GA4's default data-driven attribution requires 400 conversions per path (and 20,000 total) before it will model that path. Published analysis estimates roughly 98% of affiliate conversion paths never hit that threshold, so GA4 excludes them and routes their value into "direct" or catch-all buckets. For small sites, GA4 silently falls back to last-click and won't tell you.
  • The 30-event cap. GA4 caps a property at 30 key events; mark a 31st and it silently fails — the event still fires but stops counting. Affiliate programs blow through this fast once they tag link clicks, coupon redemptions, tiered signups, and micro-conversions on top of standard ecommerce events.
  • ~50% underreporting. Stack these up and it's common for GA4 to underreport affiliate revenue by around half — which is why the networks themselves now tell you to treat your affiliate plugin or dashboard as the source of truth, not GA4.

The general limitations that bite affiliates hardest

GA4's well-known weaknesses land especially hard on niche affiliate sites:

  • Thresholding hides your granular rows. To protect privacy, GA4 hides low-volume segments, showing zeros or "thresholding applied." A niche site drilling into specific pages or small segments — exactly where your winners hide — keeps hitting a wall of hidden data. The more specific the question, the less likely GA4 answers it.
  • Sampling distorts comparisons. Standard reports are no longer sampled, but the advanced Explore reports (funnel, path, custom) still sample under load — sometimes analyzing as little as ~30% of your data, enough to show one page beating another by 40% when the full data says otherwise, and send you optimizing the wrong thing.
  • 14-month retention and latency. Event data is retained 14 months max without BigQuery, and complex reports lag (up to ~24–48 hours), with limited real-time — awkward when you want to see whether a fix worked.

What GA4 is genuinely good for

To be fair, because this matters: GA4 is strong at on-site behavior — traffic sources, engagement, which content pulls visitors, and on-site funnels for stores that check out on your own domain. If that's your question, GA4 answers it well and for free. The failure only appears when you ask it about affiliate revenue, which lives somewhere it can't see. It's a job-fit mismatch, not a bad tool — a Ferrari engine on the wrong chassis for this particular race.

The sensible setup

Don't fight GA4 into a shape it can't hold. Use it for on-site behavior, and use a purpose-built affiliate analytics tool for the click-to-earnings side — the same "use the right tool for each job" logic the privacy-first comparison lands on.

That revenue side is exactly what Clickolytics is built for: it ties your outbound clicks to imported earnings, computes per-link and per-page EPC and RPV, doesn't threshold or sample your own data away, and shows it in real time. It fills the column GA4 structurally can't — and it's happy to sit alongside GA4 rather than replace it.

Measure what GA4 can't: Clickolytics ties clicks to real earnings for per-page EPC — the off-site number GA4 was never built to see. See how it works →

The bottom line

GA4's limitations for affiliates aren't a settings problem you can audit away; the central one is structural — affiliate revenue is off-site, and GA4 is on-site, so what a click earns is invisible to it. On top of that, attribution thresholds bury your paths in "direct," the 30-event cap silently drops your tags, and thresholding hides the granular rows you most need. Keep GA4 for on-site behavior, where it earns its keep, and measure the revenue side with a tool built to see off-site — because the one column that decides what to write more of is the one GA4 leaves blank.

Frequently asked questions

Can GA4 track affiliate revenue? Not natively — commissions happen off-site where GA4 can't see. It records the outbound click, never the earning. You'd have to import earnings and stitch them by tag.

Why does GA4 underreport affiliate revenue? Data-driven attribution excludes ~98% of affiliate paths (400-conversion threshold), the 30-event cap silently drops tags, and thresholding hides rows — commonly ~50% underreporting.

What is thresholding? GA4 hides low-volume rows for privacy, showing zeros. For niche sites analyzing specific pages/segments, it hides exactly the data you need.

Should I drop GA4? No — use it for on-site behavior, and pair it with a purpose-built affiliate analytics tool for the click-to-earnings side.

Related reading