Using a contains filter should take care of this, no?
On a technical level, one annoyance with hashtags -- and I use them happily in my projects -- is that once one is set, it can end up suffixing all the user's URLs even when they're not on a page that uses/needs them.
If you want to strip the hashtag, you could add a tiny line of JS on any page that isn't using hashes and might be ultra-sensitive to them:
if ( document.location.hash ) document.location.replace( document.location.pathname + document.location.search );
Thanks for the hash suggestion Sanford! I will take a look at it as an option. As for the trigger operand, I wanted to try contains but when webpage is used as a condition for the trigger it only gives you is or is not as options. I suppose I could remove the filter as a condition and try layering it on as a separate filter. Will definitely check out if there is a workaround that way.