What does Consent Orchestration require to function?

Marketo's Munchkin cookie must be associated with a lead; without that association, consent orchestration won't work.

Ketch and Adobe Marketo Engage

Use Marketo's native consent support where it exists, and know exactly what manual setup is required where it doesn't.

Adobe Marketo Engage Integration Documentation

About Adobe Marketo Engage

Adobe Marketo Engage automates marketing tasks at scale, and it natively supports consent propagation for exactly two purposes: email marketing and phone marketing. Anything beyond that, analytics, personalization, or other purposes, requires custom fields that have to be created manually inside Marketo, since Marketo's own API doesn't support creating fields programmatically.

Ketch connects to Marketo working with both the native support and the manual extension path.

Capabilities

How Ketch works with Adobe Marketo Engage

The Ketch Adobe Marketo Engage integration covers Consent Orchestration, Rights Orchestration (Right to Deletion, Right to Access), and Preference Orchestration.

Consent Orchestration

For email and phone marketing works through Marketo's own native consent fields directly. For any additional purpose, analytics or personalization for example, a custom Boolean field has to be created manually in Marketo's Field Management admin section, using specific required API names (`ketchAnalytics`, `ketchBehavioralAdvertising`, `ketchDataBroking`, `ketchPersonalization`, `ketchProdEnhancement`, `ketchSmsMktg`), since Marketo doesn't allow field creation via API. Requires Marketo's Munchkin cookie to be associated with a lead for the integration to work at all.

Rights Orchestration

Fulfills Right to Access and Right to Deletion against Marketo leads through the same workflow used for every other connected system.

Preference Orchestration

Works similarly: each subscription topic needs its own custom field created manually in Marketo, with a unique API name that gets entered into the Ketch connection configuration. One functional prerequisite worth knowing:

With Ketch, teams can

Use Marketo's native email and phone marketing consent fields directly, with no custom setup required for those two purposes
Extend consent orchestration to additional purposes through documented custom field creation, with the exact required API names specified upfront
Fulfill Right to Access and Right to Deletion requests through the same workflow used for every other connected system

The gap

The problem this integration solves

Marketo's native consent support covers only two purposes, and extending beyond that requires manual work that's easy to get wrong without clear guidance:

01. Assuming Marketo supports consent for every purpose natively, when it only covers email and phone marketing, risks a real gap for other purposes

02. The Munchkin cookie association is a real functional prerequisite that isn't obvious, and consent orchestration won't work without it

Ketch resolves this by documenting exactly which purposes are native and which require manual custom field setup, including the precise API names each field needs to use.

Why Ketch

Why teams choose Ketch for Adobe Marketo Engage privacy compliance

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

Clear about what's native versus what's manual
Email and phone marketing consent work natively; every other purpose has a documented, precise custom-field setup path.
Exact API names specified upfront
The required field API names for each purpose are documented precisely, reducing the risk of a mapping error during manual setup.
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 marketing automation platforms carry real exposure when consent coverage has unaddressed gaps beyond native fields.

Questions about the Adobe Marketo Engage integration

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 Adobe Marketo Engage permissioning running end to end

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

Get Started Free

Get started in less than 5 min

Get a Demo

Ketch and Adobe Marketo Engage

About Adobe Marketo Engage