Set up your bannerConfigure Your ToolsA/B Testing and Personalisation

Dynamic Yield

How to configure Dynamic Yield at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Personalise the website, Receive personalised marketing offers

Overview

This guide explains how to implement different privacy configurations for Dynamic Yield and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The Dynamic Yield (Mastercard) client-side script for personalisation, testing and recommendations.

What the service does in this scope. Cookies include _dyid (unique identifier, customer's domain), _dyid_server (1 year, customer's domain), _dyjsession (session) and DYID / DYSES on the dynamicyield.com domain. Dynamic Yield states it does not track users across multiple sites. With Active Cookie Consent enabled, users are not served personalised experiences unless they actively consent, and no personal data is processed for personalisation without consent except from strictly necessary cookies; consent is passed with DY.userActiveConsent = { accepted: true|false }. Non-personalised campaigns can be served to users without consent. Dynamic Yield operates US and EU data centres.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskActive Cookie Consent on; EU data centre; personalisation only after consent; non-personalised campaigns otherwise.
Configuration B — Higher riskScript loaded after consent; full personalisation, recommendations and audience targeting; US data centre.

⚠ Recommendation — script before consent. In A the script runs before consent and Dynamic Yield still processes data "stemming from strictly necessary cookies". Whether its cookies qualify as strictly necessary under § 25(2) TDDDG is not established by the sources. Block the script in Consenter until consent unless your DPO or independent counsel confirms otherwise.

Step 1 — Configure Dynamic Yield

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionPersonalise the websitePersonalise the website; Receive personalised marketing offers
2Active Cookie ConsentImplement DY.userActiveConsent; preview in Settings > Data Privacy > Active Cookie Consent; activation by SupportOnOn
3Non-personalised campaigns for non-consenting usersSettings > Privacy CenterOn—
4Data centreAccount setup (US or EU)EUUS
5LoadingConsenterSee ⚠ recommendationAfter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Dynamic Yield belongs to Mastercard, a US enterprise subject to the US CLOUD Act; list the United States as a potential access location in all configurations.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesPersonalise the websitePersonalise the website, Receive personalised marketing offers
Tracking methodFirst party tracking (cross-session)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device identifiers, Device characteristics, Privacy choices, Users' profilesBrowsing and interaction data, Device identifiers, Device characteristics, e-commerce Activity, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelProfile basedProfile based
Maximum storage duration1 year (_dyid_server)1 year (_dyid_server, DYID)
Processing locationEU data centre; United States as potential access locationUnited States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page