In the words of Matthew Mcconaughey, "Alright, Alright, Alright!" Don't know what I was doing wrong the first time around, but it's working now. I had to modify the regexp a bit so that I could match the home page with or without query string arguments. The pattern I ended up with is: ^[/]?[?]?[^/?]*$Thank you much! I'm so glad to have a good solution for this. -Stew

Hi Joel, I'm still not getting it to work. Have you tried this yourself and proven it to work? If I understand your suggestion, you are saying that I should be able to create a PATH condition as INCLUDE ^\/?$ with regexp turned on to detect the homepage of the website. Thanks,-Stew

Joel Stachowicz wrote... Hi Stewart, Using regex is probably the way to go, but this use case is a bit more complex than it may first appear. For instance, the match probably needs to take into account situations like variations in protocol (http vs https), the actual homepage file name (index.jsp), query params (?var1=1&var2=1), etc. in addition to simply excluding alternate filenames like /page.html at the end of the path. A simple match would be ^(https?:\/\/)?www.landsend.com\/?$ Use the reg...

Thanks for the response, but it doesn't seem to work. Have you tried it on your end? I put in exactly what you suggested and the rule still fires on every page that begins with "http://www.landsend.com/"I've tried a great number of regular expressions to no avail. I might add that within DTM the little regex tester indicates that your solution should work, but in application it does not. Thus my question.

MYOHMYOHMYMOTECH !!! This is the exact issue that I was having. Thank you for the answer!Yes, by dumping the old 3rd party floodlight tag into a Non-Sequential HTML container my problem was solved.