Consent Orchestration
Syncs consent choices into Intercom through the same workflow used for every other connected system.
Ketch and Intercom
Fulfill access and deletion requests, and sync consent, across both a person's email and Intercom's own managed visitor identifiers, so a request doesn't depend on which identifier happened to be captured.
About Intercom
Intercom combines automated and human-assisted customer service in one platform, which means a customer's data can be tied to their email address in some interactions and to an anonymous visitor ID in others, especially for conversations that start before someone identifies themselves. A rights or consent request that only matches on email can miss data still tied to a visitor identifier.
Ketch connects to Intercom to match across both.
Capabilities
How Ketch works with Intercom
The Ketch Intercom integration covers Consent Orchestration and Rights Orchestration (Right to Access, Right to Delete).
Rights Orchestration
Fulfills Right to Access and Right to Delete against Intercom through the same workflow used for every other connected system. Identifier mapping covers three types: email address, Intercom Visitor ID, and Visitor ID, with the latter two managed automatically and requiring no separate setup.
With Ketch, teams can
- Fulfill Right to Access and Right to Delete requests matched across email and Intercom's own managed visitor identifiers
- Sync consent choices through the same Consent Orchestration workflow used for every other connected system
- Cover conversations that started anonymously (visitor-identified) as well as ones tied to a known email address
The gap
The problem this integration solves
A platform that serves both known customers and anonymous visitors creates a real identity-matching challenge for rights and consent enforcement:
01. A rights request matched only on email misses conversation data still tied to an anonymous visitor identifier from before someone identified themselves
02. Manually reconciling which identifier applies to which conversation doesn't scale to real request volume
03. Consent choices that only sync for known, identified customers leave anonymous visitor interactions unaddressed
Ketch resolves this by supporting all three identifier types Intercom recognizes, so coverage doesn't depend on whether a person was identified at the start of their interaction or partway through it.
Why Ketch
Why teams choose Ketch for Intercom privacy compliance
Permissioning infrastructure that governs Intercom the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Matches across known and anonymous identifiers
Email, Intercom Visitor ID, and Visitor ID are all supported, so coverage isn't limited to identified customers alone.
One workflow for both consent and rights
Both capabilities move through the same connected workflows used across every other integration.
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 customer service platforms carry real exposure when rights and consent don't reach every identifier a person might be tracked under.
Questions about the Intercom integration
Related reading
Expert insights for teams connecting Intercom
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.
See Intercom permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Intercom yourself.
Get Started Free
Get started in less than 5 min