Skip to main content
All CollectionsAdmin
Monitoring a Data Layer
Monitoring a Data Layer
Product Enablement avatar
Written by Product Enablement
Updated over a week ago


A data layer is a JavaScript object that you can use to pass information from your website to your Tag Manager container. You can then use that information to populate variables and activate triggers in your tag configurations.

Here are some resources for learning more about a data layer and how to use it:

Image Source - Umbraco

Adding Your Data Layer to ObservePoint

In most cases, your data layer and its objects will be able to be called by the name of the data layer. You’ll need the name of the data layer to add it to your Audits and Journeys (the name is determined by someone internally at your company).

The first step is to go to your Account Settings within ObservePoint, by clicking the cog icon in the bottom left corner and select Sub-Folders:

Once you're in the Sub-Folders menu, follow the next steps:

  1. Tick the box of the sub-folder where you want to add your data layer;

  2. Click on the 3 dots on the left;

  3. Choose Edit.

Then, on the box that pops-up, add the name of the data layer of your choice and then click Save:

You can add more than one by putting a comma between the names. Once you have saved the data layer name you’ll need to rerun any Audit or Journey you’re wanting to see it in right away, otherwise you’ll see it show on the next run of any Audits or Journeys that are associated with that domain.

Looking at a Data Layer in your Audit/Journey

Any report that would show your tagging technologies will now also show the data layer on pages where it is found. It will show up as a tag (see screenshot).

You can see the variables for your data layer in the Variable Summary report of an Audit or by expanding the data layer within a Journey report.

Monitoring Your Data Layer

Once you’ve added your data layer to your domain(s), you can begin to set up alerts for your data layer. Just like any other rule in the ObservePoint, you can go from basic to complex. Here the three main use cases:

Monitor for Data Layer Presence

The rule set up below will check every single page and give you an alert if it does not see the data layer. You could change this up by adding a filter to the top and filter for URLs where you should have the data layer or if it sees the Adobe tag it should expect the data layer.

This rule setup is checking a specific variable within the data layer is correct. This rule says, on pages where the URL contains about-us or careers, I expect the Data Layer to have a variable called pageType that matches a regex for aboutus|careers (the pipe symbol | in regex means or).

If on a page where the URL contained about-us or careers it saw the data layer was missing, the data layer variable pageType was missing, or the data layer variable pageType did not match about us or careers it would then send an alert if you have your email set for notification.

If your data layer is passing information to your tags you can use rules to compare the two. This rules says on all pages, I expect the Adobe Analytics tag to have a variable called 0.pageType and the value for that variable to be the same value as the Data Layer’s value for the variable pageType on that page.

Common Data Layers

  • W3C Standard: digitalData

  • Ensighten: ensBootstraps

  • Tealium: utag_data

  • Google: dataLayer

  • Adobe Launch: _satellite

  • Signal: brightTagPixelPartner (model object) or BrightTag [case sensitive]

  • TagCommander: TCVars

Array Indexing

Google Tag Manager's Data Layer commonly includes arrays. When creating rules, you will want to use Regex for the name. In the screenshot below, you can see an example where we select the pageName variable regardless of which number precedes it (the preceding number represents the array index).

Did this answer your question?