Multi-site

There are two sensible arrangements, and one mistake that quietly produces wrong numbers.

One property per site

If each Craft site has its own GA4 property, enter each property ID under Per-site property IDs, keyed by site handle. Anything not listed falls back to the default GA4 property ID.

Nothing else is needed. Each site’s reports come from its own property, so paths cannot collide.

One property shared by several sites

If all your sites report into a single property, leave the per-site overrides empty and turn on Filter by hostname.

This matters more than it sounds. GA4 records a page path, not a full URL — so /about on example.com and /about on example.fr are the same path in a shared property. Without hostname filtering, the two sites’ numbers are added together and every report is inflated.

With it on, Telescope adds a hostName filter derived from each site’s base URL, and each site sees only its own traffic.

Which site a report uses

Reports follow the element: an entry’s report uses that entry’s site, and its URL in that site. The Telescope Overview page and the console commands take an explicit site instead — a Site filter in the control panel, and --site=<handle> on the command line.

Checking it

Run the connection check for a specific site to confirm it resolves the property you expect:

php craft telescope/analytics/check --site=fr

and print a single entry’s report to see the exact path being queried:

php craft telescope/analytics/show /a-propos --site=fr