Comments on: How to Avoid (other) in Your GA4 Reports (Cardinality)

By: Paul Koks

Paul Koks — Wed, 12 Apr 2023 14:24:02 +0000

In reply to Béate Vervaecke. Table 2 is the underlying table that populates the report. You don't see this table in GA4. Hope this helps.

By: Béate Vervaecke

Béate Vervaecke — Wed, 12 Apr 2023 11:34:16 +0000

Thank you for this article !
Short question about the 3 data tables: what’s the difference between 1 and 2? They both serve the GA4 UI and API, but the second one is aggregated? When do I see data table 1 in the UI, and when do I see data table 2?

By: Paul Koks

Paul Koks — Wed, 12 Apr 2023 09:09:22 +0000

In reply to Bernhard Lukas. Thanks for your comment Bernhard, great points!

By: Bernhard Lukas

Bernhard Lukas — Wed, 05 Apr 2023 21:10:15 +0000

Limits of page_location and page_referrer (not to be forgotten!) can easily be mitigated with Ayudante’s “TrimQuery” GTM variable template although you must not exclude “srsltid” when enabling automatic tagging for organic Google Shopping results AKA “free listings” (but only when connecting Merchant Center accounts with GA4 and only if you want to detect Organic Shopping in its own channel). Still wondering why Google cannot exclude this (very long) parameter while they obviously can do this with gclid.

Problems with cardinality often arise with ecommerce standard reports, if you have many different products (not talking about variations). E.g. a report on a one-day-basis with less than 20.000 rows result in >95% of the revenue being attributed to “other”. Your only chance then is BigQuery or Explorations (and then having to report multiples of 500 by changing the starting row constantly).