Skip to main content

Advanced Features and Tools

This section covers tools and features that allow you to go further in your use of Netvigie Tracking, to integrate the tool into your processes and to manage complex configurations.

Using the Netvigie Browser Extension​

The Netvigie extension for Chrome is a powerful companion that allows you to interact with the platform directly from your site, without having to navigate in the main interface.

  • Installation:
    1. In the Netvigie Tracking interface, click on the Chrome icon in the header to access the Chrome Web Store.
    2. Install the extension and log in with your Netvigie credentials.
  • Key features:
    • Record a scenario:
      1. Click on the extension icon, then on the "Record" button.
      2. Navigate on your site and perform the actions of your journey.
      3. Click on "Stop". The extension will list all the steps you have performed.
      4. You can then name the scenario and save it directly in your Netvigie configuration. It is the fastest way to create scenarios.
    • Create a CSS collector:
      1. Right-click on any element of your page.
      2. Select "Create collector".
      3. A window opens with the CSS selector of the element. You can name the collector, test its value and save it.
    • Check a current page ("Live Check"):
      1. On any page of your site, open the extension and click on "Check the current page".
      2. The extension will perform a live test and display the results: the detected context, the tag and dataLayer scores, the missing tags, the rule errors, etc. It is an extremely effective debugging tool.

The Multisite Feature​

Designed for organizations managing multiple sites (by country, by brand) with tagging plans that share a common base but have specificities.

  • Objective: Configure a parent tagging plan base and override or add specific rules on the child sites.
  • Concepts:
    • Cluster: A group of configurations sharing a common base.
    • Node: A configuration level in the cluster tree (e.g. a "Europe" node parent of "France", "Germany" nodes). The first node is the "root".
    • Property: A final node associated with a real website. It is at this level that crawls are executed.
    • Inheritance: By default, a property inherits all rules configured on its parent nodes.
    • Override: On a property or a child node, you can "override" an inherited rule to modify it. The modification will only apply to this node and its descendants. A blue line in the interface indicates an overridden rule.
  • Practical case:
    1. On the "root" node (valid for all sites), you configure the rule: tid (GA tracking ID) must start with UA-123456-.
    2. On the "Site France" property, you override the rule so that it is more specific: tid must be exactly UA-123456-1.
    3. On the "Site USA" property, you override it differently: tid must be exactly UA-123456-2.

Using the Netvigie Tracking API​

For a deep integration into your CI/CD (Continuous Integration / Continuous Deployment) processes or to automate actions.

  • Authentication:
    1. The API uses JWT token authentication.
    2. To obtain a token, use the /api/token endpoint with your credentials. You will receive a token (valid 1 hour) and a refresh_token (valid 1 month).
    3. In all subsequent requests, you must pass the token in the authorization header: Authorization: Bearer YOUR_TOKEN.
    4. When the token expires, use the /api/token/refresh endpoint with your refresh_token to obtain a new one without having to re-authenticate.
  • Use cases:
    • Launch a crawl on demand after a production release.
    • Export the results of a crawl to integrate them into an internal dashboard.
    • Modify the configuration by programming.

Account and User Management​

  • Profile: Accessible via the profile icon in the header, it allows you to modify your personal information and your password.
  • User management (Configuration > Utilisateurs): You can add an unlimited number of users. Three roles are available:
    • Role View: Read-only access to crawl results.
    • Role Edit: Can modify the configuration (contexts, collectors, rules) but cannot manage crawls, versions or users.
    • Role Manage: Full access to all features, including administration.

Managing Configuration Versions​

Every modification you make in the configuration (creation of a collector, modification of a rule, etc.) is not immediately active. It must be validated and deployed via a version.

  1. At the top of the interface, a notification indicates the number of unversioned changes.
  2. Click on it or go to Configuration > Versions.
  3. You will see the detail of all pending changes.
  4. Give a description to your version (e.g. "Addition of tracking for new feature X - 20/10/2023"). This is a good practice to keep a clear history.
  5. Click on Deploy. Your modifications are now active and will be used during the next crawl.