Skip to main content

Verifying the Tag Tagging Plan

The logic is very similar to that of the DataLayer, but it applies to parameters sent by your tags (the "hits"). The objective is to verify that your tags fire at the right moment, with the right data.

Configuring tag rules on contexts

This concerns tags that fire upon page load ("pageview" type).

  1. Go to Tags > Tagging Plan Settings.
  2. In the dropdown menu, select the tag you wish to configure (e.g. "Google Universal Analytics (pageview)").
  3. The same table as for the DataLayer appears.
  4. Click on the + in the column of the desired context (e.g. "Product Page").
  5. Configure the rule for a tag parameter:
    • Parameter: The parameter name in the tag URL (e.g. pr1nm for the product name in GA).
    • Rule type: The condition.
    • Value: The expected value, which will often be a collector (e.g. {{Product Name}}).
  6. Save.

Example: To verify that the product name is indeed sent to Google Analytics on product pages, the rule would be:

  • Tag: Google Universal Analytics (pageview)
  • Context: Product Page
  • Parameter: pr1nm
  • Rule: must be exactly
  • Value: {{Product Name}}

Configuring tag event rules on scenarios

This concerns tags that fire following a user action ("event" type). These rules are therefore linked to the steps of your scenarios.

  1. Go to Tags > Events (or DataLayer > Events for dataLayer events, the logic is the same).
  2. Select the scenario you want to configure in the list.
  3. A view appears with the steps of your scenario.
  4. Automatic method (recommended):
    • Click on Verify. Netvigie Tracking executes the scenario.
    • For each step, the tool will indicate the tags (or dataLayer events) that were detected.
    • Click on the row "X tag(s) detected" to see the details.
    • As for the context configuration, you can use the + button to automatically add the detected parameters to your configuration.
  5. Manual method:
    • Click on a step of the scenario.
    • Click on New rule.
    • Select the event tag (e.g. "Google Universal Analytics (event)").
    • Add parameters one by one, specifying the expected value (often a fixed value like addToCart for the ec parameter - Event Category, or a collector like {{Product Name}} for the el parameter - Event Label).