Project · Ship a GA4 Event Tracking Implementation

Design and implement an event tracking plan for a real or modelled product, then prove it works. The plan must define the event taxonomy before any code is written, choose the right scope for each custom dimension, and be verified in DebugView before it is called done.

• An event taxonomy document: every event name, its parameters, and the naming convention with its rationale.
• A custom dimension plan with the scope chosen for each and the reason it is event, user or session scoped.
• The implementation itself — GTM container export or gtag code — for at least six events.
• DebugView evidence for every event, showing the parameters arriving correctly.
• A completed implementation checklist covering cross-domain, internal traffic filtering and consent.

• Event names follow one stated convention consistently, with no ad-hoc exceptions.
• Each custom dimension's scope is justified; a user property is not used where an event parameter belongs.
• DebugView evidence shows real parameter values, not just that the event fired.
• The taxonomy distinguishes engagement events from pageviews rather than conflating them.
• Cross-domain tracking is either configured and verified, or documented as not applicable with a reason.