Skip to main content

Analysis of Results and Corrective Actions

Once your crawls are finished, it is time to analyze the results to identify and correct tracking issues.

Interpreting the DataLayer Score​

  1. Go to DataLayer > Summary.
  2. You will find a global score and a detailed table (skewed table) displaying scores by context and by parameter.
  3. A red cell or a score lower than 100% indicates an issue. Click on the score to open the detail.
  4. The detail view will show you:
    • The coverage rate: on how many pages of the context the parameter was tested.
    • The list of URLs in error.
    • For each URL, the expected value and the received value, allowing you to precisely understand the nature of the discrepancy.
  5. The same principle applies to the DataLayer Scenario Score, which details errors by scenario step.

Interpreting the Tag Score​

  1. Go to Tags > Summary.
  2. The structure is similar to the DataLayer, with a global score and a table by tag and by context.
  3. By clicking on a score, you access the detail:
    • Tag coverage rate: Percentage of pages of the context where the tag was detected. A rate of 100% is generally expected.
    • Duplication rate: Percentage of pages where the tag fired multiple times. Often a sign of implementation error.
    • Score by parameter: The detail of the parameter rules that failed.
  4. By exploring the errors, you can see the expected value vs the received value for each tag parameter on each URL concerned.
  5. The Tag Scenario Score works in the same way, but analyzes tag events triggered at each step of your scenarios.

Alert Management and Analysis​

Netvigie Tracking automatically generates alerts when a significant degradation is detected between two crawls of the same type.

  • Access: Via the bell icon in the header or the "Alerts" section on the homepage.
  • Common alert types:
    • Score drop (Tag or DataLayer).
    • Missing tag.
    • New tag detected (unknown in your configuration).
    • Scenario in error.
    • Undefined page (crawled URL that matches no context).
    • Sensitive data detected in a tag.
  • Possible actions regarding an alert:
    • Analyze: The tool offers you a comparative view between the crawl in error and the last crawl where everything was correct, helping you identify the cause.
    • Resolve manually: If you judge that the alert is not relevant or that the new state is the norm, you can manually "resolve" it.
    • Pause: Pause the alert to stop receiving notifications, for example while your teams are working on a fix.

Tag and Resource Mapping​

This section (Tag > Tag Mapping) is a complete inventory of everything that fires on your site.

  • Tag view:
    • Lists all detected tags, whether they are in your configuration or not.
    • Indicates their coverage rate and duplication rate on each context.
    • Allows you to see at a glance if a tag is well deployed everywhere, or if it is present where it should not be.
  • Resource view:
    • Lists all network requests that were not associated with any known tag.
    • It is an excellent way to discover "piggybacks" (tags triggered by other tags) or unknown scripts.
    • From this view, you can easily create a new tag or add the resource as a "secondary script" to an existing tag.

The Request Management System​

To facilitate collaboration between marketing/product teams and technical teams.

  1. Go to Site > Request Management.
  2. Create a new request (e.g. "Add lead event tracking").
  3. Describe the request and assign it a status (In progress, To QA, etc.).
  4. Link the request to the relevant configuration elements in Netvigie Tracking (e.g. a specific tag event rule, a new row in a dataset).
  5. Share the request link with your technical team. They will be able to directly access the configuration, see the requirements and even test it live, which significantly speeds up the QA process.