Two-way sync
Changes in Google Cloud Platform or Xactly instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Platform and Xactly in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, Quotas / Targets from Xactly land in Google Cloud Platform as live tables, updated within seconds, and columns computed in Google Cloud Platform write back to fields in Xactly. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Lead scores, churn risk, or usage segments computed in Google Cloud Platform appear as fields in Xactly, where the people working accounts actually see them.
Join Xactly's relationship data with billing, product, and support data in Google Cloud Platform to build the customer picture the CRM alone cannot hold.
Deduplication and normalization done in Google Cloud Platform can be written back, so warehouse-side cleanup actually fixes the 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 Platform objects | Xactly objects | How this pairing syncs | |
|---|---|---|---|
| Spanner tables Strongly consistent relational tables accessed via SQL for transactional workloads. | Credits Crediting records that tie an order to a participant and position; system-calculated credits are read, while manual and adjustment credits are loaded through Connect, so read and write. | Spanner tables is specific to Google Cloud Platform and Credits to Xactly — each maps to any object or custom field on the other side. | |
| BigQuery datasets Namespaces that group tables; syncs target tables within a dataset. | Transactions (Commission & Bonus) Calculated commission and bonus line items produced by Incent's calculation engine; read as the output of comp runs for reporting and downstream payout, so effectively read-only results. | BigQuery datasets is specific to Google Cloud Platform and Transactions (Commission & Bonus) to Xactly — each maps to any object or custom field on the other side. | |
| BigQuery tables The primary analytics destination, written through load jobs or the Storage Write API and queried with SQL. | Participants (Payees) Sales reps and payees keyed to positions; loaded and updated from HRIS/HCM source data through Connect (write) and read for roster reporting, so read and write. | BigQuery tables is specific to Google Cloud Platform and Participants (Payees) to Xactly — each maps to any object or custom field on the other side. | |
| Cloud SQL databases Managed Postgres, MySQL, and SQL Server instances synced like ordinary relational databases. | Positions & Titles Org-hierarchy positions and titles that credits and quotas roll up to; loaded and maintained through Connect (write) and read to resolve the hierarchy, so read and write. | Cloud SQL databases is specific to Google Cloud Platform and Positions & Titles to Xactly — each maps to any object or custom field on the other side. | |
| Cloud Storage objects Staging area for file-based bulk loads into BigQuery and other services. | Quotas / Targets Period quota and target values per position or plan; loaded from planning tools through Connect (write) and read for attainment reporting, so read and write. | Cloud Storage objects is specific to Google Cloud Platform and Quotas / Targets to Xactly — each maps to any object or custom field on the other side. | |
| Pub/Sub topics Event streams used to move change events between systems in near real time. | Payment Summary (Payable) Approved payable amounts per participant per period; read as the output that feeds payroll and accounts payable, so effectively read-only. | Pub/Sub topics is specific to Google Cloud Platform and Payment Summary (Payable) to Xactly — each maps to any object or custom field on the other side. |
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.
DetectionGoogle Cloud Platform pushes changes as they happen — webhook events backed by change data capture. Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery.
DeliveryEach detected change is applied to Xactly as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Xactly for changes on an incremental schedule, reading only records changed since the previous pass. No CDC log for external tools to consume.
DeliveryEach detected change is applied to Google Cloud Platform as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Platform–Xactly connection.
Changes in Google Cloud Platform or Xactly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Platform or Xactly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Platform or Xactly record.
Track your Google Cloud Platform ⇄ Xactly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Platform and Xactly.
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.
Authenticate Google Cloud Platform and Xactly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Google Cloud Platform and Xactly 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Platform and Xactly: authenticate both systems, choose the objects to sync (such as Google Cloud Platform's Spanner tables and BigQuery datasets), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Google Cloud Platform: Varies by service: log-based CDC on Cloud SQL (logical replication or binlog, also via Datastream), Pub/Sub for event delivery, polling for BigQuery tables. On Xactly: No CDC log for external tools to consume. Incremental sync uses SQL predicates on modified/last-updated timestamp columns (for example WHERE modified_date > watermark) against Connect's queryable objects, or scheduled Connect ETL Pipelines that pull deltas since the last run. Xactly Connect has no outbound HTTP webhooks, so change detection is pull/ETL-based. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Xactly side: Transactions (Commission & Bonus), Participants (Payees), Positions & Titles, Quotas / Targets, plus custom fields where Xactly exposes them. On the Google Cloud Platform side: Spanner tables, BigQuery datasets, BigQuery tables, Cloud SQL databases. 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 Google Cloud Platform and Xactly: Scores and segments back on the record; A single customer view; Cleanup that sticks. Lead scores, churn risk, or usage segments computed in Google Cloud Platform appear as fields in Xactly, where the people working accounts actually see them.
Google Cloud Platform: Per-service REST and gRPC APIs; BigQuery speaks SQL and Cloud SQL exposes standard database wire protocols. Authentication: IAM service accounts with OAuth 2.0 tokens. Xactly: Xactly Connect REST API v2 (JSON), plus ODBC/JDBC drivers over the same ANSI-SQL data model. Incent data is exposed as SQL-queryable objects (for example xactly_order, xactly_credit, xactly_transaction, xactly_payment); data is loaded and extracted through Connect load/query steps and server-side ETL Pipelines. The base host is region/pod-specific (for example https://<pod>.xactlycorp.com). Authentication: OAuth 2.0 via the Xactly Connect API Gateway (bearer tokens issued on behalf of an Xactly Incent user), with HTTP Basic authentication using a dedicated Xactly Connect service-user's credentials also supported for the Connect REST API v2. The connecting user needs Connect/API access plus the relevant object permissions in Incent. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 562 integrations available for Google Cloud Platform and Xactly.