Before you start: this is not legal advice
The GDPR (RGPD in Spain) and Spanish cookie regulations determine what you must disclose, how to ask for consent and what text you need in your privacy and cookie policies. That part depends on your business, the tools you use and how you process data, and it should be reviewed by a legal advisor.
What we can explain is how Shopify works under the hood: which tools it includes, how they connect to pixels and apps and which technical mistakes cause a store to load cookies too early even when it has a banner.
The Customer Privacy API
The Customer Privacy API is the interface that stores and checks each visitor's consent preferences. The native banner uses it under the hood, and third-party consent management apps integrate with it so Shopify knows what the customer has accepted.
If the theme or a custom section loads a third-party script, that code has to check the API before running and listen for consent changes. This is where stores fail most often: the banner exists, but a script pasted into theme.liquid loads anyway before the visitor decides.
The fix is to route all third-party code through the consent system: ideally as a custom pixel in customer events, with its permissions configured, and only if that is not possible, from the theme by checking the API. That gives you a single point of control and makes it easier to audit what loads and when.
Pixels, permissions and Google's consent mode
In customer events, each custom pixel has a permissions setting where you specify which consent categories it needs, such as analytics, marketing or preferences. If the visitor has not accepted those categories, the pixel receives no events. Configure this for every pixel instead of leaving it as not required.
For Google tools, the Google & YouTube app passes the consent status through Google's consent mode, so GA4 and Google Ads adjust their behavior based on what was accepted. If you load Google with your own code, you will have to implement that signal yourself.
Third-party consent apps
The native banner covers the basics. Some stores need more: a detailed consent log, automatic cookie scanning, tightly controlled copy per language or integration with a corporate consent platform. In those cases you use an app that integrates with the Customer Privacy API.
Choose one that explicitly states that integration and turn off the native banner so you do not show two. Then check that pixels respond to the app's consent the same way they do with the Shopify banner.
How to check that it works
Open the store in a private window with the browser's developer tools and reject all optional cookies. Check which cookies are set and which requests go out to Google, Meta or other domains. Then repeat the test accepting them and compare. If something loads before the visitor decides, track down its source in the theme or the apps.
Repeat the check every time you install an app or add a script. At Weblineo we build themes so that every third-party script respects consent at the code level, and we leave the legal setup in the hands of your advisor.
Frequently asked questions
Is Shopify's cookie banner enough to comply with the GDPR?
Technically it blocks the pixels connected to the consent system, but compliance also depends on your copy, your cookie policy and the rest of your scripts. Validate it with a legal advisor.
Does Shopify checkout respect consent?
Pixels that run in checkout do so through customer events, which respect the consent permissions configured for each pixel.
Can I use a cookie app I already use on other websites?
Yes, if it integrates with Shopify's Customer Privacy API. If it does not, Shopify will not know what the visitor has accepted and pixels will not be blocked correctly.
Who writes the cookie policy?
A legal advisor, based on the technical inventory of cookies and tools you use. Generic templates do not reflect the specific tools in your store.
