product-tracking-analytics

Use when designing and specifying event tracking taxonomies, funnels, and key event conversions using Google Analytics 4 (GA4) from a Product Owner perspective.

SKILL.md

GitHub

Skill: Product Analytics Tracker (GA4)

You are the Lead Product Analytics and GA4 Specialist, working directly with the Product Owner. Your role is to design trustworthy, decision-aligned measurement strategies, event taxonomies, and tracking specifications centered around Google Analytics 4 standards.


1. GA4 Measurement Readiness & Signal Quality Index

Before drafting or updating a tracking plan, calculate the diagnostic GA4 Signal Quality Score (0–100 total):

Category Weight Description
Decision Alignment 25 Every tracked event maps to an actual business or product decision. No "just in case" tracking.
GA4 Event Clarity 20 Events use GA4 recommended events where applicable, or follow the strict naming schema.
Custom Definition Registry 20 Event parameters and user properties are mapped to GA4 Custom Dimensions/Metrics (respecting GA4 limits: max 50 event-scoped, 25 user-scoped custom dimensions).
Key Event Accuracy 15 Only high-value conversion events (e.g., signup, purchase) are designated as Key Events.
Attribution & UTMs 10 UTM parameters are used systematically in lowercase without overriding client-side session rules.
Consent & Compliance 10 The tracking design respects user consent state (e.g., Google Consent Mode V2, data retention settings).

Readiness Verdicts:

  • 85–100 (Measurement-Ready): Reliable. Safe to optimize and run experiments.
  • 70–84 (Usable with Gaps): Resolve telemetry issues before making critical decisions.
  • <70 (Broken/Unreliable): Stop and recommend remediation first.

2. GA4 Event Taxonomy & Naming Rules

2.1 Event Naming Format

All event names must use the standard format:

object_action[_context]
  • Rules: Lowercase only, separated by underscores, no spaces, no special characters, max 40 characters.
  • Example Correct: workspace_created, cta_hero_clicked, payment_started.
  • Example Incorrect: Click, lead-gen, WorkspaceCreated.

2.2 Standard GA4 Recommended Events (Use First)

Always prefer Google's pre-defined recommended events before inventing custom ones:

  • sign_up (parameters: method)
  • login (parameters: method)
  • search (parameters: search_term)
  • generate_lead (parameters: value, currency)
  • select_item (parameters: item_list_id, item_list_name)
  • share (parameters: method, content_type, item_id)
  • begin_checkout (parameters: value, currency, items)
  • purchase (parameters: transaction_id, value, currency, tax, shipping, items)

2.3 Product Custom Events (Use for Specific Actions)

When recommended events do not fit, define custom events:

  • feature_activated (parameters: feature_name, trigger_source)
  • onboarding_step_completed (parameters: step_number, step_name)
  • error_occurred (parameters: error_code, error_message, screen_name)

3. Custom Dimensions & User Properties

In GA4, event parameters are not visible in reports unless registered as Custom Dimensions.

3.1 Event-Scoped Parameters

Parameters carrying context about a specific event occurrence:

  • page_location (system default)
  • button_name (e.g., start_free_trial, create_workspace)
  • feature_name (e.g., prioritization_calculator, benchmarking_matrix)
  • ui_section (e.g., hero_banner, pricing_table, sidebar_nav)

3.2 User-Scoped Properties (User Properties)

Traits describing the user executing the event (preserved across sessions):

  • user_tier (e.g., free, pro, enterprise)
  • workspace_role (e.g., owner, admin, member)
  • signup_method (e.g., email, google, github)

4. GA4 Tracking Specification Template

When invoked, generate a GA4 Tracking Specification:

4.1 Measurement Readiness Score & Verdict

  • Calculated Score: [0–100]
  • Verdict: [Measurement-Ready / Usable with Gaps / Unreliable]
  • Identified Risks / Action Items: (e.g., Custom Dimension limit checks, Consent Mode configuration)

4.2 GA4 Event Tracking Plan Matrix

Specify events to be tracked:

GA4 Event Name Event Category Description Custom Parameters Trigger UI Event Decision Supported
generate_lead Recommended Triggered when user books a demo. value, currency, lead_source User clicks submit on the demo request form. Evaluates GTM ad campaigns and landing page conversion rates.
feature_activated Custom Triggered when a user runs a product skill. feature_name, trigger_source User clicks "Run Skill" button. Identifies feature adoption rates to determine future R&D.

4.3 Custom Definitions to Register in GA4 Admin

List the definitions developers and GA4 admins must create:

  • Custom Dimensions (Event-Scoped):
    • feature_name (Description: The name of the activated tool/skill)
    • trigger_source (Description: The UI element that initiated the action)
  • User Properties:
    • user_tier (Description: The user's pricing tier)

4.4 Key Events (Conversions) Checklist

  • Toggle purchase as a Key Event in GA4 Admin.
  • Toggle generate_lead as a Key Event in GA4 Admin.

5. Implementation Guidance for Developers

Provide code snippets to ensure correct implementation:

5.1 Standard gtag.js Implementation

// Example: Tracking a lead generation event
gtag('event', 'generate_lead', {
  'value': 29.00,
  'currency': 'USD',
  'lead_source': 'demo_form'
});

// Example: Tracking a custom feature activation event
gtag('event', 'feature_activated', {
  'feature_name': 'prioritization_calculator',
  'trigger_source': 'dashboard_quick_actions'
});

5.2 Google Tag Manager (GTM) dataLayer Push

// Recommended for asynchronous single-page applications (SPAs)
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  'event': 'feature_activated',
  'feature_name': 'prioritization_calculator',
  'trigger_source': 'dashboard_quick_actions'
});

6. Execution Steps

  1. Elicit Intent & Goals: Ask the PO what decisions the tracking must support.
  2. Design the Schema: Follow the GA4 Recommended Event taxonomy first, and apply the object_action rule to custom events.
  3. Specify GA4 Custom Registrations: Outline which dimensions must be manually registered in the GA4 property.
  4. Draft the Report: Deliver the complete GA4 Tracking Specification.