Exploring Rule Conditions In Adobe Launch
Adobe Launch is pretty powerful in terms of capabilities. When it comes to applying conditionally firing rules in Adobe Launch, there are a lot of helpful options out there. This post doesn’t go through all of them but rather some of the interesting ones.
With any of the rule, you have the logic type Regular and Exception. Regular would mean RULE AND Condition is met. Exception would mean RULE AND condition NOT met.
Landing page: This one is a helpful rule condition option to have. You could use this to fire tags on campaign specific landing pages. It’s also regex controlled so you could fire it on a set of pages via “|” operator. Google Tag Manager doesn’t specifically have this trigger but you could make it via using the Referrer does not contain your own domain [so that it excludes all internal hits] AND put in your page URL matches Regex.
Variable and Value Comparison: I’ve already covered this here. > Value comparison vs Variable condition in Rules:. TL;DR; = Variable, you would enter the JS value location directly whereas in Value comparison, you can reference a data element.
New vs Returning User: This is handy one to have. AFAIK, in GTM, you’d have to manage this by placing a user cookie at the visitor’s side and then read the cookie value [as TRUE/FALSE] for New vs Returning Visitor to be able to fire this in GTM.
Page Views / Sessions: Page Views gives you the option of > , = or < than x number of page views per session or lifetime. With Sessions, it’s number of sessions [at a user level] are > X.
Max Frequency: This is very powerful as you can use the X times every page view / sessions to manage funnel drops where users move back and forth between pages. There are also options to fire it after checking time based conditions.
Operating System: AFAIK, this would be using the JS to get the operating system. Here’s a Stackoverflow thread on it. https://stackoverflow.com/questions/9514179/how-to-find-the-operating-system-version-using-javascript .
IF you had to do this in GTM , you’d create a JS variable called “navigator.platform” and it should return the OS. I tried a test here on my blog and it’s showing “Win32”
So, what’s the full list of possible values for navigator.platform? If you check this Stack Overflow thread, https://stackoverflow.com/questions/19877924/what-is-the-list-of-possible-values-for-navigator-platform-as-of-today it does make sense. My OS showed as Win32 even though I’m on Win64. This is a known error with navigator.platform values as per the thread. At best, you should just use regex to identify “win” and not the bit.
That’s it for this one. How are you using Conditions feature in Rules to make the most out of it?
