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

Sessions Across Domains & Cookie Migration - Coremetrics and Google Analytics

When visitor hops from one domain to another the session connectivity is lost, in order to retain the session continuity line of tracking code have to be added to the site pages, in addition to the usual web analytics tracking code.

In this post I have compared the lines of code that need to be included in  the master code of web analytics tools such as Coremetrics and Google analytics.

Here is how you need to do it in Google Analytics

Scenario: You send visitors from Site A to Site B in order to complete a purchase. Since GA uses first party cookies, wherein the same domain sets the cookies than a different domain, it is hard to find out if the same visitors has completed the purchase on Site B. This is simply because site A cannot set cookies for Site B, and the latter domain need to do it to get deemed as first party cookies.

Solution: This is where _link () comes handy and enables the Site B to set the cookies, and the session gets continued for visitors moving from Site A to Site B without any turbulence, and tracking happens in a best possible way.

Here is the necessary lines of tracking codes to keep the session moving from A to B.

 Here is how you need to do it in Coremetrics

Scenario: Same as mentioned in the GA, you have to extend the sessions between two websites to track the path of visitors A and identify if visitor A has made a purchase / not in the second website. CM uses first-party cookies, and again the cookies have to be set by the same domain and not by any other websites.

Solution: In Coremetrics cmSetupCookieMigration () does the trick in capturing the visitor activities from site A to site B (checkout-store.com).


Note in both the tools: CM and GA, the codes need to be added in both the websites along with the client Id / Urchin account number.

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?