Google Analytics
Add Google Analytics to your Basker site to track pageviews and audience behaviour
The Google Analytics app injects the GA4 tag onto every page of your live site, so pageviews and visitor behaviour flow into your Google Analytics account. Reporting and dashboards happen in Google Analytics; the app's job is to make sure the tag is on the page and respecting consent.
Connection
Installation is typically handled by Basker support. Have your GA4 Measurement ID ready (e.g. G-XXXXXXXXXX) — it's the only thing Basker needs to install the tag on your live site.
What it captures
With the tag installed, your site sends standard GA4 events to Google Analytics — pageviews, session detail, referrer, and the user properties GA4 collects by default.
What the app doesn't do:
- It doesn't ingest data into Basker. Reporting lives in Google Analytics.
- It doesn't apply custom event tracking beyond the defaults — anything custom (event-specific tracking, conversion goals, custom dimensions) is configured on the Google Analytics side.
For the analytics side of things — setting up reports, configuring goals, understanding the data — see Google's own documentation.
Stable reporting hooks for blocks
When you want to track a specific block in GA4 or Google Tag Manager — say, to measure clicks on a featured-events section — give it a stable name to report against. Each block on a page has optional Analytics Key and Analytics Label settings (under the block's Analytics section):
- Analytics Key — a stable reporting identifier, e.g.
homepage-featured-events. The block exposes this on the page as adata-analytics-keyattribute, which you target with GTM triggers and variables or with GA4 event configuration. - Analytics Label — an optional human-readable name, e.g.
Homepage featured events, exposed asdata-analytics-labelfor use in reports and tag setup.
Both are optional. Set them on the blocks you care about reporting on, and pick a key you can keep constant — that's the point. A block also carries an automatically generated technical ID, but that ID can change over time, so don't use it as a reporting hook. The Analytics Key stays whatever you set it to, even if the block is moved or rebuilt, so your GA4/GTM reports keep lining up.
You can configure these on any block in the page editor. They work the same whether your site runs a built-in or a custom theme.
Consent and the cookie banner
Google Analytics drops cookies, so the GA tag should respect your visitors' consent choices. Basker's cookie banner integrates with the GA app: when a visitor declines analytics cookies, the GA tag holds back its data collection until they consent. Configure the banner under Security.
If you operate in a jurisdiction with stricter consent requirements (UK GDPR, EU GDPR, CCPA), make sure the banner's defaults match what your legal team needs.