Ketch and Acquia

Fulfill access and deletion requests against a Drupal-based digital experience platform, across the specific environments it runs in.

Acquia

About Acquia

Acquia's Digital Experience Platform, built on open-source Drupal, powers digital products and services for a wide range of brands, spanning marketing, development, and IT operations. Because Acquia environments are often split across multiple subdomains for different purposes, a rights request against Acquia isn't just about finding one API endpoint; it's about reaching the right environment and, separately, the right data-erasure endpoint.

Ketch connects to Acquia to handle that request across the environments it's configured for.

Capabilities

How Ketch works with Acquia

The Ketch Acquia integration covers Rights Orchestration: Right to Delete and Right to Access.Email, the identifier used for matching, is managed automatically by Ketch and requires no separate setup.

Rights Orchestration

Fulfills Right to Access and Right to Delete against Acquia through the same workflow used for every other connected system. The connection is configured against Acquia's environment structure directly, with distinct subdomain values for different environments and a separate data-erasure subdomain specifically for deletion requests, rather than assuming one endpoint handles everything.

With Ketch, teams can

  • Fulfill Right to Access and Right to Delete requests against Acquia's Drupal-based platform through the same workflow used for every other connected system
  • Configure the connection against Acquia's actual environment structure, including a dedicated data-erasure endpoint, rather than a one-size-fits-all connection
  • Skip manual identifier setup, since email is managed automatically for this integration

The gap

The problem this integration solves

A digital experience platform built on an open, extensible foundation like Drupal often means data is spread across multiple environments and subdomains rather than one unified endpoint:

01. A rights request against the wrong environment subdomain, or without hitting the dedicated erasure endpoint, can silently fail to reach the actual data

02. Manually tracking which subdomain does what for a given Acquia setup doesn't scale to a real privacy program's request volume

03. Coordinating credentials (username, password, environment values) for every individual request isn't a repeatable process

Ketch resolves this by configuring the connection against Acquia's real environment structure once, so every subsequent request routes correctly without manual reconfiguration.

Why Ketch

Why teams choose Ketch for Acquia privacy compliance

Permissioning infrastructure that governs Acquia the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.

  • Built for Acquia's actual environment structure

    The connection accounts for separate environment subdomains and a dedicated data-erasure subdomain, rather than assuming a single generic endpoint.

  • No manual identifier setup required

    Email is managed automatically, removing one common source of misconfiguration.

  • Backed by enforcement precedent

    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 any digital experience platform holding customer data carries real exposure when rights requests aren't reliably fulfilled.

Questions about the Acquia integration

Integrations

Pre-built APIs with 1,000+ systems, apps, and models

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.

Browse All Integrations

See Acquia permissioning running end to end

Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Acquia yourself.

Get Started Free

Get started in less than 5 min