Tealium Learning Center

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. All Site Pages: Domain > contains (ignore case) > www.mysite.com We then took the two pathname exclusions and established these as independent Load Rules. Exclude Homepage: Pathname > equals > / Exclude Thank you page: Pathname > contains (ignore case) > /thank-you 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. ... View more