GA4 Event Tracking QA Audit Prompt
Audit a Google Analytics 4 event tracking plan for naming consistency, parameters, conversions, attribution risks, and reporting readiness.
Prompt Template
You are a digital analytics QA lead. Audit a GA4 event tracking plan before or after implementation. Website/app context: [business model and main user journeys] Tracking plan: [paste event names, parameters, triggers, destinations] Primary conversions: [signup, checkout, lead form, trial activation, subscription, etc.] Platforms involved: [web, iOS, Android, server-side, GTM, Segment, RudderStack] Current reporting needs: [dashboards, funnel reports, ads attribution, product analytics] Known concerns: [duplicate events, missing parameters, consent mode, cross-domain, ecommerce, internal traffic] Naming conventions: [if any] Stakeholders: [marketing, product, data, agency, engineering] Provide: 1. Tracking-plan QA summary 2. Event naming and parameter consistency issues 3. Missing events or parameters by funnel stage 4. Conversion and attribution risks 5. DebugView / GTM / realtime testing checklist 6. Recommended fixes ranked by impact and effort 7. Final sign-off checklist for launch
Example Output
GA4 Tracking QA — Trial Signup Funnel
Summary
The plan covers page views, signup starts, form submissions, and trial activations, but it has inconsistent event names and missing parameters needed for campaign and plan-tier reporting.
Issues Found
- `sign_up_start` and `signup_submit` use different verb patterns; standardize to `signup_start` and `signup_submit`.
- `trial_started` lacks `plan_tier`, making free vs pro activation reporting impossible.
- Lead form events fire on button click, not confirmed success, which may inflate conversions.
- Cross-domain checkout is not documented; attribution may reset.
High-Impact Fixes
1. Add required parameters: `plan_tier`, `signup_method`, `user_type`, `source_page`
2. Fire conversion event only after server success response
3. Test cross-domain linker and consent mode behavior
Testing Checklist
- Use DebugView for one clean test user
- Confirm no duplicate events after refresh/back button
- Validate parameters in BigQuery export sample
- Compare GA4 realtime counts with backend signups for one hour
**Launch sign-off:** naming approved, conversions verified, dashboards updated, owner assigned for post-launch anomaly review.
Tips for Best Results
- 💡Ask the AI to inspect both event names and reporting use cases; technically captured events can still be useless for analysis.
- 💡Define whether events fire on click or successful completion — this is a classic analytics trapdoor.
- 💡Include a post-launch reconciliation step against backend data before trusting the dashboard.
Related Prompts
Data Cleaning and Preprocessing Checklist Builder
Generate a comprehensive data cleaning and preprocessing checklist tailored to your dataset type — covering missing values, outliers, encoding, normalization, and validation steps before analysis or model training.
Survey Sampling Bias Audit Builder
Audit survey results for sampling bias, nonresponse bias, weighting needs, and reporting caveats before making decisions from the data.
Dataset Summary and Insights
Paste or describe a dataset and get an instant summary of key statistics, patterns, anomalies, and actionable insights.