Skip to main content

Wunderkind Cookies and Consent Management Platforms

Updated

How does Wunderkind leverage cookies?

As with most web technologies, Wunderkind may leverage cookies and similar tracking technologies 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 HTTP cookies where available, it is not reliant upon them. Rather, the identity platform technologies also leverages local storage and probabilistic identifiers built off of hashed email addresses, or HEMs.

 

Customers are responsible for configuring the Consent Management Platform for their websites

Given recent changes to the regulatory environment (e.g., CIPA in California, Law 25 in Quebec, GDPR, LGPD in Brazil), we are seeing more and more places where a consent for cookies, profiling and similar activities is required. As a result, we wanted to share the following information about WKND cookies so that each Clientʼs legal and privacy teams are in good position to make informed decisions when configuring the consent management platforms (e.g., OneTrust) on your digital properties.

In some jurisdictions, it may make sense to enable the Wunderkind tag to load ahead of cookie consent requests in order to optimize UX and performance. However, we strongly encourage you to ensure that your implementation complies with all applicable privacy and data protection laws. For example, in addition to any required consents, your CMP configuration should ensure that opt-out choice requirements (e.g., sale, sharing, profiling, ad targeting) are met.

Note that Wunderkind does not share any of the data listed below with 3rd parties (outside of approved sub-processors).

 

Required Cookies

Cookie Name: bounceClientVisitXXXX

  • Domain: Client's domain OR .bounceexchange.com
  • Party:
    • 1st Party Cookie
    • 3rd Party Cookie
    • 1st Party Local Storage
    • 3rd Party Local Storage
  • Lifespan: 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.
  • Description: Used for 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.

Cookie Name: bounceClientVisitXXXXv

  • Domain: Client's domain OR .bounceexchange.com
  • Party:
    • 1st Party Cookie
    • 1st Party Local Storage
  • Lifespan: 30 minutes(however if local storage there is no expiration)
  • Description: Referral and landing page information including Google Organic / Paid indication.

 

Conditional Cookies

These cookies will be set for specific purposes related to your specific campaign strategy & account setup. 

Cookie Name: bounceClientVisit
XXXXc

  • Domain: .bounceexchange.com
  • Party: 3rd Party Cookie
  • Lifespan: 30 minutes
  • Description: This data is set when an conversion occurs via convert2

Cookie Name: gdpr_opt_out

  • Domain: .bounceexchange.com
  • Party: 3rd Party Cookie
  • Lifespan: 1827 days
  • Description: Used for GDPR purposes

Cookie Name: bxgraphv2CCPAOptOut

  • Domain: Client's domain
  • Party: 1st Party Cookie
  • Lifespan: 1827 Days
  • Description: Used for CCPA purposes

Cookie Name: __3idcontext

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 13 months
  • Description: Helps id reinforcement

Cookie Name: __adcontext

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 13 Months
  • Description: Helps id reinforcement with regards to opt out

Cookie Name: __idcontext

  • Domain: .cdnwidget.com
  • Party: 1st Party Cookie
  • Lifespan: 13 months
  • Description: Helps id reinforcement

Cookie Name: _idcontext_APIKEY

  • Domain: Client's domain
  • Party: 1st Party Local Storage; 1st Party Session Storage
  • Lifespan:
    • 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
    • Session Storage
      • visitors browsing session
  • Description: Helps id reinforcement

Cookie Name: wdidXXXX

  • Domain: Clients’s Domain
  • Party: 1st Party Server Side Cookie
  • Lifespan: 90 days
  • Description: Used in Server Side Tracking to persist the Wunderkind Identifier

Cookie Name: API

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: BXDID

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: bxgraphGDPROptOut

  • Domain: Client's Domain
  • Party: 1st Party Cookie; 1st Party Local Storage
  • Lifespan:
    • Cookie: 1827 days
    • 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.
  • Description: Flag used to opt out and respect privacy

Cookie Name: bxgraphv2CCPAOptOut

  • Domain: Client's Domain
  • Party: 1st Party Cookie; 1st Party Local Storage
  • Lifespan:
    • Cookie: 1827 days
    • 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.
  • Description: Flag used to opt out and respect privacy

Cookie Name: bxgraphOptOut

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 1827 days
  • Description: Flag used to opt out and respect privacy

Cookie Name: bxgraphYOCOptOut

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 1827 days
  • Description: Flag used to opt out and respect privacy

Cookie Name: BXVID

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: BXWID

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: iv

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: __PT1CID

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: __PT1DID

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

Cookie Name: v

  • Domain: .cdnwidget.com
  • Party: 3rd Party Cookie
  • Lifespan: 60 sec
  • Description: Temporary data for analytics

 

Related articles

Comments

0 comments

Article is closed for comments.

Powered by Zendesk