The domain filter

Each domain in an installation runs through a domain filter. The filter makes sure Metrion only forwards data from the website you actually want to track on this installation.

Why it exists
When the Metrion plugin is installed on a shop, it can pick up traffic from the main domain and any subdomains attached to it — including staging environments, preview environments, or unrelated subsites you don’t want sending data to your live ad accounts.

The domain filter solves this. For each domain you’ve added, Metrion only includes events that match that filter when forwarding conversions through a Sync. Anything outside the filter is ignored.

How it works in practice
If you add https://example.com to an installation, Metrion’s filter will accept conversions from example.com. Subdomains like staging.example.com or preview.example.com are kept out of the live data flow unless you explicitly add them as their own domains.

This keeps test data, internal traffic, and unrelated subdomain traffic out of your ad platforms — and keeps your destinations optimising on real customer behaviour only.

Where to see it
Each domain row in the Domains section of an installation shows the “Active domain filter” label, confirming the filter is in place. There’s no extra configuration needed — adding a domain enables its filter automatically.