Consent, the EU banner, and what Vibel sends without it
In regions where consent is required, a shopper's choice changes what the Vibel pixel is allowed to send, and a decline is a real, permanent loss no tracking setup recovers.
The short answer
Where consent is legally required, the Vibel pixel checks the shopper's consent choice before it sends analytics data, exactly the way it checks before sending anything to an ad platform. A decline is honoured: it is not a bug to engineer around, it is the shopper's actual choice.
What a decline costs you, honestly
A declined visitor's session genuinely does not reach Meta, Google or any other platform, and the pixel's own coverage figure on Events reflects that as a real gap rather than hiding it. This is why coverage never reaches 100 percent even on a perfectly installed pixel: consent declines and in-app browsers are real, permanent losses.
This is also one of the standard explanations when Meta reports fewer conversions than you actually had, see the Meta-vs-Shopify guide for the full list of causes.
The banner itself
The consent banner shown to EU visitors is a theme-level concern, configured on the storefront, not inside Vibel's settings. Vibel reads whatever consent state the storefront's own banner records and respects it; it does not set the banner's wording or design.
- If you run your own consent management platform already, the Vibel pixel reads that signal rather than requiring a second, competing banner.
More in Advertising
Run your store on Vibel.
Connect your channels, set up your costs, and see true profit live per SKU and per channel.
Get started free