How regional pixel blocking works in LinkStack
Understand where LinkStack blocks third-party pixels and how routing continues.
4 min read
In this article
Where blocking applies
LinkStack blocks configured tracking pixels for visitors detected in the European Union, European Economic Area, United Kingdom, and Switzerland.
Current behavior
- The restriction applies to saved provider pixels and legacy pixel fields.
- There is no per-link or per-pixel switch that can enable delivery in those regions.
- Pixels stay blocked in these regions.
- The Link still routes the visitor; the third-party pixel is the part that stays blocked.

What to expect in reporting
- LinkStack click analytics can include traffic that a provider pixel does not receive.
- Provider audiences and visit totals can therefore be lower than Link clicks.
- Do not use a restricted-region test as proof that a saved Pixel ID is broken.
- Destination-site tracking remains separate and must follow that site's own consent and privacy setup.
Related articles
Still need help?
Support & feedback