Your Tagging Plan: From Strategy to Set-up to Scalability in 7 Steps

Play Video
Your Tagging Plan: From Strategy to Set-up to Scalability in 7 Steps

The votes came in: your company wants a data democracy. And you’re no dictator—you’re ready to give the people what they want. But democratizing data doesn’t just mean making your analytics platform available to the masses, you thoughtfully realize. True data democratization starts at ground zero, letting teams deploy the tags they need to collect their own data. A little MarTech here, a sprinkle of MarTech there—no harm done, right?

Yeah, until suddenly your implementation is bogged down with so many tags, your website is taking hours to load and your technology team can’t keep up with the growing docket of tagging errors lighting your data on fire.

A democracy doesn’t sound so great anymore, does it? It’s a cruel irony indeed that data democracy can lead to data corruption.

So you’re at an impasse. Do you tighten your grip on data collection to avoid letting things get out of hand? Or do you let your teams have free rein and then compensate by appropriating more funds to the technology fire department? Either way, you will have to sacrifice a great deal.

This is where you stand. You need a way to realize the benefits of data democracy without losing control of what people deploy on your site.

You need a constitution for your data democracy. You need a tagging plan.

What is a Tagging Plan?

Referred to by myriad names, including: variable map, solution design reference (SDR), tech spec, site reference and more, a tagging plan is the documentation of your digital analytics strategy and process—a foundational piece of your data governance framework.

A tagging plan is the blueprint for your analytics implementation.

A tagging plan takes business requirements identified by stakeholders throughout your organization and maps them to metrics that can be measured across your digital properties.

The tagging plan helps analytics architects know where, when, and how to implement code.

Why You Need a Tagging Plan

A tagging plan creates a baseline for data governance processes, to ensure organizations are maximizing the ROI of their MarTech stack and collecting high-quality data to make strategic business decisions.

According to Forrester Research, “Data Governance programs have a way of starting and then fading away. This creates peaks and valleys in an organization’s ability to engage relevantly with their analytics program. Forrester finds that 45% of organizations govern data inconsistently across business units.”

Documentation is essential to collecting and governing high-quality data. Without a tagging plan:

  • Business initiatives fall through the cracks
  • Analytics efforts fail
  • Code degrades
  • Tagging errors pile up
  • Data quality suffers

Establishing a Tagging Plan in 7 Steps

Designed to build on one another, each of the following steps steers your team towards greater data governance capability in a simple and scalable way.

  1. Ownership of the tagging plan
  2. Location of the tagging plan
  3. Collecting business requirements
  4. Defining metrics to measure
  5. Building the tagging plan
  6. Coding the tagging plan
  7. Maintenance and QA

Whether you are building a tagging plan in-house or utilizing the services of an expert agency, ensuring each of the above areas is addressed sets your team up for success.

Step One: Ownership of the Tagging Plan

There are two critical points of leadership for establishing the tagging plan and creating a culture of true data governance in an organization.

Data Governance Leader

With direct ownership of data governance and quality in an organization, a data governance leader should have the correct background and authority, including:

  • A strong technical background
  • Familiarity with MarTech solutions
  • Knowledge of the platforms their digital properties are built on
  • Organizational seniority
  • Understanding of the business value of data
  • Thorough data orientation

Industry research indicates that organizations with a dedicated data leader, what Forrester calls a Chief Data Officer, are top performers.

Data Governance Council

In supporting the data governance leader, a data governance council should be composed of business leaders from all areas of the company who understand their unique business objectives and the company mission. A data governance council should:

  • Incorporate leaders from Marketing, Sales, IT, Operations, Finance, Human Resources, etc.
  • Respond to requests of the data governance leader
  • Meet at least quarterly to review the tagging plan
  • Be a strategic priority

The key to having an effective data governance program is to prioritize and maintain it. A regular meeting of the data governance council might include the following:

  • Review quality assurance notes on the latest implementation
  • Discuss any outstanding actions on your implementation, such as inactive tags
  • Review the business requirements and discuss potential additions

Step Two: Location and Format of the Tagging Plan

Treat your tagging plan as a living, breathing document.

Step Two: Location and Format of the Tagging Plan

Step Three: Collecting Business Requirements

Every business has unique objectives and data needs. A tagging plan should always be aimed at understanding these needs in order to provide an actionable and accurate measurement and implementation plan.

Identifying your business requirements begins with business questions:

1. Why are we doing this?

2. What do we want to know about the user?

Your business requirements should articulate, specifically, what you want to know about the user experience (UX).

Example: If you would like to know the channels visitors use to reach your website, you can include that as one of your business requirements.

Answering the initial questions around identifying your business requirements usually involves asking another question like, “What is their objective for being on our site?” These secondary questions will lead you to determine specific use cases.

Example: You might be wondering, “Are visitors to the site finding the content that they are looking for?” Or even just, “What are visitors looking for?”

You can quickly generate a list of unorganized questions, and then work to focus your collection. This will save you more time throughout the next steps of building your tagging plan.

Categorizing Business Objectives

Analytics Demystified experts recommend categorizing the business objectives your stakeholders want to know and then mapping each question back to the appropriate category, or use case.

So, your collection document might look something like this:

Categorizing Business Objectives

Conversion Events Chart

Step Four: Defining Metrics to Measure

Ask yourself, “What story does this metric tell? How can it help leadership make the right decisions?”

Every metric should be mapped to an end goal.

Once the data governance council has established what they want to discover, analysts and developers should work together to define appropriate metrics to generate actionable insights.

One of the challenges in this is that while analysts may have a solid understanding of how the data that is unique to each business goal should be analyzed and represented, they are often working with stakeholders who may not.

Generating example reports helps address this common disconnect.

It is tempting to skip this step because it is time-consuming, but generating mock analytics reports has several advantages, in that it:

  • Validates that your team is collecting the right information
  • Shows stakeholders they will be able to make decisions about their digital asset with these reports
  • Helps your analytics team understands the business requirements
  • Provides an opportunity to refine your metrics
  • Lessens the likelihood that your team will have to go back and implement tracking that was overlooked during initial discovery

Here are some questions to ask:

“Are my visitors finding the content that they are looking for?”

If a user is looking for something on your site, they will most likely utilize the internal search function. Businesses must consider user search actions and how they can be measured.

The second part of the business requirement is:

“Did they find what they were looking for?”

This can be measured by whether or not their search yielded results. The metric that combines these two use cases would be an internal search that yielded results.

“Are visitors getting the information they need from the frequently asked questions section of my website?”

A corresponding user action could be clicking a link to the FAQ page or expanding a FAQ field. You can monitor the frequency of clicks on certain FAQs to understand what your visitors want to learn more about.

Step Five: Building the Tagging Plan

A tagging plan concisely outlines all the events and coding details to help your data governance council and designated programmers maintain coherency and consistency with your metrics.

Once you have decided on a specific event for each metric, you can begin assembling your tagging plan.

Make sure that you give your tagging plan a name that is clear and concise, along with some context, like the website name and some sort of timestamp.

A comprehensive tagging plan is a matrix of use cases and variables. It should contain similar information to the chart provided:

ObservePoint Tagging Plan

ObservePoint Tagging Plan Chart

Step Six: Coding the Tagging Plan

A completed tagging plan will provide programmers all the necessary information to code an effective analytics implementation that produces actionable data.

The tagging plan will serve as a reference point for all who collaborate on the project in the short and long terms.

Once you have documented your tagging plan, your team can really dive in and start programming the implementation in a staging environment.

This will usually be done by an IT team, but with the amazing power of some tag management systems, marketers can also build analytics rules themselves, easing demand on the IT department.


If you don’t have the resources to code your implementation in-house, don’t be afraid to work with a contractor or an agency that specializes in analytics implementations. The only thing worse than no data is bad or misleading data—and you could save yourself a lot of frustration and headaches if you outsource this essential task to an experienced analytics firm.

Step Seven: Maintenance and Quality Assurance

Validate your analytics implementation against your tagging plan during staging, development and after release.

Missing, misfiring or duplicate tags can result in incomplete or misleading data, which destroys confidence in your data for decision-makers. Always double- and triple-check your tagging integrity, even when using a tag management system.

When to Perform QA:

  • In a staging environment before releasing your implementation
  • After releasing your implementation
  • Periodically to ensure that any updates or changes have not affected the functionality of your implementation

Automated Governance and Validation

Tag management systems have made it extremely easy to build and deploy code, both for programmers and marketers. If not properly regulated, however, the ease of deployment can lead to issues with your implementation. Massive amounts of tags deployed on multiple sites, with subdomains and different languages operating on different browsers, can make monitoring and maintaining all of these implementations a very sticky job—one that takes thousands of hours of manual spot-checking and validation.

Thankfully, automation is possible.

Constant validation allows you to keep your baseline true.

As an example, ObservePoint’s rule-based scans can be used to run audits on thousands of pages to ensure that your analytics tags are firing correctly, according to the expectations established in your tagging plan.

In addition, active critical-path monitoring can keep you apprised of any issues keeping critical paths from functioning properly and users moving through your site towards conversion.

See ObservePoint in action by watching the below 9-minute demo.

Summary – 7 Steps

1. Ownership of the tagging plan

2. Location of the tagging plan

3. Collecting Business Requirements

4. Defining Metrics to Measure

5. Building the tagging plan

6. Coding the tagging plan

7. Maintenance and QA

Building a successful analytics implementation is essential to understanding and responding to user behavior and maximizing the functionality of your website. Tag management systems, automated governance solutions, and other analytics tools have simplified the process of deploying and maintaining analytics implementations.

The best way for your organization to accomplish your goals is to really take control of your data governance and develop a tagging plan outlining all of the business requirements that you hope to achieve through your implementation.

Doing so emphasizes that your marketing data is an enterprise asset—one that drives your competitive advantage and ultimately your bottom line.

To see how ObservePoint’s automated governance solution can help your business, request a custom pre-recorded demo showcasing an audit of your site.

Browse your favorite Categories

Want to go deeper? Click on a category below for more from the Observe Point

Schedule a Meeting