About Me

IMG_8440-Edit-2 (1)I’m currently a Principal Analytics Engineer at Cognetik, but I’ve been consulting in some way since starting at Omniture in 2006. I had the pleasure of working at Search Discovery just before Satellite (now known as Dynamic Tag Management) was acquired by Adobe, but I actually made the switch to Adobe consulting just before that acquisition, putting me in a unique role as a consulting Subject Matter Expert for the Adobe consulting org. That experience with tag management and data layers has put me in quite a few unique positions to see some of the best (and worst) of how tag management and data layers are used.

I used to blog at Implementalytics.com from 2011 through 2013, and only recently resurrected that blog under a new domain. I will be posting new content around data layers (particularly the W3C standard), tag management, data visualization, Google Analytics, and Adobe Analytics, as the opportunity arises.
While I do work for Cognetik, the thoughts and ideas on this blog are completely my own.

Find me on linkedin or twitter.

5 thoughts on “About Me

  1. Hi,

    do you offer consulting services?
    I would like to get in touch regarding discrepancies between URL shortener and analytics tools.

    Best regards,
    Claudia

    1. Hi, Claudia. I’m afraid right now I’m not taking consulting projects outside of what I get through my employer, Adobe. If you’re an Adobe client, you may be able to get in touch with your account team and we can see if we can sync up that way.

  2. I will appreciate if you can advise on following.

    I have a single page application (called Insurance Proposal). This application is used by Agents.

    It has an awfully long page with separate sections which can be visited by clicking links/carousals or just by scrolling.

    Requirement is to measure “time spent on each sections of the page”.

    I am planning to track separate sections as page loads.

    If user visits the section by clicking links to each section, then it can be done easily.

    I need some suggestions from you for the case when user scrolls to the section. I am using “enters viewport” event (and then fire page load – s.t).

    It works fine for the first time, but if you visit the same section again by scrolling up or down, “enters viewport” does not trigger.

    What am I doing wrong?

    Since it is our test URL, you may not be able to access it.

    1. Hello, Sameer! “enters viewport” is only going to fire once for when the conditions of the rule are met- so if you’ve firing it when “div.article” enters viewport, once “div.article” has entered the viewport once, DTM kinda checks that off as having been viewed, and won’t fire the rule more on that DOM. In some cases, this is really handy and prevents inflated data, but in your case when you have multiple separate elements you want to track, it is working against you.
      IF you have a data layer or some data element that is changing as the user scrolls down, you may be able to change your rule condition to “Data element changed” and have it fire every time the page name or site section name data element changes.

  3. Hello Jennifer,
    Thanks for replying my “enters viewport” question. I was able to do it by hosting a customized code in DTM. It is working fine.

    Regards

Leave a Reply

Your email address will not be published. Required fields are marked *