Why create a tagging plan?
The tagging plan is the reference document that formalizes what you want to measure on your site or application: events, variables, trigger conditions, user parameters, etc.
It ensures consistency between business needs and technical implementations, while serving as a basis for managing data quality. To go further, see our article: Your Tag Management must also be RGPD Compliant.
Above all, ask yourself the right questions
Before opening your spreadsheet, start by defining the goals of your tracking:
- What are the strategic indicators (KPIs)
- What data are you going to rely on to pilot your actions?
- What metrics directly influence your conversions (or North Star Metrics)?
- Who will use this data? For what analyses?
This prior thought will prevent you from falling into the trap of overtracking.
Events: measure only the essentials
An event is an action that you want to track (e.g. click, add cart, scroll). The frequent error? Wanting to measure everything, without prioritizing. This overloads your tools, complicates analyses, and dilutes the value of your data.
To do:
- List events related to your marketing goals.
- Filter according to their real contribution to your business KPIs.
- Limit events that are purely informative or incidental.
Event parameters: to enrich the data
Associate each event with contextual parameters useful for analysis: product type, color, value, channel of origin...
- Prioritize useful data over your dashboards and segments.
- Pay attention to the limitations of your tool (GA4, for example, limits the number of parameters per event).
- Group what can be grouped together: structure your settings to limit redundancy.
User parameters: an enriched customer vision
In cookieless, user data becomes strategic. Fill in the information useful for customer knowledge :
- Fixed data: registration date, country, device...
- Dynamic data: type of subscription, loyalty status...
- Anticipate the segments you want to create later.
Structure of the marking plan: what should it contain?
Create a document that is clear, shared and understandable by all teams (Data, IT, Marketing, Product).
Include:
- Name of the event
- Measurement objective
- Parameters collected
- Trigger conditions
- Datalayer variables
- Affected pages
- Implementation example
Also add a “status” column to follow the evolution: to be created, active, obsolete, being deleted...
A living, maintained and monitored
plan A tagging plan is not a fixed document. Each evolution of the site or your data stack must be reflected there. It is also a key element in your GDPR compliance.
To guarantee its reliability:
- Recover your tracking regularly
- Automate control with tools like Seenaptic
- Create alerts to detect regressions
- Document every change
In summary
, a good tagging plan is:
-> A strategic vision of useful data -> A shared and maintained repository -> Clear governance -> A tool to better collect, not to collect everything
Objective: to ensure reliable, useful, activatable and compliant data to calmly manage your
digital performance.This document will also be shared with the technical implementation teams. A good translation of business needs to these teams will be crucial to the proper implementation of these teams.