Description -More and more website are being built using Single-Page Application (SPA) architecture. With a SPA website, when a user moves between screens it does not cause a full refresh of the page. This causes Data Elements that have a Storage Duration set to "page view" to live beyond what the user experiences as a page view as these data elements require a full refresh from them to be cleared. Why is this important -Within SPAs, data elements set to "page view" duration can actually live fo...

False alerts are bad news. Apart from being very annoying, they can cause you to lose trust in your alerts, leading you to ignore real problems. Out of the box Adobe does not offer a way to turn off hourly alerts overnight. This can lead to false alerts being sent as volumes drop and the data becomes more volatile. However, there is an easy method to disable hourly alerts during specific hours... Imagine a scenario where you wanted to create an alert when 'orders' are below or equal to 1000, but...

Variables in Adobe Analytics are limited in length so losing data because we are exceeding these limits is something we all need to keep in mind. This can happen when we combine several values into a variable for future classification and we don't realise that certain combinations create a very long string. Fortunately, there is a simple method to proactively detect when this happens, allowing you to identify and deal with cases where values are being truncated. And the simple method is... ...ad...

A common (and incredibly useful!) technique in Adobe Analytics is to concatenate multiple values into a variable and then use the classification rule builder to split these values back out in to separate classifications. This is fantastic way to save on the number of variables being used as we all know we have a limited number of props and eVars available! What I hope to show you in this blog post is a method to make this process of concatenating and splitting out values more robust and faster t...

Description -At the moment rules are triggered in a sequence determined by the rule order number. However, each rule executes asynchronously meaning that rules with a higher priority may finish after rules with a lower priority. This can cause issues where there is a dependency between rules. Why is this feature important to you -We are experiencing issues where there are dependencies between rules. They are hard to spot because the are intermittent and are difficult to resolve due the the async...