Real-time
Two-way sync
Changes in Braze or Google Pubsub instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Developer tools
Braze to Google Pubsub integration — real-time, two-way sync
Keep Braze and Google Pubsub in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Braze and Google Pubsub
Connect the tickets, records, and events in Braze to the systems engineering runs in Google Pubsub, kept current in real time and in both directions.
Braze is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Google Pubsub is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.
Stacksync syncs Custom Events, Purchases, Segments, Campaigns in Braze with Topics, Subscriptions, Messages, Schemas in Google Pubsub field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.
Common use cases
- 01 Sync CRM and billing attributes onto Braze user profiles so lifecycle campaigns target accurate plan and status data.
- 02 Push product usage events from a database or warehouse into Braze to trigger onboarding and retention journeys.
- 03 Publish new and changed database rows as messages to a Pub/Sub topic so multiple downstream subscriptions consume the change stream independently.
- 04 Consume messages from a subscription via StreamingPull and write them into a Postgres or warehouse table for durable, SQL-queryable storage.
Common sync patterns
Where Google Pubsub tracks engineering work: requests become issues
A ticket or request raised in Braze opens or updates a matching issue in Google Pubsub, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.
Where Google Pubsub moves messages between services: activity lands on the stream
Records created or changed in Braze publish to the queue or topic in Google Pubsub as they happen, so downstream services react to real events rather than polling for them.
Where Google Pubsub is the directory or identity source: one set of users
People and accounts in Braze stay matched to the users in Google Pubsub, so access, provisioning, and org changes propagate instead of being keyed in twice.
What you can sync between Braze and Google Pubsub
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Braze objects | Google Pubsub objects | How this pairing syncs | |
|---|---|---|---|
| Custom Events Behavioral events pushed into Braze to trigger campaigns and Canvases. | Snapshots Captured subscription state for seek/replay; lets already-acknowledged messages be redelivered from a point in time. | Custom Events is specific to Braze and Snapshots to Google Pubsub — each maps to any object or custom field on the other side. | |
| Purchases Transaction records logged against profiles for revenue-based targeting. | Message attributes Up to 100 key-value pairs per message; carry routing metadata and drive subscription filter expressions. | Purchases is specific to Braze and Message attributes to Google Pubsub — each maps to any object or custom field on the other side. | |
| Segments Audience definitions read for membership export and campaign targeting. | Dead-letter topics Destination for messages that exceed a subscription's max delivery attempts; isolates poison messages for later handling. | Segments is specific to Braze and Dead-letter topics to Google Pubsub — each maps to any object or custom field on the other side. | |
| Campaigns Message sends whose metadata and analytics are read for reporting. | Ordering keys Tag messages so those sharing a key deliver in publish order when message ordering is enabled; throughput capped at 1 MBps per key. | Campaigns is specific to Braze and Ordering keys to Google Pubsub — each maps to any object or custom field on the other side. | |
| Canvases Multi-step journeys; entry and performance data is read for lifecycle analysis. | Topics Named resource publishers send to; Stacksync publishes each record change as a message to a topic for downstream subscribers to consume. | Canvases is specific to Braze and Topics to Google Pubsub — each maps to any object or custom field on the other side. | |
| Subscription Groups Channel-level opt-in states synced with consent records in other systems. | Subscriptions A stream of messages from one topic; Stacksync consumes here via StreamingPull or a push endpoint, acknowledging each message after a successful write. | Subscription Groups is specific to Braze and Subscriptions to Google Pubsub — each maps to any object or custom field on the other side. |
How changes propagate between Braze and Google Pubsub
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Braze Google Pubsub Interval-based propagation
DetectionStacksync polls Braze for changes on an incremental schedule, reading only records changed since the previous pass. Braze Currents streams engagement events outward.
DeliveryEach detected change is written to Google Pubsub through its API, with automatic retries and rate-limit backoff.
Google Pubsub Braze Sub-second propagation
DetectionGoogle Pubsub notifies Stacksync of record changes through webhook events. Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST.
DeliveryEach detected change is written to Braze through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Braze: Endpoints have per-endpoint rate limits documented by Braze; batch endpoints accept multiple users per request.
- Google Pubsub: Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key.
What ships with Braze ⇄ Google Pubsub
Connect Braze and Google Pubsub for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Braze–Google Pubsub connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Braze or Google Pubsub data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Braze or Google Pubsub record.
Observability
Monitoring
Track your Braze ⇄ Google Pubsub sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Braze and Google Pubsub.
How the Braze and Google Pubsub connectors work
Braze
- Integration surface
- REST API
- Authentication
- REST API keys scoped to specific endpoints, issued per workspace
- Change detection
- Braze Currents streams engagement events outward; profile reads otherwise rely on export endpoints and polling
- Capabilities
- read · write
- Rate limits
- Endpoints have per-endpoint rate limits documented by Braze; batch endpoints accept multiple users per request
Google Pubsub
- Integration surface
- REST and gRPC (Cloud Pub/Sub API v1)
- Authentication
- Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber
- Change detection
- Consumes messages as they arrive on a subscription — StreamingPull (long-lived gRPC) or a push subscription delivering each message as an HTTPS POST; no modified-date polling
- Capabilities
- read · write · webhooks
- Rate limits
- Per-region throughput quotas (publish up to ~4 GB/s in large regions); 10 MB max per message and per publish request, 1,000 messages per request, and 1 MBps per ordering key
How it works
How to connect Braze to Google Pubsub — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Braze and Google Pubsub with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Braze
connected
Google Pubsub
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Braze and Google Pubsub objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Braze ⇄ Google PubsubCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Braze Google PubsubCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Braze and Google Pubsub integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Braze and Google Pubsub: authenticate both systems, choose the objects to sync (such as Braze's Custom Events and Purchases), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Braze side: Custom Events, Purchases, Segments, Campaigns, plus custom fields where Braze exposes them. On the Google Pubsub side: Topics, Subscriptions, Messages, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Braze and Google Pubsub: Where Google Pubsub tracks engineering work: requests become issues; Where Google Pubsub moves messages between services: activity lands on the stream; Where Google Pubsub is the directory or identity source: one set of users. A ticket or request raised in Braze opens or updates a matching issue in Google Pubsub, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.
-
Braze: REST API. Authentication: REST API keys scoped to specific endpoints, issued per workspace. Google Pubsub: REST and gRPC (Cloud Pub/Sub API v1). Authentication: Google Cloud IAM via OAuth 2.0 / service-account credentials (JSON key or workload identity); requires roles such as pubsub.publisher and pubsub.subscriber. Stacksync manages authentication, retries, and rate limits on both sides.
-
Braze: Braze Currents streams granular engagement events to data warehouses and storage destinations, which is how message-level data typically leaves the platform. Google Pubsub: Individual messages are capped at 10 MB, with a maximum of 1,000 messages or 10 MB per publish request and up to 100 attributes per message. Stacksync's field mapping accounts for these differences between Braze and Google Pubsub without custom code.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 311 integrations available for Braze and Google Pubsub.
Popular · 7 of 311
-
Braze ⇄ Rabbitmq -
Braze ⇄ Azure Service Bus -
Braze ⇄ Datadog -
Braze ⇄ Ldap -
Google Pubsub ⇄ Zendesk -
Google Pubsub ⇄ Campfire -
Google Pubsub ⇄ Front
No integrations match .
