Use case #1: How do you keep a tagging plan up to date when it lives in a spreadsheet?
Teams concerned: Analytics • Marketing • Product • Data
The situation. The tagging plan lives in a Google Sheet. Is there an “up to date?” column ” that no one dares to fill out. When an event changes, someone alerts by email, and hopes that the right people open it. The file describes what should happen. No one is sure if they are describing what is going on anymore.
What we think about it. The problem is not the file. It's because a spreadsheet can't verify itself. As long as the plan is not confronted with the site, it silently expires. And it's believed that you shouldn't have to pay every month to access your own tagging plan. This is why we chose to make its governance free.
What Netvigie Tracking does.
- For free and with no time limit, you import your existing plan, without retyping it, and you structure it in a unique space: each event has its parameters, the pages where it is expected and the KPIs it feeds.
- You work with several people, with rights per team. Always for free.
- When you are ready, Data Quality connects this plan to the controls. The new events found on your site are presented to you with the control already proposed: all you have to do is accept it
What that changes. The tagging plan stops being a deliverable that we maintain as best we can. It becomes the common reference from which everything else is controlled.
Use case #2: How to deploy faster without breaking tracking?
Teams concerned: Product • QA • Development • Marketing
The situation. For many teams, Tracking remains the last point on the recipe checklist. The one you check by hand, page by page, if there is time left. Then the release leaves, the real users arrive, and an anomaly appears that no test had seen.
What we think about it. A recipe valid for one moment, not what happens the next day. Test before or monitor after? For us, the question is poorly asked: you need both, on the same journey.
What Netvigie Tracking does.
- Your critical paths are described once, recorded or dictated in French, and then automatically checked before each production launch.
- The same path continues to run in production, at the frequency you choose. An anomaly opens an alert, with its scope and its date of first appearance.
- Nothing is installed on your pages: your controls run in our browsers, with no impact on the performance of your site.
What that changes. The Tracking recipe is no longer a day of manual checks before each release. And when something breaks afterwards, you know it in the hours that follow, not in the monthly report.
Use case #3: Which tracking anomaly should be treated first?
Teams concerned: Marketing • Digital • Data • Management
The situation. Ten anomalies occurred the same morning. The most severe and the mildest present the same way. The team spends an hour figuring out which one deserves attention. And in the meantime, the anomaly that really matters continues to distort the conversion rate that will be presented to the committee.
What we think about it. Detecting has never been the hardest part. A parameter that is missing on a secondary page and the same parameter that is missing at the time of purchase are two errors on paper. In reality, it is not at all the same urgency.
What Netvigie Tracking does.
- Each alert says which KPIs are no longer guaranteed, on what scope and since when.
- The controls are replayed under controlled conditions before notification: the site that coughs once does not wake anyone up, without a real anomaly being ruled out.
- The message is written in plain text. It can be read without being a technician, including by the person who must decide if the subject comes first.
What that changes. You decide on facts, not on a pile of mistakes. The anomaly that threatens the conversion rate of the main tunnel comes first. Whoever touches a label will wait. Less time spent sorting, and especially fewer decisions made on false numbers: a budget moved to the wrong channel, a campaign cut wrongly.
Use case #4: How to manage the tracking of several brands without duplicating plans?
Teams concerned: Digital Department • CDO • CDO • Data • Marketing
The situation. At each new site, we duplicated the tagging plan to go quickly. Six months later, the same event is controlled in three different ways depending on the brand. And the day the headquarters asks for a group conversion rate, no one compares quite the same thing.
What we think about it. The challenge is not managing more sites. It's to avoid everyone operating in their own silo. The usual dilemma, a single plan that cannot be adapted or a plan per site that can no longer be maintained, is irrelevant.
What Netvigie Tracking does.
- All your brands are united in the same space, with a shared branding plan. The common definition is written once, the specificities of each brand remain local.
- A correction on a common event benefits all brands. A local peculiarity does not affect anyone else.
- Each team manages its perimeter, with its rights. The central team keeps the overview: each result and each alert refers to the site from which they come.
What that changes. “This tag only fails on the B brand” becomes a question that has an immediate answer, without comparing twelve reports. And your load is not growing at the rate of your sites.
What to remember
Four situations, the same logic: start with the marking plan, then have it respected.
- Structure a tagging plan that stays true over time.
- Check before production, and continue after.
- Prioritize anomalies according to the KPIs they put at risk.
- Manage all your sites from the same space.
The governance of the tagging plan is free, including on several sites. Controls, production monitoring and alerts fall under Data Quality.
And now?
The Netvigie Tracking governance tool is available to members of our Guest List. You leave your email address and you will receive your access as soon as it is opened.
