👋🏼 Introduction to Netvigie Tracking
Your tagging plan is the foundation of your data collection strategy. It ensures that you collect the right information, at the right time, to feed your analytics, marketing, and personalization tools. However, maintaining the quality and reliability of this tagging plan as your site evolves (production releases, redesigns, migrations) is a constant challenge.
Netvigie Tracking was designed to address this challenge by automating the testing and monitoring of your web or app tracking.
-
Simplify the Testing of Your Tagging Plan No more manual, tedious, and often partial verifications. Netvigie Tracking automates the testing of your dataLayers, your analytics and marketing tags, ensuring complete coverage and rapid detection of anomalies.
-
Classify Your Pages by Context for Efficient Verifications Your tags are not all necessary on all pages, and the data they collect varies. Netvigie Tracking allows you to classify your pages by context (e.g., homepage, product page, checkout funnel) to apply specific and relevant control rules to each type of page.
-
Create Custom Control Rules Should your Analytics tag capture the product price on all product pages? Should the value of this price match exactly what is displayed to the user? With Netvigie Tracking, you configure precise rules that reflect your tagging plan requirements, thus ensuring the reliability of the data you collect.
-
Manage Complex Tagging Plans (Brand Sites, Countries) If you manage multiple sites with similar tagging plans but with local specificities, the multisite functionality allows you to define a common base of rules while managing exceptions for each site, simplifying maintenance and ensuring consistency.
-
Archive and Version Your Configuration Your tagging plan evolves. Netvigie Tracking allows you to version your configuration. Every change is tracked, allowing you to follow the history of modifications and ensure that your tests are always aligned with the current version of your site.
-
Independent Integration with Your Ecosystem Netvigie Tracking works independently of your tools (TMS, analytics solutions, DMP, etc.) to provide objective and reliable verification of collected data, regardless of your technology stack.
Glossary of Key Terms
-
Alert: Notification generated when a metric degrades significantly between two crawls (e.g., score drop, missing tag).
-
Collector: Netvigie Tracking tool used to extract specific information from a page (e.g., CSS element content, cookie value, URL part). Collectors are the building blocks for creating rules.
-
Context: Group of pages sharing similar characteristics (e.g., all product pages). Contexts allow applying specific verification rules to a type of page.
-
Crawl: Process during which Netvigie Tracking robots explore your site to analyze pages and verify the rules you have configured.
-
Crawl Type: Defines the scope of the test.
- Monitoring: Only tests example URLs from contexts and scenarios. Fast and ideal for frequent verifications.
- Partial: Tests monitoring URLs plus a defined number of other site pages.
- Complete: Attempts to explore the entire site by following links.
-
Crawl Mode: Defines the state in which the browser is before performing tests. Allows simulating different types of users. Examples:
- Identified Visitor: The robot logs into a user account before crawling.
- Mobile: The robot uses a mobile user-agent and screen size.
- Without Consent: The robot simulates cookie rejection to verify GDPR compliance.
-
DataLayer: JavaScript object present on your site that stores and makes available structured information (about the page, user, products, etc.) for your tracking tools, particularly your Tag Management System (TMS).
-
Tagging Plan: Reference document that describes which tags and what data should be collected, on which pages, and when (on page load, during user action).
-
Scenario: Sequence of automated actions (clicks, text input, etc.) that simulates a user journey on your site (e.g., add product to cart, subscribe to newsletter).
-
Preparatory Scenario: A standard scenario used to define a Crawl Mode. For example, a login scenario is used as a preparatory scenario for the "Identified Visitor" crawl mode.
-
Tag Score / DataLayer Score: Percentage of verification rules (for tags or dataLayer) that were successfully validated during a crawl. This is a key indicator of your tracking quality.