Skip to main content

This guide accompanies you step by step in the basic configuration of a Netvigie Tracking account. We will take the demonstration site https://ecommerce.seenaptic.com/fr/ as an example.

Step 1: Managing Environments

caution

By default, your account has an environment based on the URL provided at creation. You can add others, like a pre-production or QA environment.

  1. Go to Configuration > Environments.
  2. Click on Add an environment.
  3. Give it a name (e.g. "Pre-production").
  4. Enter the base URL of this environment.
  5. You can define it as the default environment if tests are to be mainly performed on it.
  6. Save.

Step 2: Creating Context Groups and Contexts

Contexts allow you to segment your site into logical page types.

  1. Create a Context Group:
    • Go to Site > Context Groups.
    • Click on Create a new context group (e.g. "Product", "Checkout").
    • Save.
  2. Create a Context:
    • Go to Site > Contexts.
    • Click on Add a context.
    • Name it (e.g. "Product Page").
    • Associate it with a group (e.g. "Product").
    • Provide an example URL: https://ecommerce.seenaptic.com/fr/vetements/p/52-121-t-shirt-femme-manches-courtes.html.
    • Define a context rule. For a product page, a simple rule could be: Collector {{Page pathname}} must contain /p/. (We will create the {{Page pathname}} collector in the next step).
    • Save.

Step 3: Creating Collectors

Collectors extract the data that will be used in your rules.

  1. Go to Site > Collectors.
  2. Click on Add a collector. Let's create three essential ones:
    • DataLayer Collector:
      • Name: dataLayer GTM
      • Type: DataLayer
      • DataLayer variable: dataLayer (for Google Tag Manager).
    • CSS Collector for the product name:
      • Name: Product Name
      • Type: CSS
      • Selector: .h1 (on our example site, the product name is in an <h1> tag).
    • URL Collector for the path:
      • Name: Page pathname
      • Type: URL
      • Property: pathname.
  3. For each collector, use the Verify button (by providing an example URL) to ensure it works, then Save.

Step 4: Creating Scenarios

Let's simulate an add to cart journey.

  1. Go to Site > Scenarios.
  2. Click on Add a scenario.
  3. Name it "Add to Cart".
  4. Step 1: Open the product page
    • Action: URL opening
    • Use the example URL of your "Product Page" context.
  5. Add a pause to wait for the page to load.
    • Click on the + button and choose Add a pause.
    • Type: Wait for a delay, Duration: 2000 (ms).
  6. Step 2: Click on "Add to cart"
    • Click on + and Add a step.
    • Action: Click.
    • CSS selector: .add-to-cart (the button selector on our example site).
  7. Use the Verify button to test the scenario, then Save.

Step 5: Configuring the DataLayer Tagging Plan

Let's verify that the page name is correct in the dataLayer on product pages.

  1. Go to DataLayer > Tagging Plan.
  2. A table appears with your contexts in columns. Click on the + at the intersection of the "Add a parameter" row and the "Product Page" column.
  3. A window opens. Configure the rule:
    • DataLayer: dataLayer GTM (the collector we created).
    • Parameter: page.name
    • Rule: must be exactly
    • Value: product_detail (expected value on a product page).
  4. Verify the rule, then Save.

Step 6: Configuring the Tag Tagging Plan

Let's verify that your Google Analytics account ID is correct on all pages.

  1. Import the tag:
    • Go to Tags > Tag Management.
    • Click on Import a tag and search for "Google Universal Analytics (pageview)". Import it.
  2. Configure the rule:
    • Go to Tags > Tagging Plan Settings.
    • Select the "Google Universal Analytics (pageview)" tag in the dropdown menu.
    • Click on the + in the "All contexts" column.
    • Parameter: tid (Tracking ID).
    • Rule: must be exactly.
    • Value: UA-XXXXXXXX-X (your tracking ID).
    • Verify and Save.

Step 7: Setting up and Launching a Crawl

Now, we are going to launch an analysis.

  1. Generate a version: Every configuration change must be "deployed" via a version. At the top of the interface, click on the button indicating "X unversioned changes", give a description (e.g. "Initial config") and deploy.
  2. Schedule the crawl:
    • Go to Crawls > Scheduling.
    • Click on Add a crawl configuration.
    • Name it "Daily monitoring test".
    • Crawl type: Monitoring.
    • Program it to run (or launch it manually).
    • Save.

Step 8: Analyzing Results

Once the crawl is finished:

  1. At the top right, select the crawl you just executed in the date/crawl selector.
  2. The homepage will give you an overview of scores and alerts.
  3. Go to Tags > Summary and DataLayer > Summary to see detailed results. Red cells indicate errors. Click on them to see:
    • Which rules failed.
    • On which URLs.
    • What was the expected value compared to the received value.

You now have a functional basic configuration to start monitoring your tracking quality!