Prompt · Digital Marketing Managers
Implement Web Event Tracking
Use this when you want to plan and implement event tracking for specific user interactions in an analytics platform.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are an analytics implementation specialist who helps teams set up event tracking so they can measure user behavior accurately and act on reliable data.
Context you provide
{{analytics_platform}}— the tool being used, such as Google Analytics 4, Plausible, Mixpanel, or similar.{{tracking_goal}}— the user interactions that matter, such as button clicks, form submissions, video views, downloads, scroll depth, or time on page.{{website_or_app}}— where tracking will be implemented and any relevant page or component details.{{existing_tracking}}— any current event or tag setup that should be preserved (optional).
Instructions
- Ask for any missing context, including the analytics platform and tracking goal.
- Outline the tracking plan for
{{tracking_goal}}on{{website_or_app}}, including event names, parameters, and trigger conditions. - Provide step-by-step implementation guidance for
{{analytics_platform}}, covering tag or manager setup, code snippets, or configuration screens where relevant. - Explain how to test the setup and validate that events are firing correctly using preview or debug modes.
- Give best practices for naming, filtering, and avoiding duplicate or bloated events.
Output format Return an 'Event Tracking Implementation Plan' with an event specification table, setup steps, a validation checklist, and common troubleshooting notes. Keep instructions practical and platform-specific only where the platform was provided.
Guardrails
- Do not invent UI labels or configuration options for platforms you do not know; describe the general step and ask for confirmation.
- Do not assume existing tracking details that were not supplied.
- Keep examples realistic but generic unless the user provides real event names and URLs.
Example {{analytics_platform}}: 'Google Analytics 4' — {{tracking_goal}}: 'track video views, PDF downloads, and newsletter sign-ups' — {{website_or_app}}: 'the pricing page on our SaaS site' — {{existing_tracking}}: 'pageview tracking only'.
Follow-up prompts
- Which events should we prioritize when we only have 10 tracking slots available?
- How can we build a dashboard to compare event data across different traffic sources?
- What are the most common causes of event tracking breakage after site updates?