Consentmo - Swym Integration
Swym Cookies Integration
If you are using Swym Wishlist Plus on your Shopify store, you may notice cookies and browser storage entries related to Swym detected by the Consentmo scanner.
Swym Wishlist Plus uses browser-based storage to support wishlist functionality, such as remembering an anonymous visitor’s wishlist, recognizing whether a shopper is logged in, and storing contact details provided by the shopper for wishlist-related alerts.
Swym’s cookies generally start with:
swym-This guide explains how Swym cookies can be categorized in Consentmo and what to keep in mind when Swym’s cookie consent options are enabled.
How Swym works with cookie consent
Swym Wishlist Plus is designed to work alongside Shopify’s Customer Privacy API and consent management platforms such as Consentmo.
When a cookie banner is required for the shopper’s region, Swym relies on the consent status before allowing its standard cookie-based wishlist functionality to operate.
If the shopper gives consent, Wishlist Plus can work normally.
If the shopper declines consent, the behavior depends on the type of Swym wishlist button used by the store and whether Swym’s optional Privacy-First Wishlist mode is enabled.
Consentmo continues to manage the store’s cookie banner, consent categories, and cookie/tracking preferences. Swym handles how Wishlist Plus behaves when consent has not been granted or when cookies are declined.
Swym cookie classifications
Swym’s current cookie classification table includes Necessary, Functional, and Marketing cookies.
These cookies can be added to the matching categories in the Consentmo app.
Necessary cookies
These cookies are used to support the basic operation of Wishlist Plus.
Cookie | Purpose | Duration | Category |
|---|---|---|---|
| Identifies the store to Swym’s backend systems. | Up to 365 days | Necessary |
| Anonymous visitor identifier used to keep a guest shopper’s wishlist across visits in the same browser, without requiring login. | Up to 365 days | Necessary |
| Tracks the shopper’s current browsing session. | 30 minutes | Necessary |
| Caches whether the store has multi-market functionality enabled for the current session. | 30 minutes | Necessary |
| Internal record used to avoid repeating a one-time account-authentication cleanup step. | Up to 365 days | Necessary |
Functional cookies
These cookies support wishlist preferences, alerts, login-related flows, cart-related features, and similar functionality.
Cookie | Purpose | Duration | Category |
|---|---|---|---|
| Stores an email address provided by the shopper for Save-for-Later or watchlist features. | Up to 365 days, unless the shopper logs out or disconnects manually | Functional |
| Stores an email address specifically tied to watchlist alerts. | Up to 365 days | Functional |
| Records the state of a cart action for a specific product. | Up to 365 days | Functional |
| Stores a confirmed phone number for back-in-stock text message alerts. | Up to 365 days | Functional |
| Records when to show the shopper a permission prompt again, so they are not asked repeatedly. | Up to 365 days | Functional |
| Stores saved wishlist and notification preferences. | Up to 365 days | Functional |
| Tracks whether a passwordless login request is pending, completed, or should be cleared. | Up to 365 days | Functional |
| Internal record used to avoid duplicate identity-detection calls. | Up to 365 days | Functional |
| Tracks the last-synced shopping cart token, only if the optional cart-attribute-sync feature is enabled. | 30 minutes | Functional |
| Internal record preventing an order confirmation from being reported more than once. | 30 minutes | Functional |
| Remembers which page to return the shopper to after login is required. | 30 minutes | Functional |
| Short-lived internal marker used after a passwordless login request. | 30 minutes | Functional |
| Records that the shopper added an item to their wishlist during the current browsing session. | 30 minutes | Functional |
| Internal record ensuring a technical mismatch is only reported once per session. | 30 minutes | Functional |
| Internal record ensuring a software version check only runs once per session. | 30 minutes | Functional |
| Counts repeated technical errors related to a visitor identifier to decide when it should be reset. | 30 minutes | Functional |
Marketing cookies
Cookie | Purpose | Duration | Category |
|---|---|---|---|
| Records marketing campaign attribution information, such as which campaign brought the shopper to the store. | Up to 365 days | Marketing |
Swym web pixel
Swym Wishlist Plus may also include an optional analytics web pixel.
According to Swym, this web pixel does not set cookies on its own. It reads Swym cookies and Shopify’s cart cookie to measure activity, and it runs only if the shopper has provided the relevant consent through Shopify’s consent system.
If this pixel is active on the store, merchants should make sure it is aligned with the appropriate consent categories, such as Analytics, Marketing, or Preferences, depending on the store’s setup and legal requirements.
Privacy-First Wishlist
Swym also offers an optional Privacy-First Wishlist mode.
When enabled, this mode allows wishlist functionality to continue even when a shopper declines cookies. Instead of setting cookies, wishlist items are stored locally on the shopper’s own device.
In this mode, no cookies are set and no personal information is sent to Swym unless the shopper later chooses to log in.
Important: this option does not apply to every Swym wishlist setup.
Swym notes that Privacy-First Wishlist applies specifically to:
- Advanced Product Detail Page wishlist buttons
- Advanced Collections wishlist buttons
It does not automatically apply to:
- Classic wishlist buttons
- Classic collections buttons
- Every header wishlist icon behavior
- Custom wishlist implementations
Before relying on Privacy-First Wishlist, merchants should confirm with Swym which wishlist button type their theme is using and whether the feature is enabled for their setup.
Contextual GDPR Consent
Swym also describes a separate mechanism called Contextual GDPR Consent.
This mechanism checks Shopify’s consent status when a shopper interacts with supported wishlist elements. If consent has already been granted, the wishlist action can continue. If consent has not been granted, Swym may show a prompt asking the shopper to consent.
If the shopper declines this prompt, no wishlist action is completed and no data is stored.
This is separate from Privacy-First Wishlist. Declining a Contextual GDPR Consent prompt does not automatically activate Privacy-First Wishlist’s local-device saving.
Working with Consentmo
If your store uses Consentmo as the cookie consent management platform, Consentmo continues to control:
- The cookie banner
- Consent categories
- Visitor consent preferences
- Cookie and tracking behavior controlled through the app
- The classification of detected cookies in the Cookie Scanner
Swym continues to control how Wishlist Plus behaves when the shopper has not granted consent or has declined cookies.
No special setup is required in Consentmo beyond correctly categorizing the Swym cookies based on Swym’s current cookie classification table.
How to configure Swym cookies in Consentmo
In Consentmo, Swym cookies can be added to the relevant cookie categories based on Swym’s current classification:
- Necessary cookies should be added under the Strict/Necessary category.
- Functional cookies should be added under the Functional category.
- Marketing cookies should be added under the Marketing category.
If Swym-related cookies or storage entries are detected by the Consentmo scanner, merchants can review them and assign them to the matching categories listed above.
If Privacy-First Wishlist is enabled in Swym, this does not replace the need for a cookie banner or proper cookie classification. It only changes how the Swym wishlist feature behaves when cookies are declined.
Recommended merchant checks
Before finalizing the setup, we recommend checking the following:
- Confirm whether the store uses Advanced Product Detail Page wishlist buttons or Advanced Collections wishlist buttons.
- Confirm whether Privacy-First Wishlist is enabled in Swym.
- Confirm whether the store uses Swym’s optional web pixel.
- Review all Swym cookies detected by the Consentmo scanner.
- Assign the detected Swym cookies to the correct categories in Consentmo.
- If the wishlist implementation is custom, confirm with Swym whether the same consent behavior applies.
Need help?
If you are not sure which Swym setup your store is using, we recommend confirming this with Swym support first, especially if you are using Advanced Product Detail Page buttons, Advanced Collections buttons, the header wishlist icon, or a custom wishlist implementation.
For help categorizing the detected Swym cookies in Consentmo, please contact our support team via live chat or at support@consentmo.com.
You can also review Swym’s official guide here:
https://help.getswym.com/en/articles/16093297-how-wishlist-plus-handles-cookies-and-cookie-consent
Updated on: 29/07/2026
Thank you!