Rights Orchestration
Right to Delete erases all data related to a lead for a specific website.
Fulfill deletion requests scoped to the exact website a lead came through, since Wisepops issues a separate API key for each one.
Wisepops creates popups, banners, and notifications for lead capture and conversion, and organizations running popups across multiple websites need each site's data handled separately. Wisepops itself reflects that structure: API keys are issued per website, not as one shared credential across an entire account.
Ketch connects to Wisepops with that per-site scoping in mind.
Capabilities
The Ketch Wisepops integration covers Rights Orchestration, specifically Right to Deletion. Connection requires an API key that's issued per website, so the correct site-specific key needs to be selected when connecting, rather than assuming a single account-wide key covers everything.
Right to Delete erases all data related to a lead for a specific website.
With Ketch, teams can
The gap
Organizations running lead capture popups across multiple websites need deletion scoped correctly to the right site, not assumed to be account-wide:
Why Ketch
Permissioning infrastructure that governs Wisepops the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Wisepops requests move through the same Data Subject Rights Automation used for every other connected system.
The California Attorney General reached a $1.55 million settlement with Healthline Media over sharing sensitive data with advertisers without valid consent, a reminder that lead capture tools carry real exposure when deletion isn't scoped and fulfilled correctly.
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 Wisepops yourself.
Get started in less than 5 min