Google Analytics

GA4 reporting depends on collected events, predefined or custom dimensions, campaign classification and the chosen consent mode. Use predefined dimensions where available; register custom definitions for additional data that needs them (GA4.md). Consent behavior is defined in CONSENT-MODE.md. So most of the work happens before the data arrives: a tracking plan that starts from the decisions the numbers will drive, names that match what Google collects, UTMs that follow one spelling, and a check in DebugView or Tag Assistant before anyone trusts a report. The material comes from the analytics skill of coreyhaines31/marketingskills (MIT; its partner-UTM table is "adapted from Wispr Flow's link-creator skill (MIT)"), checked against Google's Analytics, Tag Manager, tag platform and Google Ads help pages, with the Google side of c15t's consent docs (Apache-2.0). Where the source disagrees with Google, each file gives Google's form with its URL and says what the source said.

The old intro treated missing custom definitions and denied consent as universal no-data cases. Google recommends predefined dimensions, and advanced consent mode can send measurements without cookies while consent is denied; modeling has eligibility requirements. Google custom definitions, Consent mode overview

Product analytics for the user's apps is PostHog (posthog SKILL.md); the owner's website sends GA4 events through one typed helper in consent mode, described in landing-page-ui DISCOVERY.md and google-analytics.ts. That design is the owner's and this skill does not replace it. The cookie banner, consent categories and script gating are cookie-consent SKILL.md; choosing attribution models and reconciling tools is marketing-attribution SKILL.md; experiment design is ab-testing SKILL.md.

Before asking questions, read .agents/product-context.md if it exists (defined in anti-slop-copy CONTEXT.md; the source calls this file .agents/product-marketing.md), then ask only what it doesn't cover: what decisions the data will inform and the key conversions, what tracking and tools exist, the stack and any privacy requirements [coreyhaines31/marketingskills, analytics].

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]