Hey @tyrese  are you then also returning the result of the function? Or how exactly do you want to make it usable?   Note that - to my knowledge, and different to GTM - you cannot define a function in one data element and then call it from another. So, something like this is not possible _satellite....

Hi @tyrese , can you provide a concrete example of what you want to achieve and what you have unsuccessfully tried yet?You can of course write your own custom function in a data element, call it and return the result function foo(){ return "bar"; } return foo();  

Hi @_Paul_S your assumptions are correct. To recap from what I hear you have different Launch properties. So yes, you can "white list" the report suites on your datastream that you allow to be used in the override, and the set the override in the Web SDK extension configurationthe override does not ...

HI @icontre1  best would be if you paste a screenshot of your processing rule here, and maybe as well as test URL of yours.

Hi @Esakkidevi    Assuming that your core click rule is attached to buttons, you may want to have a look at Jim Gordon's cheat sheet https://jimalytics.com/wp-content/uploads/2017/11/Adobe-Launch-Cheat-Sheet.pdf   In your eVar4, you can then just use the percent placeholder syntax e.g.,  %this.@clea...

Hi @SivaramM  you could use the Perpetua Assistant to search for "core::conditions::date-range" https://assistant.perpetua.digital/    Will require API access though, but should give you a quick overview (even though you will have to open the items manually)  

Hi @Paul1982  I would assume a sequential segment like this should work. This should be applicable to any date range, not just per year          

Phew, regexes will never be fun to look at!   Well, since javascript regexes don't support if/else conditions, maybe this post is helpful https://stackoverflow.com/questions/32852857/javascript-conditional-regular-expression-if-then-else Stupid question: have you talked to a dev to fix this on the w...

Hi @AWalsh1  no, bot rules are not working retroactively. For what it's worth, here's a documentation that covers the processing order in Adobe Analytics

Hi @HảoHo  can you please add a little more context like what do you want to achieve?what have you tried so far?which documentation are you referring to?