How does Wunderkind leverage cookies?
As with most web technologies, Wunderkind may leverage cookies to track user history across pages and sessions. Cookies allow us to maintain information about end-users, improve the user shopping experience, and make intelligent segmentation decisions when serving onsite, triggered email, and text campaigns.
Wunderkind’s identity technology relies on pseudonymous observed browser, network, and device level signals. While our identity technology does leverage cookies where available, it is not reliant upon them.
Wunderkind cookie classification depends on locale
Wunderkind continues to place a great deal of importance in making sure our technology stays up to date with the ever changing privacy regulations. To this end, we have spent countless hours with outside counsel and third party entities (like OneTrust) to ensure our cookies are categorized in a compliant manner that still aims to drive performance for our clients. That said, please consult with your own legal counsel for any questions.
The United States, Canada, and other non-GDPR territories do not require consent for cookies or data collection. Therefore, we recommend setting our tag to load ahead of cookie consent in order to optimize UX and performance. For some CMPs like OneTrust, you may need to classify Wunderkind cookies as "Strictly Necessary" in order for our tag to load ahead of consent.
For GDPR territories, we recommend setting our tag to load after affirmative user cookie or tracking consent. For most CMPs, this is done by classifying cookies as "Advertising" or "Marketing" cookies. Note that some “Advertising” cookies help personalize the user experience in a 3rd party context -- typically where the targeting takes place on a different URL than when data is initially collected via the cookie. Wunderkind's use of cookies however is limited to use for personalizing the end user's experience on the site they are visiting, not 3rd party sites. Wunderkind does not share any user data with 3rd parties (outside of approved subprocessors).
Wunderkind participates in the IAB Consent Framework to track and record consent.
Required Cookies
| Cookie Name | Domain | Party | Description - When would these cookies be utilized? | Lifespan |
| bounceClientVisitXXXX | Client's domain OR .bounceexchange.com |
1st Party Cookie 3rd Party Cookie 1st Party Local Storage 3rd Party Local Storage |
Wunderkind specific product, user or campaign related data storage. Party type (e.g. 1st or 3rd) and the storage location (e.g. cookie or local storage) is determined by the visitors browser and configured Wunderkind settings. The domain used to store data is determined by whether the data is persisted to 1st party or 3rd party. 1st party is the clients domain, and 3rd party is the bounceexchange.com domain. |
1 year Note: - If local storage is set (1st or 3rd party) there is no expiration date for most browsers - Safari does have an expiration date of 7 days on local storage if the visitor hasn't returned to the site. That's a Safari specific exception. |
| bounceClientVisitXXXXv | Client's domain OR .bounceexchange.com |
1st Party Cookie 1st Party Local Storage |
Referral and landing page information including Google Organic / Paid indication | 30 minutes |
Conditional Cookies
These cookies will be set for specific purposes related to your specific campaign strategy & account setup.
| Cookie Name | Domain | Party | Description - When would these cookies be utilized? | Lifespan |
| __ibxc | Client's Domain | 1st Party Cookie | Used to save click-through data | 1 year |
| __ibxc0 | Client's Domain | 1st Party Cookie | Used for conversion tracking | 1 year |
| __ibxcr | Client's Domain | 1st Party Cookie | Sets the ibx cookie for cart | 12 Hours |
| __ibxl | Client's Domain | 1st Party Cookie | Set to prevent multiple "bx_lookup" requests | 1 year |
| __ibxm | Client's Domain | 1st Party Cookie | Sets the ibx cookie for mode | 1 year |
| __ibxu | Client's Domain | 1st Party Cookie | Used for inbox user tracking | 1 year |
| _ibx_ci | Client's Domain | 1st Party Cookie | Used for inbox tracking | 1 year |
| bounceClientVisitXXXXc | .bounceexchange.com | 3rd Party Cookie | This data is set when an conversion occurs via convert2 | 30 minutes |
| gdpr_opt_out | .bounceexchange.com | 3rd Party Cookie | Used for GDPR purposes | 1827 days |
| bxgraphv2CCPAOptOut | Client's Domain | 1st Party Cookie | Used for CCPA purposes | 1827 Days |
| yoc_token | .bounceexchange.com | 3rd Party Cookie | Your Online Choices Selection | 1 year |
| __3idcontext | .cdnwidget.com | 3rd Party Cookie | Helps id reinforcement | 13 months |
| __adcontext | .cdnwidget.com | 3rd Party Cookie | Helps id reinforcement with regards to opt out | 13 Months |
| __idcontext | .cdnwidget.com | 1st Party Cookie | Helps id reinforcement | 13 months |
| __idcontext_APIKEY | .cdnwidget.com |
1st Party Local Storage 1st Party Session Storage |
Helps id reinforcement |
1) Local Storage: - If local storage is set (1st or 3rd party) there is no expiration date for most browsers - Safari does have an expiration date of 7 days on local storage if the visitor hasn't returned to the site. That's a Safari specific exception. 2) Session Storage: visitors browsing session |
These cookies will be set for specific purposes related to your specific campaign strategy & account setup.
| Cookie Name | Domain | Party | Description - When would these cookies be utilized? | Lifespan |
| API | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| BXDID | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| bxgraphGDPROptOut | Client's Domain |
1st Party Cookie 1st Party Local Storage |
Flag used to opt out and respect privacy |
1) Cookie - 1827 days 2) Local Storage - If local storage is set (1st or 3rd party) there is no expiration date for most browsers - Safari does have an expiration date of 7 days on local storage if the visitor hasn't returned to the site. That's a Safari specific exception. |
| bxgraphv2CCPAOptOut | Client's Domain |
1st Party Cookie 1st Party Local Storage |
Flag used to opt out and respect privacy |
1) Cookie - 1827 days 2) Local Storage - If local storage is set (1st or 3rd party) there is no expiration date for most browsers - Safari does have an expiration date of 7 days on local storage if the visitor hasn't returned to the site. That's a Safari specific exception. |
| bxgraphOptOut | .cdnwidget.com | 3rd Party Cookie | Flag used to opt out and respect privacy | 1827 days |
| bxgraphYOCOptOut | .cdnwidget.com | 3rd Party Cookie | Flag used to opt out and respect privacy | 1827 days |
| BXVID | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| BXWID | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| iv | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| __PT1CID | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| __PT1DID | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |
| v | .cdnwidget.com | 3rd Party Cookie | Temporary data for analytics | 60 sec |