When using Custom Script in a Rule Condition, you need to return (boolean) true when you want the Rule to fire. Try this:var myH1 = document.getElementsByClassName("hero-title")[0].innerHTML.toString(); if (myH1 == "The information you are trying to access has moved." ) { return true; }

yes, this issue was fixed/released at the end of february -- now i have a new issue, with the speed 😕

Hi Mike, That does allow the rule to fire, but doesn't afford us the flexibility we need to write one rule for both the dev and prod environments. We're trying to format a global rule for all pages on the site. Maybe I need to re-work the regex for the path statement.Thanks!

Good request! It's still early in the beta, and we're adding features quickly. We'll keep an eye on this post for "hearts" and comments.

Great catch. We'll get this one fixed. 

I managed to find it by clicking the hamburger menu (top left), then look in Components. You can get to the other manage screens (segments, dashboards, etc) from there too.

First, I'd make sure the rule is even firing (DTM Switch plugin is useful here).If you are defining props/evars in the custom code area, you need to use s. in front of them (like s.eVar2).