Skip to content

GA4 + PostHog

Prerequisites

Section titled “Prerequisites”
  • Canonical event taxonomy and naming conventions.
  • Tag manager/admin access to GA4 and PostHog projects.
  • Consent mode strategy defined.

Steps

Section titled “Steps”
  1. Map canonical events to GA4 and PostHog equivalents; document property mappings.
  2. Implement client collection via Tag Manager/SDK with consent gating; send server copies where possible.
  3. Configure GA4 conversions and audiences; set PostHog properties and cohorts.
  4. Verify deduplication keys and identify calls to align users across tools.
  5. QA with a test plan: fire events, inspect payloads, and validate reporting.

Validation

Section titled “Validation”
  • Event counts within expected deltas (sampling, consent). Key properties present in both tools.

Troubleshooting

Section titled “Troubleshooting”
  • Missing events in GA4: check tag triggers, consent state, and debug view.
  • Identity mismatch in PostHog: ensure identify/alias calls at the right time.

Time/Impact

Section titled “Time/Impact”
  • 2–4 hours. Enables full-funnel visibility without vendor lock-in.
Section titled “Related”