Skip to main content

👋🏼 Introduction to Netvigie Tracking

Your tagging plan is the foundation of your data collection strategy. It guarantees that you collect the right information, at the right time, to feed your analysis, marketing, and personalization tools. However, maintaining the data quality and reliability of this tagging plan throughout the evolutions of your site (deployments, redesigns, migrations) is a constant challenge.

tip

Netvigie Tracking was designed to answer this challenge by automating the QA and monitoring of your web or app tracking.

  • Simplify the QA of your Tagging Plan No more manual, tedious, and often partial verifications. Netvigie Tracking automates the tests 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 (ex: home page, product page, checkout funnel) to apply specific and relevant control rules to each type of page.
  • Create Custom Control Rules Must your Analytics tag report the product price on all product pages? Must the value of this price correspond exactly to the one displayed to the user? With Netvigie Tracking, you configure precise rules that reflect the requirements of your tagging plan, thus making the data you collect reliable.
  • Manage Complex Tagging Plans (Brand Sites, Countries) If you manage multiple sites with similar tagging plans but presenting local specificities, the multisite feature allows you to define a common base of rules while managing exceptions for each site, simplifying maintenance and guaranteeing consistency.
  • Historicize and Version your Configuration Your tagging plan evolves. Netvigie Tracking allows you to version your configuration. Each change is tracked, allowing you to follow the modification history 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 offer an objective and reliable verification of the collected data, regardless of your technological stack.

Glossary of Key Terms

  • Alert: Notification generated when a metric degrades significantly between two crawls (ex: score drop, missing tag).
  • Collector: Netvigie Tracking tool used to extract specific information from a page (ex: the content of a CSS element, the value of a cookie, a part of the URL). Collectors are the building blocks to create rules.
  • Context: Group of pages sharing similar characteristics (ex: all product pages). Contexts allow applying verification rules specific to a page type.
  • 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: Tests only the example URLs of the contexts and the scenarios. Fast and ideal for frequent verifications.
    • Partial: Tests the monitoring URLs plus a defined number of other pages of the site.
    • Complete: Attempts to explore the entire site by following links.
  • Crawl mode: Defines the state in which the browser is before performing the tests. Allows simulating different types of users. Examples:
    • Identified visitor: The robot logs into a user account before crawling.
    • Mobile: The robot uses a user-agent and a mobile screen size.
    • Without consent: The robot simulates a refusal of cookies to verify GDPR compliance.
  • DataLayer: JavaScript object present on your site that stores and makes available structured information (about the page, the user, the products, etc.) for your tracking tools, notably your Tag Management System (TMS).
  • Tagging plan: Reference document that describes which tags and which data must be collected, on which pages, and at what time (on page load, during a user action).
  • Scenario: Sequence of automated actions (clicks, text entries, etc.) that simulates a user journey on your site (ex: adding a product to the cart, subscribing to a newsletter).
  • Preparatory scenario: A standard scenario that is 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 the tags or the dataLayer) that were successfully validated during a crawl. It is a key indicator of the quality of your tracking.