Set up analytics tracking for product decisions

Set up analytics tracking for marketing and product decisions

PM or analyst implementing analytics for SaaS product — full workflow from business questions → event design → GA4 setup, with essential event templates for apps and marketing sites.

• · Product marketing context file (if exists)
• · Business context (decisions data will inform, key conversions)
• · Current tracking state (existing tools, current tracking)
• · Technical context (tech stack, privacy/compliance needs)

• · Tracking plan framework (event, category, properties, trigger, notes)
• · Event types list (pageviews, user actions, system events, conversions)
• · Essential events by product type (marketing site vs. app)
• · Event naming conventions (object-action, best practices)
• · GA4 implementation with custom event example
• · Google Tag Manager container structure

• · GA4
• · Google Tag Manager (optional)

• · Analytics tool selected
• · Conversion funnel defined
• · Product marketing context available (optional)

• · Doesn't validate events are firing correctly — spot-check guidance only
• · GTM container structure is generic template
• · Data layer pattern is basic — complex implementations need custom design
• · Privacy/compliance mentioned but not covered in detail

• · Backward-looking workflow (business context → questions → events)
• · Event naming convention (object-action, snake_case, specific context)
• · Essential events table (marketing site: cta_clicked, form_submitted, signup_completed; app: onboarding, feature_used, purchase, subscription_cancelled)
• · GA4 custom event example with gtag.js
• · Data layer pattern for GTM implementation