Event Driven Data Layer Implementation using ACDL/GTM - Create Own EDDL Strategy

Data Layer is a known concept for most in digital analytics. As the name suggests it is all about data residing in the layer of the pages. Data can be about useful information of your properties when the user interacts using which analytics and marketing folks understand the likes and wants of users to create an enriching experience for the users. Capturing the data useful for your properties is the foundation to begin knowing anything about your users preferences to provide compelling user experiences that flourish your business. Designing a robust data layer should the number one priority to take the right path to success. Most of us have heard about Customer Experience Digital Data Layer layer by W3C and would have worked on designing data layer to collect data footprints of the users.  One of the main challenges in tracking in SPA / regular pages is users moving to next page or bouncing off the pages. Tracking Interactions happening on a page without the need to refresh the page ne

How to get the Page URL Report (Not Available by Default) in SiteCatalyst using DTM / s_code / Processing Rules

Nowadays you don’t see the page URL report by default in SiteCatalyst, your search for this readymade report will end in vain with just OOB (Out of the Box) configuration.

However small changes to the implementation can do wonders to bring back this data in SiteCatalyst as this value is already available in SC data warehouse and data feeds. The page URL is being fired up for all SC implemented sites but since there is no placeholder to take in value in SiteCatalyst this is not reported as a dimension.

Here is a way to check and confirm that the page URL is getting fired up…go to adobe.com> open the chrome debugger > go to the network tab > type /ss/ > click on the image request and then look for the value for g:….you will get to see the value as http://www.adobe.com… It will be similar to the below screenshot.

Now g is the variable which hold the page URL value. In order to get this information in SiteCatalyst the value need to be stripped and passed to any other custom variable you would want to assign this value. Now here is how you can do via DTM, through s_code and via Processing rules.

Method 1: Implementation via DTM
If your implementation uses Adobe's Dynamic Tag Manager, you can easily follow these steps:
  1. Log in to dtm.adobe.com and click the desired web property.
  2. Click the icon next to the Analytics tool.
  3. Under global variables, find an unused eVar and set it to D=gD= is Adobe's dynamic variable operator, and g is indicative of page URL.
  4. Save and deploy settings.

Method 2: Implementation using s_code
If your organization is not using DTM, you can assign the variable value within your core JavaScript file:
  1. Open your s_code.js file.
  2. Within the doPlugins() function, add a line containing this code, replacing XX with the desired eVar:
  3. Save the file and upload to your site.

Method 3: Using Processing Rules
If you are authorized to use Processing Rules, you can use them to automatically populate a variable with page URL:
  1. Log in to Adobe Analytics and go to Star Menu | Admin Tools | Report Suites
  2. Select the correct report suite, and go to  Edit Settings | General | Processing Rules
  3. Click Add Rule, and create the following rule (Always Execute):
    Overwrite value of [desired eVar] with page_url
  4. Click Save.

Now you know how can you easily get the URL data in SiteCatalyst using any of the above methods!

Popular posts from this blog

As the testing industry grows and matures, more testers will likely:

Learn Adobe Analytics Marketing Reports & Analytics (SiteCatalyst) : Free Self Implementation Kit for Study

Measuring conversion rates on “thank you” pages provides?