Session Storage elements persist for as long as a current tab is open. A session for Launch is not the same as for, for example, your analytics system.But there are a number of things to keep in mind when using the “once every x sessions” logic because it is based on the Session Storage: If it doesn’t exist, Launch assumes a new session has started and increments the number of sessions. It does that by looking for the landingPage key in the Session Storage (had to learn that myself by looking at the source code of the extension). When Launch loads, it tries to figure out if a new session has just begun. There is quite a bit of information about the session here. Hunting for session information in Adobe Launch Quite elegant!īut wait a minute! You may call me pedantic, but I know the rule id of each and every rule I have ever created (don’t challenge me on that, just believe me), and that one in the screenshot ain’t it! And even worse: When I change the name of the rule in Launch, push the changes live, and click on the page again, there now is a second Local Storage value: That way we can also cover cases like “every 3 page views”, by simply shifting the count a bit. If the persisted value is lower or not existent, the rule is good to run. That pages viewed counter is incremented, you guessed it, on page load. So when the condition is evaluated, Launch checks the persisted value that belongs to the rule that should execute and, if it exists, compares its value to the number of pages viewed. The key includes something that looks like the id of a Launch rule, and the value equals the pagesViewed key we saw before. Interesting! Now we have one more key in our Local Storage with a very peculiar name (again, have fun with that privacy notice). Launch’s local storage after our condition executed In Launch, I created this simple rule that, on every click, shows an alert message to show the rule just ran: So, let’s start! The test setupįirst, we need a very simple rule that we can use for testing. In the end your data might end up being less reliable than you might think.īecause of this situation and my own experiences debugging those discrepancies, I wanted to create this post to look at what Launch has built in already, find out how it works under the hood, and give recommendations on which approach should be used in which situation. On top of those varying definitions of once, Adobe Launch has some matching functionality built-in which is rarely completely understood by the end users. What once really means (once per session, user, day, year?) might differ from tag to tag, so as a result it can be surprisingly difficult to fulfill those requirements reliably and consistently. While Launch is great for making implementation of Adobe’s own tools very fast and easy, managing other tools is not always so straight forward.Ī common requirement for those 3rd Party tags is to fire a certain tag or pixel only once. I will still call it Launch for the near future) to implement other tags as well. When you are managing an implementation of Adobe tools like Analytics, chances are you are using Adobe Experience Platform Data Collection, formerly known as Adobe Launch, Adobe Dynamic Tag Management, or the Adobe Tag Manager (and no, this is not a SEO text, it’s the actual list of names.
0 Comments
Leave a Reply. |