Skip to content
Database ⇄ CRM

Google Cloud Spanner to Veeva CRM integration — real-time, two-way sync

Keep Google Cloud Spanner and Veeva CRM 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 Google Cloud Spanner and Veeva CRM

Treat Veeva CRM like part of your database: its records live in Google Cloud Spanner as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Google Cloud Spanner, where it can be queried and joined like everything else.

Stacksync mirrors Accounts (HCPs and HCOs), Calls, Medical Inquiries, Sample Transactions from Veeva CRM into Rows, Interleaved tables, Secondary indexes, Change streams in Google Cloud Spanner with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Veeva CRM with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Feed territory alignments from a roster system into Veeva as field teams change.
  • 02 Mirror medical inquiries into a medical information system for fulfillment and audit.
  • 03 Push billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.
  • 04 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.

Common sync patterns

Trigger workflows from CRM changes

Field and stage updates in Veeva CRM arrive as row changes in Google Cloud Spanner, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Veeva CRM become tables in Google Cloud Spanner you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to Google Cloud Spanner sync onto the matching records in Veeva CRM, giving go-to-market teams live product context.

What you can sync between Google Cloud Spanner and Veeva CRM

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.

Google Cloud Spanner objects Veeva CRM objects How this pairing syncs
Change streams Capture inserts, updates, and deletes for log-style change data capture. Medical Inquiries Information requests captured in the field and routed to medical affairs. Change streams is specific to Google Cloud Spanner and Medical Inquiries to Veeva CRM — each maps to any object or custom field on the other side.
Views Read-only projections useful for shaping data before it leaves Spanner. Sample Transactions Sample disbursement records tracked for regulatory compliance. Views is specific to Google Cloud Spanner and Sample Transactions to Veeva CRM — each maps to any object or custom field on the other side.
Databases Top-level containers that scope schema and sync configuration. Consent Records Channel-level communication consent for HCPs, synced to enforce opt-outs across systems. Databases is specific to Google Cloud Spanner and Consent Records to Veeva CRM — each maps to any object or custom field on the other side.
Tables Relational tables mapped one-to-one to sync targets. Key Messages and CLM Content Approved content presented during calls, referenced in activity data. Tables is specific to Google Cloud Spanner and Key Messages and CLM Content to Veeva CRM — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. Territories and Alignments Rep-to-account assignments, often fed from a roster or alignment system. Rows is specific to Google Cloud Spanner and Territories and Alignments to Veeva CRM — each maps to any object or custom field on the other side.
Interleaved tables Child rows physically co-located with parents; synced as related records. Events Medical events and speaker programs managed through Veeva's events capabilities. Interleaved tables is specific to Google Cloud Spanner and Events to Veeva CRM — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and Veeva CRM

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.

Google Cloud Spanner Veeva CRM Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

DeliveryEach detected change is written to Veeva CRM through its API, with automatic retries and rate-limit backoff.

Veeva CRM Google Cloud Spanner Interval-based propagation

DetectionStacksync polls Veeva CRM for changes on an incremental schedule, reading only records changed since the previous pass. Polling on record modification timestamps.

DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • Veeva CRM: Subject to the underlying platform's API request allocations, which are contract-dependent.
What ships with Google Cloud Spanner ⇄ Veeva CRM

Connect Google Cloud Spanner and Veeva CRM for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Veeva CRM connection.

Real-time

Two-way sync

Changes in Google Cloud Spanner or Veeva CRM instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Cloud Spanner or Veeva CRM 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 Google Cloud Spanner or Veeva CRM record.

Observability

Monitoring

Track your Google Cloud Spanner ⇄ Veeva CRM sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Veeva CRM.

How the Google Cloud Spanner and Veeva CRM connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

Veeva CRM

Integration surface
Salesforce-platform APIs (REST, SOAP, Bulk) for classic Veeva CRM; Vault REST API for Vault CRM
Authentication
OAuth 2.0
Change detection
Polling on record modification timestamps; platform event streams where the underlying org enables them
Capabilities
read · write
Rate limits
Subject to the underlying platform's API request allocations, which are contract-dependent.
How it works

How to connect Google Cloud Spanner to Veeva CRM — 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.

  1. 01

    Connect your apps

    Authenticate Google Cloud Spanner and Veeva CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Google Cloud Spanner connected
    Veeva CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Spanner and Veeva CRM 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Google Cloud Spanner ⇄ Veeva CRM
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Google Cloud Spanner Veeva CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Google Cloud Spanner and Veeva CRM integration FAQ

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 426 integrations available for Google Cloud Spanner and Veeva CRM.

Popular · 7 of 426
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.