Data layer validation is a key component to accomplishing an effective data governance strategy.
As Jason Call stated in his introductory blog post to the data layer,
For those of you who have implemented a data layer, you did so because you wanted to:
- Standardize data across marketing technologies.
- Maintain consistent data collection despite changes to HTML structure.
- Reduce development time for implementing new technologies.
Here are the steps to set up data layer validation in the OP platform:
Steps to Setup
Identify your data layer
- Talk with your developers:
- There may be multiple “data layer” type objects in use on your site(s). It pays to use the correct one the first time. Considerations should include identifying “out-of-the-box” objects associated with tag management solutions, as well as custom objects.
- Optional – confirm with your tag management system configuration.
- Direct confirmation:
- Avoid assumptions. Once you know the object name, confirm it in the console of your web browser. To do so, open the console and type in the object name. If it exists, it should autocomplete for you. Press the “Tab” key to autocomplete. Below are several examples of data layer object names and output for reference:
- Object name = dataLayer (Google Tag Manager)
- Object name = digitalData (W3C Standard)
- Object name = _hddata (custom object)
Setting up a new domain for data layer validation
- Inside the ObservePoint web application, there is a “Create New” button at the top left. Click this button and select “Domain.” A modal will appear that looks like this:
- Select a folder, or create a new folder.
- Name this web property.
- Add the domain, including the protocol.
- Save your settings.
Editing the data layer of an existing domain
- Open the folder containing the targeted domain.
- Find the domain to which you want to add a data layer. Click the three dots in the upper right-hand corner of this domain.
- Enter the object name and save your settings.
- Some common object names are:
- digitalData – W3C
- dataLayer – Google Tag Manager
- utag_data – Tealium
- Setting up a data layer is optional. If no object name is defined, the domain, and all audits or simulations contained therein, default to “digitalData,” which is the W3C standard for data layer objects.
- Dot syntax is supported. For example, if your data layer is a member of a larger object, best practice is to limit the definition to the portion of the object that is specific to that purpose. An example of this is Adobe Activation’s default data layer, _satellite, which is a large, system-generated object that contains more than just digital consumer data. Use dot syntax to select only the portion specifically defined for data layer usage.
- Avoid large objects in general. While even large objects are supported, it makes reporting and understanding that data difficult. Variables should be specific to your vendor tag implementations. If more than that is contained therein, the utilization of that object of data layer usage should be reconsidered.
Reporting for data layer details is similar to that of tags, in which variables are scanned from the object with values aggregated and reported on a per page basis. Once the domain settings have been updated, reporting details for the data layer can be found in the following locations:
- Web Audits > Variables > Variable Summary > Data Layer
- Web Audits > Tags > Tag Summary > Data Layer
- Tag Reports > (All reports)
- Compliance Reports > Business Compliance (if set)
- [Steps] > Tags (tab)
The Future of the Data Layer
The data layer plays a key role that will not be going away anytime soon. As such, ObservePoint is already planning future updates to enhance the functionality to simplify and automate the setup and monitoring process. We look forward to sharing these updates with you in the not too distant future.
About the AuthorLinkedIn More Content by Dan Reno