- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
12-05-2022 07:55 AM - edited 12-05-2022 09:14 AM
We have , what should be, a seemingly streight forward request. Add a tag to All Site Pages but exclude our site homepage ( / ), and submission confirmation page ( /thank-you ).
Given this scenerio is somewhat common for us we've chosen to leverage a load rule for this situation. We initially tried a single Load Rule that contained both conditions.
Domain - contains (ignore case) - mydomain.com and Pathname - does not equal - /
Domain - contains (ignore case) - mydomain.com and Pathname - does not equal (ignore case) - /thank-you
This rule was not recognized on either the homepage or the /thank-you page. We then seperated these conditions putting each in it's own Load Rule and applied to the relevant tag under the "Match Any" condition. Still no success.
However, if only one of these independent load rules is applied, they both function correctly.
We have tried Load Rule configurations that include the (ignore care) condition, as well as, without this condition. We've also used the "contains" and "contains (ignore case) condition on the /thank-you page Load Rule. Independently these work, but not in combination with both rules running.
This situation feels like, once we see a working solution, we're going to slap our forehead. Any tips would be welcome.
12-13-2022 10:32 PM
12-14-2022 07:05 PM
Hi there @aaqib
We were able to address this issue leveraging a slightly different approach. We removed all "exclusion" based conditions from the Load Rule in question, leaving only the rule we had in place for the trigger based on the site domain; i.e.
We then took the two pathname exclusions and established these as independent Load Rules.
Then in the tag itself we selected all 3 Load Rules under the Match All condition.
After considering this approach, I am beginning to like it more and more. What I mean by this is, by setting up the exclusions on their own, we're not establishing single use Load Rule whose use case is so specific that it can't be used beyond the initial request that had us establish it in the first place. We've seen this approach snowball into terribly messy set-ups.
I do see the rational for first checking if the domain "exists" before evaluating. I had wondered if the issue we were observing was due to timing given we have the very configuration we were attempting to create established and functioning in a different profile. Sometimes it's difficult to see the forest through the trees.
Thank you for jumping on with a suggestion. We definitely appreciate the insight.
Copyright All Rights Reserved © 2008-2023