Skip to content
Analytics ⇄ CRM

Tableau to Veeva CRM integration — real-time data sync

Keep Tableau 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 Tableau and Veeva CRM

Put live Veeva CRM data behind every dashboard and cohort in Tableau, and write the segments and scores Tableau computes back onto the Veeva CRM record — one connection, not a nightly export.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Veeva CRM, so Veeva CRM always reflects the current state of Tableau — without exports, scripts, or schedulers.

Tableau turns data into dashboards, cohorts, and metrics; Veeva CRM is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.

Stacksync syncs Key Messages and CLM Content, Territories and Alignments, Events, Approved Email Activity from Veeva CRM into Tableau field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Tableau write back to fields in Veeva CRM, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 02 Read Databases, Tables, and Fields from the Metadata API to populate a data catalog with Tableau lineage and column definitions.
  • 03 Feed territory alignments from a roster system into Veeva as field teams change.
  • 04 Mirror medical inquiries into a medical information system for fulfillment and audit.

Common sync patterns

One customer across analytics and CRM

The same account or person is keyed consistently in both systems, so a profile or row in Tableau lines up with the contact or account in Veeva CRM.

A record that outlives edits in the CRM

A continuously synced copy of Veeva CRM's records and activity in Tableau keeps a queryable history even as records change or age out of the CRM.

Customer context in Tableau

Accounts, contacts, deals, and activity from Veeva CRM sync into Tableau, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.

What you can sync between Tableau 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.

Tableau objects Veeva CRM objects How this pairing syncs
Extract Refresh Tasks Scheduled extract refreshes; status and history read via REST, with DatasourceRefreshSucceeded and Failed events delivered by webhooks. Territories and Alignments Rep-to-account assignments, often fed from a roster or alignment system. Extract Refresh Tasks is specific to Tableau and Territories and Alignments to Veeva CRM — each maps to any object or custom field on the other side.
Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Events Medical events and speaker programs managed through Veeva's events capabilities. Fields and Columns is specific to Tableau and Events to Veeva CRM — each maps to any object or custom field on the other side.
Published Data Sources Published data sources (.tdsx); their underlying rows are read via the VizQL Data Service, and refresh state is tracked through content webhooks. Approved Email Activity Sent-email records from Veeva Approved Email, used in engagement reporting. Published Data Sources is specific to Tableau and Approved Email Activity to Veeva CRM — each maps to any object or custom field on the other side.
Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Accounts (HCPs and HCOs) Healthcare professionals and organizations; the central entity most syncs key on. Workbooks is specific to Tableau and Accounts (HCPs and HCOs) to Veeva CRM — each maps to any object or custom field on the other side.
Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Calls Recorded visits and interactions with HCPs, including samples dropped and key messages shown. Views is specific to Tableau and Calls to Veeva CRM — each maps to any object or custom field on the other side.
Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Medical Inquiries Information requests captured in the field and routed to medical affairs. Projects is specific to Tableau and Medical Inquiries to Veeva CRM — each maps to any object or custom field on the other side.

How changes propagate between Tableau 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.

Tableau Veeva CRM Sub-second propagation

DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.

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

Veeva CRM Tableau 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.

DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating Veeva CRM records.

Rate-limit considerations

  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
  • Veeva CRM: Subject to the underlying platform's API request allocations, which are contract-dependent.
What ships with Tableau ⇄ Veeva CRM

Connect Tableau and Veeva CRM for flexible, real-time data sync.

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Tableau ⇄ 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 Tableau and Veeva CRM.

How the Tableau and Veeva CRM connectors work

Tableau

Integration surface
REST API, Metadata API (GraphQL), and VizQL Data Service
Authentication
Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.

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 Tableau 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 Tableau 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
    Tableau connected
    Veeva CRM connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Tableau 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 · Tableau ⇄ 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
    Tableau Veeva CRM
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Tableau 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 437 integrations available for Tableau and Veeva CRM.

Popular · 7 of 437
All Tableau integrations All Veeva CRM integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own