Limits

Every limit here reports itself rather than failing silently. These are the numbers to plan around.


#Every limit

Limit

Value

What happens

Measurement ID format

Must start with G- (GA4)

Universal Analytics IDs are accepted by the settings field but collect nothing anywhere.

Custom dimensions created

14 (5 required, 9 optional)

Against GA4's standard limit of 50 event-scoped custom dimensions. The app budgets 45 so you keep room for your own.

Report table page size

200 rows maximum, 50 by default

Applies to the Content, Spaces, Searches and Raw tables.

Report filter sizes

50 space keys, 50 account ids, 10 surfac

Per report query.

Overview chart buckets

500 time buckets maximum

Per overview time series.

Macro date range

1 to 365 days (picker offers 7, 30, 90)

Default 30 days.

Reports page date range

7 / 30 / 90 day presets plus a custom ra

Default 30 days.

Historical lookback

400 days

The health check that drives the reports notice bar looks back 400 days, matching GA4's default retention ceiling.

Settings propagation delay

Up to about 10 minutes

Four caches sit between saving a setting and a reader's browser acting on it: a 60-second server cache, the published projection, a 10-minute CDN cache and a 10-minute cache in each reader's browser.

GA4 data latency

Up to 48 hours

New events and newly created custom dimensions take up to 48 hours to appear in Google Analytics. This is Google's behaviour, not the app's.

Space-level settings

None exist

There is exactly one settings page for the whole site. The space page is a report view only.

Google connection scope

One per Confluence site

The Google connection is site-level, not per-user. One admin connects and everyone uses it.


#A few things worth knowing

  • A limit that is reached is reported in the interface, not in a log you have to find.

  • Limits are per site or per tenant depending on the limit. The table says which.

  • Edition can change some of these.



They announce themselves. Read the message.