Set Up Analytics Tracking and Event Measurement

Analytics Tracking guides measurement planning, implementation, and auditing for marketing sites and products. It starts with business decisions and conversion goals, then works backward to the events and properties needed to answer those questions. The emphasis is useful, consistent, validated data rather than collecting every possible interaction or optimizing vanity metrics.

Before asking for context, the workflow looks for an existing product-marketing document. It then establishes what decisions the data should inform, what tracking already exists, the technology stack, implementation ownership, and privacy constraints. The intended result is a documented measurement plan plus implementation and validation guidance.

Use it to set up or improve event tracking, review conversion measurement, organize UTM parameters, or audit a GA4 and Google Tag Manager configuration. It is relevant when teams cannot consistently answer which actions users complete or which campaigns contribute to a defined outcome.

Do not treat the event library as a requirement to collect everything. Each event should support a decision, and properties should avoid personally identifiable information. Platform interface paths, defaults, advertising features, and privacy requirements need current platform and jurisdiction-specific verification before implementation. A consent configuration example alone does not establish legal compliance or prove all tags honor the intended choice.

Inputs include business questions, key actions, existing analytics tools, application events, campaign naming rules, and consent requirements. The tracking plan records each event's name, category, properties, trigger, and notes. It also documents custom dimensions and conversions, including how outcomes are counted.

Naming guidance favors lowercase object-action names with underscores, specific events, and context in properties. Standard property groups cover page, user or account, campaign, product, session, and timing information. Avoid duplicating automatically collected values and maintain consistent parameter names. The supplied event example is:

gtag('event', 'signup_completed', {
  'method': 'email',
  'plan': 'free'
});

The included event library spans marketing navigation and engagement, calls to action, forms, signup and trial conversion, onboarding, feature use, errors, support, pricing, checkout, subscriptions, commerce browsing and carts, post-purchase actions, team collaboration, integrations, and account changes. Signup, purchase, and e-commerce funnel sequences show how events connect across stages. Choose the subset that matches actual product behavior and verify success triggers rather than counting an attempted action as a completed outcome.

Campaign conventions cover source, medium, campaign, content, and term. The guide recommends lowercase values, consistent separators, concise specificity, and a documented UTM registry.

The main implementation references cover GA4 and Google Tag Manager. GA4 topics include streams, enhanced measurement, recommended and custom events, conversion values and counting, dimension or metric scopes, audiences, internal-traffic filters, cross-domain sessions, retention, and Google Ads linking. Platform defaults and available features should be checked in the actual property.

GTM separates tags, triggers, and variables. Its examples use dataLayer events, nested properties, form and button handlers, e-commerce objects, and clearing previous commerce data before a new event. It also covers descriptive names, workspaces, version notes, tag sequencing, exceptions, lookup variables, and custom JavaScript. Advertising-pixel examples are configurations to review rather than preauthorized tracking.

Validation uses DebugView, GTM Preview, Tag Assistant, and data-layer inspection. Check correct triggers, property values, duplicate events, conversion counting, browser and mobile behavior, and absence of personal-data leakage. Troubleshooting distinguishes missing tags, wrong variable paths or timing, repeated triggers, filtering, parameter-name mismatches, and processing delays. Consent-aware collection includes default denied states, deliberate updates, data minimization, retention and deletion capabilities, and integration with a consent-management platform.

The tool registry additionally names Mixpanel, Amplitude, PostHog, and Segment as analytics options. Related workflows use the resulting data for experiments, SEO analysis, conversion optimization, and revenue operations; their inclusion does not mean those services are configured.

This skill supports marketing and product teams, together with their implementing developers, who need a documented measurement system and a way to verify that collected events answer real business questions.