Stop future data collection across every domain from an opted-out device, not just the specific site someone happened to opt out on.
Dynamic Yield personalizes interactions across a website, social, email, text, and increasingly real-world touchpoints, using A/B testing and AI to customize experiences. Because personalization engines like this often operate across multiple domains and properties, a real opt-out needs to stop collection everywhere that device or browser is recognized, not just the single domain where the opt-out happened.
Ketch connects to Dynamic Yield to enforce exactly that scope.
Capabilities
The Ketch Dynamic Yield integration covers Consent Orchestration.
Opting out stops future data collection from the current device or browser across every domain, overriding any previous opt-in method that was in effect. If someone previously opted out and later opts back in, data collection resumes from that point forward.
With Ketch, teams can
The gap
A personalization engine spanning multiple domains and channels needs an opt-out that actually matches that scope, not a per-domain patchwork:
Why Ketch
Permissioning infrastructure that governs Dynamic Yield the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
An opt-out stops data collection from a device across every domain Dynamic Yield operates on, not just one.
The California Privacy Protection Agency fined Honda $632,000 over improperly configured data sharing with ad-tech partners, a reminder that personalization platforms operating across multiple domains carry real exposure when opt-out doesn't match that same scope.
Related reading
Integrations
Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Dynamic Yield yourself.
Get started in less than 5 min
