Do you install GA4 with a plugin or in code?

Site Kit by default, code when the situation calls for it. Site Kit connects GA4 and Tag Manager quickly and puts a stats panel inside WordPress, which matters because it is the only place most editors will ever look. Its cost is limited flexibility and a dependency on Google. Manual injection through the theme or ACF gives full control, at the price of ongoing validation nobody owns unless you assign it. The alternatives we get asked about: Matomo: complete data ownership, but its own infrastructure to run. Jetpack Stats: simple reporting with no real segmentation. Hotjar and Microsoft Clarity: useful for UX research, but they sit alongside the CMS rather than integrating with it.

How do you stop event tracking from breaking on the next release?

By treating the data layer as application code rather than a Tag Manager setting. The push logic lives in the repository, so it goes through the same review as anything else that ships. Variable names are standardized once and used identically on both sides, which removes the most common silent failure: a rename in the markup that nobody propagates to the container.

What do you typically track, and how much is too much?

The default set is deliberately small: downloads of gated assets, scroll depth, form interactions, and successful submissions. Beyond that we add what a specific decision depends on. Two rules keep it from sprawling: One user interaction produces exactly one GA4 event, so a single click never inflates three counters. Nothing fires on All Pages except the base configuration, so debugging does not turn into archaeology. An event nobody reads still costs a firing condition to maintain and a line in the consent inventory.

How does consent management work, and what does it cost us in data?

Consent is configured with CookieYes or an equivalent and wired so tags are gated by consent state, not merely coexisting with a banner. A banner with tags that fire regardless is worse than none, because it looks compliant. It does cost you data, and we will not quote a recovery number: the honest answer depends on your traffic mix, your jurisdictions and your banner design. What we commit to is that the loss is a known quantity rather than a discovery during a privacy review.

Can this data reach our CRM, or does it stay inside GA4?

It reaches the CRM, and that is usually the point. A form submission that fires a GA4 event and also creates a contact is one interaction described in two systems, which only stays consistent if the event contract and the field mapping are designed together. That handoff is covered on our integrations page.

Do you run this stack on your own site?

Yes, and most of it is checkable from outside. 40q.agency runs Site Kit with GA4 and Search Console connected, a CookieYes consent banner, and Gravity Forms routing submissions into HubSpot. Both Search Console and GA4 export into BigQuery. Search Console is where organic results actually get measured, which is why this sits next to technical SEO rather than in its own silo. Running the stack ourselves is not a client outcome and we will not present it as one.

Home
Capabilities
Analytics & Measurement

Analytics & Measurement

Enterprise WordPress analytics that still works after the next release

Most GA4 setups are an afternoon of work followed by three years of quiet decay. We define the event contract in code, wire it through Tag Manager, gate it behind consent, and document what runs.

What we configure

A measurement layer, not a tracking script

Enterprise measurement fails in predictable ways: data scattered across tools with no single source of truth, tracking that ships without real consent handling, and editors who leave the CMS to answer a question about their own content.

A dataLayer contract in your codebase

Events fire through a custom JavaScript layer with a fixed shape: event name, action, label, and the content section. JavaScript defines the contract; Tag Manager and GA4 consume it.
GA4 and Tag Manager, configured rather than installed

Google Site Kit connects GA4, surfaces a stats panel inside WordPress, and manages Tag Manager. When you need tighter control, we inject scripts through the theme or ACF.
Custom events that map to real decisions

Asset downloads, scroll depth, form interactions and successful submissions. One interaction produces exactly one GA4 event, and nothing fires on All Pages except the base configuration.
Consent handled before the first tag fires

GDPR and CCPA consent configured with CookieYes or an equivalent and wired to the banner, so tags respect the visitor’s choice instead of running beside it. Scripts load asynchronously.
Editorial analytics for publishing teams

On WordPress VIP we add Parse.ly for engagement, scroll depth and popular-article data. Its public API brings dashboards into the admin and powers frontend components like a most-read module.
Naming standards and a documented script inventory

Variable names are standardized once and used identically in the dataLayer and in Tag Manager. Every active script is documented in version control: what it loads, where, and when.
Data that reaches the systems which act on it

Measurement is only worth the effort if something happens next. The same event contract that feeds GA4 feeds your CRM and marketing automation, so a form submission becomes a Salesforce or HubSpot record and a measured event at once. Measure, evaluate, act, then let what you learned change what you measure next.

The pipeline

How one click becomes a number you can trust

Four handoffs sit between a user action and a report. Each is where measurement breaks.

Step 1

The site emits

A dataLayer push with a fixed structure: event name, action, label, content section, page path. The contract lives in your repository, under code review.
Step 2

Tag Manager translates

Each dataLayer key becomes a variable, each event name a trigger, one tag forwards the payload to GA4. Naming must match the code exactly.
Step 3

GA4 registers

Custom definitions are created for every variable arriving from Tag Manager, which makes the data queryable rather than merely received.
Step 4

Your team reports

Explorations built on those dimensions and metrics, validated in Tag Manager Preview and GA4 DebugView before launch.

Measurement governance

The part nobody scopes: who owns the events

Installing GA4 is a task. Keeping it accurate across three years of releases is a governance problem, and it has three parts.

Ownership

Marketing decides what is worth measuring. Engineering decides how it is emitted. Writing the contract down lets those two groups disagree in a document instead of in production.

Durability

A data layer in the theme codebase gets reviewed on every release, like any other code. One that lives only inside a Tag Manager container does not, and quietly stops matching the markup.

Compliance

Consent state gates the tags rather than sitting beside them. Which scripts run, on which pages, under which conditions: documented. A privacy review becomes a reading exercise.

FAQ

What enterprise teams ask us about analytics

Worth reading even if you never hire us.

Related insights

Keep reading on measurement and marketing operations

How enterprise teams measure what works and stay compliant.

A grid showing icons and labels for different content blocks: Paragraph, Heading, Media & Text, Image, Cover, Gallery, Video, Audio, Columns, File, Code, and List, under the heading Be your own builder.

Apr 9, 2024

Marketing autonomy

Request a tracking audit

We will review your data layer, Tag Manager container, GA4 custom definitions and consent configuration, and send you the findings whether or not you work with us.

Request a tracking audit Talk to a measurement engineer

Enterprise WordPress analytics that still works after the next release

A measurement layer, not a tracking script

How one click becomes a number you can trust

The site emits

Tag Manager translates

GA4 registers

Your team reports