a data layer can be seen as an object holding all the information to pass and process with google tag manager. this is a bit technical concept. the term data layer is used to denote the data structure used by google tag manager for storing, processing and passing data between your website/blog and the tag manager.

to elaborate it further, a data layer can feed the data into your analytics tool about your visitor. taking another perspective for the definition, data layer is actually a list of business requirements and goals for each subset of the digital context.

let us take an example of ecommerce website, business requirements might include −

transactional information, having the details about what was purchased
visitor data, regarding who purchased
other details about the purchase, such as where was the purchase made and at what time
lastly, the information about other factors, such as whether the visitor subscribed for the email updates or not

so, in a nutshell, the data layer carries information that can be used by different tools/users/stakeholders as required.

in google tag manager, datalayer is a javascript array. it consists of key-value pairs. following is a quick example of datalayer with different data types −

datalayer = [{
   'products': [{
      'name': 'western cotton',
      'tuning': 'high-g',
      'price': 49.75
   },
   {
      'name': 'fenda speakers',
      'tuning': 'drop-c',
      'price': 199
   }],
   'stores': ['hyderabad', 'bangloer],
   'date': sat sep 13 2017 17:05:32 gmt+0530 (ist),
   'employee': {'name': 'raghav}
}];

here, we have different values such as an array of objects (the products), numerical values (the price), an array of strings (stores), a date object and an object (name).

on another note, when you place google tag manager container code in your website, the data layer is automatically created.

in itself, data layer is a pretty complex concept to understand in the first go. this chapter will provide more insights on how to interact with the data layer.

data layer events

a quick example of data layer event can be, a newsletter signup form, which cant be easily tracked with automatic gtm listeners. a website developer can support you to push a data layer event once a new subscriber has entered his/her email on your website. the code of this event should look like this −

push({event: new_subscriber});

if you require, you can ask your developer for some more information, such as the form location. this is required if there are more than one form on your website. it can be achieved using the following code.

window.datalayer = window.datalayer || [];
window.datalayer.push({
   'formlocation': footer,
   'event': new_subscriber
});

also, google tag manager pushes a certain set of values to the data layer of web applications by default. these values are −

gtm.js − pushed to the data layer as soon as google tag manager is ready to run
gtm.dom − pushed to the data layer when the dom is ready
gtm.load − pushed to the data layer when the window is fully loaded

inspecting the data layer

as we already know by now, there are certain events that are created as a result of any interaction on the screen.

for instance, let us consider this simple page load event. to look at the events, you need to have the debugger running. once you have the debugger running (in preview mode), visit the blog. if you look at the summary window at the bottom left corner, this is what you will see −

step 1 − click window loaded and then data layer.

the information shown in the data layer tab is about the window loaded event.

it is shown as {event: gtm.load, gtm.uniqueeventid: 3}

further, if you want to take a closer look, you need to take support from chromes console tab. inspecting a data layer becomes easy when you know how to use chrome debugger in the correct way.

step 2 − when you are on your blog, right-click at any part in the page. in the context menu displayed, click inspect. the panel will be displayed at the right side of the screen, with elements tab activated.

step 3 − click console. when in the console mode, click the top left corner icon to clear all the messages shown. see the following screenshot for reference.

step 4 − once the window is cleared for any previous messages, type in datalayer, make sure the capitalization for l is done. this name is provided by google tag manager to its data layer. however, your developers may assign it a different name as and when required.

step 5 − press enter after datalayer. it will show the following details.

there are three objects, and each object contains some information. now, these objects might not be the same for you, as they are shown in the above screenshot. the datalayer is configurable and it is very much in the developers control to configure it as per the requirement.

the values that are present, are due to the blogger gadget that is in use at that particular position/space. this is the reason why there is certain information there.

if you look at object 1, you will notice that the event that is fired, is gtm.dom. it is fired by gtm while loading the page.

in this way, you can inspect the data layer and add information in it as and when needed.

variables in the data layer

now that we are acquainted with the data layer, let us try and read one of the variables using google tag manager interface.

here, we are going to try and read the event using a data layer variable.

if we see the above figure, the variable event holds the gtm.dom. we are going to create a variable from gtm interface and see how it reflects in the variables tab under google tag manager.

step 1 − in google tag manager interface, go to variables. scroll down to the user-defined variables. click new.

step 2 − provide a name to this new variable, let us call it as varevent.

step 3 − click choose a variable type to begin setup

step 4 − select data layer variable from the list.

step 5 − when you select data layer variable, you will be required to provide the name and version.

this name will be from the actual data layer of google tag manager. as mentioned previously, the variable that we will track is event.

step 6 − enter event in data layer variable name.

step 7 − click save.

step 8 − click preview to see the changes reflected in the debugger.

step 9 − once the page is loaded, click window loaded and then variables. scroll to the very bottom of variables section, you will see varevent, as highlighted in the above screenshot.

as seen in the above screenshot, the value will be gtm.load.

in this way, one can inspect the data layer and capture the values in the data layer as required.

Save or share this article