LinkStack
Back to Help Center

Retargeting and Pixels

How regional pixel blocking works in LinkStack

Understand where LinkStack blocks third-party pixels and why there is no consent override yet.

Updated Jul 26, 20264 min read

Table of contents

Where blocking appliesCurrent behaviorWhat to expect in reporting

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.
  • Consent-enabled pixel delivery is not available yet.
  • The Smart 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 Smart 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

How to configure and assign tracking pixelsSmart LinksHow to test Smart Link pixels without inventing conversionsRetargeting and PixelsHow to set up TikTok and other Smart Link pixelsRetargeting and Pixels

Still need help?

Tell us what you are trying to do and where you got stuck.

Contact support
How regional pixel blocking works in LinkStack | LinkStack Help | LinkStack.fyi