How Is This Page Doing?

Nothing. Telescope is free, under the Craft license. There is no paid edition, no trial and no upsell.

No. Telescope talks to the Google Analytics Data API directly. It has zero runtime dependencies — the signed JWT assertion, the API client and the timeline chart are all implemented in the plugin, and nothing is loaded from a CDN. That also means it works under a strict Content Security Policy.

Craft CMS 5.0 or later and PHP 8.2 or later, with the json and openssl extensions — both are standard on virtually every PHP install. You also need a GA4 property and permission to add a user to it.

With a Google service account by default: you create a JSON key in the Google Cloud console, add the service account’s email address to your GA4 property as a Viewer, and paste the key (or a path to it) into the plugin settings. There is no browser consent flow and no refresh token to expire. If you already have an OAuth client and refresh token for the Analytics API, you can use those instead.

No — that is largely the point. The service account is the only Google identity involved. Editors just need the View analytics reports permission in Craft.

Yes, and you should. Both the credentials and the property ID fields parse environment variables, so you can store the key in .env and enter $GOOGLE_ANALYTICS_CREDENTIALS in the setting. Project config then only ever contains the variable name.

Only if you want the full report inline. Turn on Show on all entries and Telescope adds a compact summary to every entry’s sidebar without touching a single field layout — optionally limited to chosen sections. The Analytics field itself stores nothing either, so adding or removing it never touches your content tables.

Overview cards (page views, visitors, sessions, average session duration, engagement rate and bounce rate), a timeline chart, and breakdowns by location, traffic source, referring page and landing page. Each of those sections can be switched off individually.

Each site can point at its own GA4 property via per-site property IDs, or they can all share one. If they share one, turn on Filter by hostname — otherwise /about on every site is the same page path in GA4 and the numbers get added together.

A full report costs six Data API calls, one per section. Reports are cached for ten minutes by default and served from cache thereafter; failed calls are never cached, so fixing a credential problem takes effect straight away. On a busy site, run telescope/analytics/warm from cron and switch off the sections you do not need.

Almost always because the page path Telescope is matching is not the path GA4 recorded. Run php craft telescope/analytics/show <id> to see the exact path being queried, compare it with GA4 under Reports → Engagement → Pages and screens, then adjust Path match type or Include query strings.

Yes. craft.telescope.report(entry), craft.telescope.reportForUrl(url) and craft.telescope.topPages() are available in front-end Twig, along with the same formatting and SVG chart helpers the control panel uses.