Set up GA4 event tracking
trackingskillsetup L2★468
kostja94/marketing-skills ↗Causal-lift measurements
event-tracking-design0pp vs no-skill baselinewith-skill 68% · baseline 68%
Measured by running the task with and without this artifact, K=5, graded by deterministic checks — no LLM judging.
What it does
Set up GA4 tracking, event naming, and conversion attribution
Best for
Content marketer or analyst tracking article ROI via CTA clicks and funnel attribution — sets up user ID for cross-session tracking, event naming convention for consistency, and conversion marking for multi-touch attribution.
Inputs
- · GA4 property and web data stream setup
- · Custom event list (business-specific conversions)
- · CTA attribution articles (URLs for per-article conversion tracking)
Outputs
- · User ID configuration (cross-device, cross-session)
- · Event naming convention guide (snake_case, verb-first, specific)
- · CTA attribution tracking (event per CTA, conversion marking)
- · Infrastructure requirements checklist (data warehouse, event tracking, attribution)
Requires
- · Google Analytics 4
- · Google Tag Manager (optional but recommended)
- · Data warehouse (optional — for attribution)
Preconditions
- · GA4 property created
- · Web data stream configured
- · gtag.js or GTM container active
Failure modes
- · User ID implementation assumes login flow (doesn't cover anonymous → authenticated transition)
- · Event naming conventions are guidelines only — no schema enforcement
- · CTA attribution assumes article URLs are trackable (not gated/dynamic content)
- · Conversion attribution model guidance is GA4-default focused (doesn't compare other models)
Trust signals
- · User ID setup for cross-device tracking
- · Event naming convention (snake_case, verb-first, specific context)
- · CTA attribution method (event per CTA, conversion marked in GA4)
- · Infrastructure requirements listed (data warehouse, event tracking, attribution)