THIS ARTICLE WILL HELP YOU:
Data Layer Definition
A Data Layer is a data structure that ideally holds all data that you want to process and pass from your website to other applications that you have linked to.
A very common example is web analytics tracking. You might have a Data Layer that feeds data about the visitor into your analytics tool. Often, this data isn’t available in the presentational layer or in the markup at all. This data might be, for example, details about the visitor (login status, user ID, geolocation), metadata about the page (optimal resolution, image copyrights), or even information that’s already in the markup but that you want to access in a more robust way.
Therefore, you can use this Data Layer to store session visitor data and present later a specific experience to a specific visitor group.
Data Layer Structure
A classic Data Layer would look like the following and would be embedded in your page:
dataLayer = [{
isLoggedIn: 0,
userEmail: 'any@test.com',
industry: 'medical'
}];
Let's assume that the industry field can have different values, and we want to target with our experience only users in the medical industry.
Steps
First, we need to create the experience that we want to show to this audience group. We need to configure an Advanced Audience for this experience.
Select Audience:
Then select "Create an advanced goal" and under Page Tags, select JS condition:
Enter the following JS code:
(function() {
if (typeof window.dataLayer === 'undefined') {
console.log('dataLayer not found');
convert_recheck_experiment();
return false;
}
if (Array.isArray(window.dataLayer)) {
for (var i = 0; i < window.dataLayer.length; i++) {
var data = window.dataLayer[i];
if (data.industry && data.industry === 'medical') {
return true;
}
}
}
convert_recheck_experiment();
return false;
})();
Then, the experience will only run for those visitors whose industry value of the Data Layer equals medical.
A similar type of targeting can be achieved if the dataLayer holds page data. Then, the JS Condition would be placed on the experience Location instead.