To help you balance global privacy regulations with a high-converting user experience, we have updated how the Wishlist interaction handles GDPR consent. This "just-in-time" approach ensures your wishlist remains accessible while staying compliant with data privacy laws.
Overview
Previously, if a user in a GDPR-regulated region had not accepted cookies via your site’s main consent banner, the Wishlist button might have been hidden or non-functional.
With this update, the Wishlist button on the PDP is now consistently visible to all users. Instead of asking for permission upfront for the entire site, we evaluate consent at the exact moment a user tries to add an item to their wishlist. This reduces friction and ensures that only interested users are prompted for data permission.
Note: This contextual flow is gated on the shopper's real-time consent status with Shopify, not on a region name or a fixed "banner required" setting. The prompt appears for shoppers whose consent status isn't already granted — in practice this most often means shoppers in opt-in consent regions such as the EU/EEA and UK who haven't yet made a choice. Whether it appears for a shopper elsewhere, including in the US, depends on your store's specific Customer Privacy configuration and that shopper's own consent status, not their region by itself.
How the Flow Works
The new consent logic follows a specific "if/then" sequence based on the user's current status:
1. Consistent Visibility
The "Add to Wishlist" button appears on all Advanced Product Detail Pages (PDP). This ensures that the UI remains stable and professional for every visitor, regardless of whether they have interacted with your primary cookie banner.
2. Interaction-Based Evaluation
When a user clicks the Wishlist button, the system performs a real-time check:
If Consent is Already Present: If the user previously accepted cookies via your main site banner, the item is added instantly. The button state updates (e.g., the heart fills in) with no interruption.
If Consent is Missing: A contextual modal pops up immediately near the Wishlist button. This modal explains that consent is required to save items to their list.
3. User Choices within the Modal
Accept: The consent is recorded, the item is successfully added to the wishlist, and the button updates to the "active" state.
Decline: No wishlist action is taken, and no data is stored. The button remains in its original state.
User Control: Declining does not "lock" the feature. If the user changes their mind and clicks the button again later, the prompt will reappear, giving them another opportunity to opt-in.
Relationship with Your Main Cookie Banner
This feature is designed to work in tandem with your existing site-wide consent management platform (CMP).
If a user accepts cookies on your main banner, they will never see this wishlist-specific prompt.
This prompt acts as a "fallback" to ensure that users who skipped the initial banner can still use the Wishlist feature legally and easily without having to find and reset their global cookie settings.
How This Differs from Privacy-First Wishlist
Swym also offers a separate feature called Privacy-First Wishlist, which can show a similarly-styled prompt. The two are not the same mechanism, and they behave differently if a shopper declines:
With this feature (Contextual GDPR Consent): declining means no wishlist action is taken and no data is stored anywhere, including on the shopper's own device.
With Privacy-First Wishlist, where enabled: declining this feature's prompt does not activate Privacy-First Wishlist's device-only saving. The two mechanisms don't hand off to each other.
If your store has both features active on the same wishlist button, contact Swym support to confirm exactly which prompt a shopper will see and what happens if they decline it, since this depends on your specific configuration.
Current Scope & Future Rollout
This contextual consent flow is active on:
Advanced Product Detail Page (PDP) Wishlist Buttons
Header Wishlist Icon
Advanced Collections Wishlist Buttons
All three surfaces are covered today. There is no further rollout pending for this feature.
Using a custom wishlist implementation instead of one of these three surfaces? This contextual flow doesn't apply to it automatically. See "How Wishlist Plus Handles Cookies and Cookie Consent" for what a custom implementation means for your options, or contact Swym support directly.
Frequently Asked Questions
Will this affect my site's loading speed?
No. The consent check happens only upon a user's click, meaning there is zero impact on your initial page load performance.
Does this mean I don't need a main cookie banner?
No. This feature ensures your Wishlist is compliant, but you should still maintain a primary cookie banner to cover other site-wide tracking, analytics, and marketing pixels.
Is this visible to US-based customers?
It can be — this prompt is gated on the shopper's real-time consent status with Shopify, not their region by itself. Whether a specific US-based shopper sees it depends on your store's Customer Privacy configuration and that shopper's own consent status, the same as it does in any other region.