Exclude subdomain Google Analytics

[growcodile]

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

NA

What is the issue or error you’re encountering

How to Exclude the subdomain when using Google Analytics with zaraz

[fritex]

@growcodile

How to Exclude the subdomain when using Google Analytics with zaraz

You can prevent loading Zaraz on a sub-domain using Configuration Rules as well as follows on below screenshot example.

Step 1 - Navigate to Rules tab from Cloudflare dashboard → https://dash.cloudflare.com/?to=/:account/:zone/rules/overview and click on the blue button " + Create Rule":

Step 2 - Select “Products” tab from the top then find the box “Configuration Rules” and click on the “Create a Rule”:

Step 3 - Select Hostname equals sub.example.com (replace with your sub-domain), scroll down and find Zaraz and click “+ Add” to Disable it:

Step 4 - Click on the blue “Deploy” button to save and apply.

Helpful article:

Create a configuration rule in the dashboard · Cloudflare Rules docs

You could set a trigger as well using below:

Zaraz firing on pages/subdomains that I thought I excluded

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.

Different scripts for each subdomain

You could add multiple conditions to any trigger with an AND operator between them, and do another match rule this time on {{ system.page.url.pathname }} and select not matches regex as your operation with a match string such as: ^/wp-(admin|login.php)

Other way, using Page Rules:

Different scripts for each subdomain

Adding to what Simon said, you can also block Zaraz (together with all tools loaded by it) on specific page using Page Rules: Load Zaraz selectively · Cloudflare Zaraz docs