Preference Orchestration
Syncs subscription preferences into Google Pub/Sub through the same workflow used for every other connected system.
Ketch and Google Pub/Sub
Publish consent and preference events to a real-time messaging topic, so any system that subscribes can react, without building a separate integration for each one.
About Google Pub/Sub
Google Cloud Pub/Sub is a fully managed, event-driven messaging service built for scalable, low-latency communication across distributed systems. Rather than connecting Ketch to one specific downstream application, this integration publishes consent and preference change events to a Pub/Sub topic directly, letting any number of internal systems subscribe and react to those events on their own.
Ketch connects to Google Pub/Sub to make consent and preference changes available this way.
Capabilities
How Ketch works with Google Pub/Sub
The Ketch Google Pub/Sub integration covers Consent Orchestration and Preference Orchestration.Connection requires a Google Pub/Sub service account key (a JSON credential generated in the Google Cloud Console), a Consent Topic Name, and optionally a separate Subscription Topic Name.
Consent Orchestration
Syncs consent choices into Google Pub/Sub through the same workflow used for every other connected system. When a consent or preference change occurs, Ketch publishes a structured event message to a configured Pub/Sub topic: a consent message carrying the identity, jurisdiction, legal basis, and both custom and canonical purpose grant states, or a preference message carrying the identity and the specific subscription topic's updated status. Consent and preference events can be published to the same topic or to separate ones, depending on how an organization wants to route them.
With Ketch, teams can
- Publish structured consent and preference events to Google Cloud Pub/Sub in real time, rather than polling or manual export
- Let any number of internal systems subscribe to the same topic and react independently, without a separate Ketch integration for each one
- Route consent and preference events to the same topic or separate topics, depending on internal architecture
The gap
The problem this integration solves
Organizations with many internal systems that need to react to consent changes face a real scaling problem if each one requires its own direct integration:
01. Building a separate point-to-point integration for every internal system that needs consent or preference data doesn't scale as the number of systems grows
02. A polling-based or manual export approach to syncing consent state introduces real latency between a person's choice and systems actually reflecting it
03. Different internal teams may want different levels of detail (canonical purposes versus custom purposes, for example) from the same underlying event
Ketch resolves this by publishing a structured, real-time event to a shared Pub/Sub topic, so any subscribing system gets the same event without a bespoke integration.
Why Ketch
Why teams choose Ketch for Google Pub/Sub privacy compliance
Permissioning infrastructure that governs Google Pub/Sub the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
One publish, many subscribers
A single event reaches every system subscribed to the topic, rather than requiring a separate integration per downstream system.
Real-time, structured events
Consent and preference messages carry identity, jurisdiction, legal basis, and both canonical and custom purpose states in one structured payload.
Backed by enforcement precedent
The California Privacy Protection Agency fined Honda $632,000 over improperly configured data sharing with ad-tech partners, a reminder that consent state needs to reach every system that acts on personal data, not just the ones with a direct integration.
Questions about the Google Pub/Sub integration
Related reading
Expert insights for teams connecting Google Pub/Sub
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 Google Pub/Sub permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Google Pub/Sub yourself.
Get Started Free
Get started in less than 5 min