Zaraz firing on pages/subdomains that I thought I excluded

[josh29]

For Workes & Pages, what is the name of the domain?

N/A

What is the error number?

N/A

What is the error message?

N/A

What is the issue or error you’re encountering

Zaraz triggers when I think it shouldn’t

What steps have you taken to resolve the issue?

I’ve tried multiple patterns, firing triggers, and blocking triggers.

What are the steps to reproduce the issue?

I am using the attached settings as a firing trigger.

I expect the 1st rule to restrict the match to the exact domain, excluding subdomains. I expect the 2nd rule to exclude any path with “wp-admin”.

But Zaraz fires on subdomains and on “wp-admin” pages.

I’m using Zaraz to add GA4. GA4 has 2 other actions which are disabled.

I’m out of ideas. What should I try next to troubleshoot this?

Screenshot of the error

[yoav_zaraz]

have you tried using the Zaraz Debugger? it will show exactly how Zaraz evaluated your rules.

however, I recommend trying different trigger: create a firing trigger that fires for your domain (use “starts with”, or “contains”, not a regex). then create another trigger that matches url starting with or containing “wp-admin”. use this one as a blocking trigger for your actions/tool.

[josh29]

Thanks for the tip on the debugger. I didn’t know that existed.

As for the other configuration, that’s how I did it at first.

[josh29]

That debugger is priceless. Thanks again for mentioning it.

[yoav_zaraz]

Great to hear! We’re planning on giving it a few improvements, let me know if there are things you wished it did better.