After configuring your pixel, you may receive an email notification or see a “New Domain Sending Data” alert in the Diagnostics tab of Events Manager. You might then notice traffic from domains unrelated to your business, which can also trigger event registrations.
This happens for 2 reasons:
-
Because your pixel ID is public, anyone can access and use it on their own domains after you install the code on your website.
-
Another reason for unfamiliar domains sending data is the use of third-party integrations or iframes when installing the pixel. These can create redirects to your website, which appear as referring URLs from unknown domains.
To better control these redirects, consider the following best practices recommended by Facebook:
-
When using third-party integrations or iframes to install your pixel, allow both your business domain and the third-party integration to send data to your website.
-
Use allow lists to automatically block traffic from unwanted sources. These lists block any domain not included. You can add or remove sites at any time, but events lost while a domain was blocked cannot be recovered.
-
You can switch from a block list to an allow list at any time. When you do, domains on your block list are removed, and only your allow list will apply.
-
Set up a block list if you want to automatically receive events from your pixel when it is installed on a new domain.
-
When you add a top-level domain, all its subdomains are included in the list, so you do not need to add them individually. For example, adding "domain.com" also includes "m.domain.com". If you want to exclude specific subdomains, add them manually instead of the top-level domain.
