--- title: "Treasure Data connector: setup and compatibility | Stacksync" description: "Treasure Data integration planning: Databases, Tables and Master (Parent) Segments. Compatibility, identity, dependencies, and validation." canonical: https://www.stacksync.com/connectors/treasuredata last_modified: 2026-09-15 --- Analytics · Two-way sync platform # Treasure Data integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Treasure Data workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Databases, Tables and Master (Parent) Segments. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Databases** - **Tables** - **Master (Parent) Segments** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=treasuredata) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Treasure Data records to discuss. These Treasure Data record examples help scope a technical review. They are not a list of verified Stacksync operations. Databases Identify this record type and the operation you need to review with Stacksync. Tables Identify this record type and the operation you need to review with Stacksync. Master (Parent) Segments Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Segments Identify this record type and the operation you need to review with Stacksync. Journeys Identify this record type and the operation you need to review with Stacksync. Predictive Segments Identify this record type and the operation you need to review with Stacksync. Connection setup ## Treasure Data connection requirements. Review Treasure Data access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Treasure Data account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Treasure Data, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Treasure Data integration. Document the event or metric grain, dimensions, time zone, and computation time. A person-level score and a daily aggregate should not share an identity rule. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Treasure Data **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. Load related records in the right order List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### Mapping checks by record type #### Databases, Tables and Master (Parent) Segments Confirm object support with Stacksync Identity Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. Fields to consider Source record identifier · Account or workspace · Required business values · Related record identifiers Related records to resolve first List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Test before going live Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Treasure Data integration in four steps. The same dimensions and period yield comparable values; a late correction updates the intended result without overwriting a newer computation. ### View the four setup tests and expected results 1. ### Confirm the intended Treasure Data account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Databases, Tables and Master (Parent) Segments Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. **Expected result:** The same dimensions and period yield comparable values; a late correction updates the intended result without overwriting a newer computation. 3. ### Test the operation your workflow needs Review one Treasure Data record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Treasure Data integration. ### Diagnose record matching, delayed changes, and rejected operations A Treasure Data record appears under the wrong destination record Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Treasure Data implementation’s change-detection method for Databases, Tables and Master (Parent) Segments. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Treasure Data object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Treasure Data workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=treasuredata) ## Treasure Data integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Treasure Data connector FAQ ### How should I plan an integration with Treasure Data? Document the event or metric grain, dimensions, time zone, and computation time. A person-level score and a daily aggregate should not share an identity rule. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Treasure Data connector write changes back? Write-back support is not established for this connection. Review the Treasure Data records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Treasure Data data? Request a representative record and its documented stable identifier. Define the owning account/workspace and the business meaning of one record before creating a cross-system lookup. ### Which related records should I load first for Treasure Data? List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### How do I validate Treasure Data changes after the initial load? Demonstrate how an existing record is found after a label change, and how a related record is resolved when its parent is missing. The same dimensions and period yield comparable values; a late correction updates the intended result without overwriting a newer computation. ### What will we cover in a Treasure Data integration demo? Start with one workflow and a sample record from Databases, Tables and Master (Parent) Segments. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Treasure Data from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Treasure Data and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Treasure Data. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Treasure Data record changes.” - “Create a Genie that answers questions about our Treasure Data data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Treasure Data connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [SAP Business ByDesign and Treasure Data](https://www.stacksync.com/integrations/sap-business-bydesign-and-treasuredata) - [SQL Server and Treasure Data](https://www.stacksync.com/integrations/sql-server-and-treasuredata) - [Outreach and Treasure Data](https://www.stacksync.com/integrations/outreach-and-treasuredata) - [Magento and Treasure Data](https://www.stacksync.com/integrations/magento-and-treasuredata) - [Snowflake and Treasure Data](https://www.stacksync.com/integrations/snowflake-and-treasuredata) - [Oracle Fusion Cloud HCM and Treasure Data](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-treasuredata) - [Recurly and Treasure Data](https://www.stacksync.com/integrations/recurly-and-treasuredata) - [Linnworks and Treasure Data](https://www.stacksync.com/integrations/linnworks-and-treasuredata) ### CRM · 31 - [Treasure Data and 6sense](https://www.stacksync.com/integrations/6sense-and-treasuredata) - [Treasure Data and Affinity](https://www.stacksync.com/integrations/affinity-and-treasuredata) - [Treasure Data and Attio](https://www.stacksync.com/integrations/attio-and-treasuredata) - [Treasure Data and Chorusai](https://www.stacksync.com/integrations/chorusai-and-treasuredata) - [Treasure Data and Clearbit](https://www.stacksync.com/integrations/clearbit-and-treasuredata) - [Treasure Data and Close](https://www.stacksync.com/integrations/close-and-treasuredata) - [Treasure Data and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-treasuredata) - [Treasure Data and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-treasuredata) - [Treasure Data and Freshsales](https://www.stacksync.com/integrations/freshsales-and-treasuredata) - [Treasure Data and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-treasuredata) - [Treasure Data and Gong](https://www.stacksync.com/integrations/gong-and-treasuredata) - [Treasure Data and Gorgias](https://www.stacksync.com/integrations/gorgias-and-treasuredata) - [Treasure Data and HubSpot](https://www.stacksync.com/integrations/hubspot-and-treasuredata) - [Treasure Data and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-treasuredata) - [Treasure Data and Insightly](https://www.stacksync.com/integrations/insightly-and-treasuredata) - [Treasure Data and Intercom](https://www.stacksync.com/integrations/intercom-and-treasuredata) - [Treasure Data and Kommo](https://www.stacksync.com/integrations/kommo-and-treasuredata) - [Treasure Data and Outreach](https://www.stacksync.com/integrations/outreach-and-treasuredata) - [Treasure Data and Pipedrive](https://www.stacksync.com/integrations/pipedrive-and-treasuredata) - [Treasure Data and Salesforce](https://www.stacksync.com/integrations/salesforce-and-treasuredata) - [Treasure Data and Salesloft](https://www.stacksync.com/integrations/salesloft-and-treasuredata) - [Treasure Data and SAP Sales Cloud](https://www.stacksync.com/integrations/sap-sales-cloud-and-treasuredata) - [Treasure Data and Seismic](https://www.stacksync.com/integrations/seismic-and-treasuredata) - [Treasure Data and Shopify](https://www.stacksync.com/integrations/shopify-and-treasuredata) - [Treasure Data and SugarCRM](https://www.stacksync.com/integrations/sugarcrm-and-treasuredata) - [Treasure Data and Veeva CRM](https://www.stacksync.com/integrations/treasuredata-and-veeva-crm) - [Treasure Data and Vtiger CRM](https://www.stacksync.com/integrations/treasuredata-and-vtiger-crm) - [Treasure Data and Xactly](https://www.stacksync.com/integrations/treasuredata-and-xactly) - [Treasure Data and Zoho CRM](https://www.stacksync.com/integrations/treasuredata-and-zoho-crm) - [Treasure Data and Zoho SalesIQ](https://www.stacksync.com/integrations/treasuredata-and-zoho-salesiq) - [Treasure Data and ZoomInfo](https://www.stacksync.com/integrations/treasuredata-and-zoominfo) ### ERP · 24 - [Treasure Data and Acumatica](https://www.stacksync.com/integrations/acumatica-and-treasuredata) - [Treasure Data and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-treasuredata) - [Treasure Data and Cin7](https://www.stacksync.com/integrations/cin7-and-treasuredata) - [Treasure Data and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-treasuredata) - [Treasure Data and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-treasuredata) - [Treasure Data and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-treasuredata) - [Treasure Data and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-treasuredata) - [Treasure Data and Linnworks](https://www.stacksync.com/integrations/linnworks-and-treasuredata) - [Treasure Data and Microsoft Dynamics GP](https://www.stacksync.com/integrations/microsoft-dynamics-gp-and-treasuredata) - [Treasure Data and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/microsoft-dynamics-nav-and-treasuredata) - [Treasure Data and NetSuite](https://www.stacksync.com/integrations/netsuite-and-treasuredata) - [Treasure Data and Odoo](https://www.stacksync.com/integrations/odoo-and-treasuredata) - [Treasure Data and Plex ERP](https://www.stacksync.com/integrations/plex-erp-and-treasuredata) - [Treasure Data and QAD ERP](https://www.stacksync.com/integrations/qad-erp-and-treasuredata) - [Treasure Data and Sage 100](https://www.stacksync.com/integrations/sage-100-and-treasuredata) - [Treasure Data and Sage 300](https://www.stacksync.com/integrations/sage-300-and-treasuredata) - [Treasure Data and Sage Intacct](https://www.stacksync.com/integrations/sage-intacct-and-treasuredata) - [Treasure Data and Sage X3](https://www.stacksync.com/integrations/sage-x3-and-treasuredata) - [Treasure Data and SAP](https://www.stacksync.com/integrations/sap-and-treasuredata) - [Treasure Data and SAP Business ByDesign](https://www.stacksync.com/integrations/sap-business-bydesign-and-treasuredata) - [Treasure Data and SAP Business One](https://www.stacksync.com/integrations/sap-business-one-and-treasuredata) - [Treasure Data and SAP S/4HANA](https://www.stacksync.com/integrations/sap-s4hana-and-treasuredata) - [Treasure Data and Syspro](https://www.stacksync.com/integrations/syspro-and-treasuredata) - [Treasure Data and TikTok Shop](https://www.stacksync.com/integrations/tiktok-and-treasuredata) ### Database · 12 - [Treasure Data and Airtable](https://www.stacksync.com/integrations/airtable-and-treasuredata) - [Treasure Data and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-treasuredata) - [Treasure Data and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-treasuredata) - [Treasure Data and Firebase](https://www.stacksync.com/integrations/firebase-and-treasuredata) - [Treasure Data and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-treasuredata) - [Treasure Data and MongoDB](https://www.stacksync.com/integrations/mongodb-and-treasuredata) - [Treasure Data and MySQL](https://www.stacksync.com/integrations/mysql-and-treasuredata) - [Treasure Data and Neo4j](https://www.stacksync.com/integrations/neo4j-and-treasuredata) - [Treasure Data and PostgreSQL](https://www.stacksync.com/integrations/postgresql-and-treasuredata) - [Treasure Data and SAP HANA](https://www.stacksync.com/integrations/sap-hana-and-treasuredata) - [Treasure Data and SQL Server](https://www.stacksync.com/integrations/sql-server-and-treasuredata) - [Treasure Data and Supabase](https://www.stacksync.com/integrations/supabase-and-treasuredata) ### Data warehouse · 8 - [Treasure Data and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-treasuredata) - [Treasure Data and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-treasuredata) - [Treasure Data and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-treasuredata) - [Treasure Data and BigQuery](https://www.stacksync.com/integrations/bigquery-and-treasuredata) - [Treasure Data and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-treasuredata) - [Treasure Data and Databricks](https://www.stacksync.com/integrations/databricks-and-treasuredata) - [Treasure Data and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-treasuredata) - [Treasure Data and Snowflake](https://www.stacksync.com/integrations/snowflake-and-treasuredata) ### Accounting and finance · 13 - [Treasure Data and Adyen](https://www.stacksync.com/integrations/adyen-and-treasuredata) - [Treasure Data and Anaplan](https://www.stacksync.com/integrations/anaplan-and-treasuredata) - [Treasure Data and BILL](https://www.stacksync.com/integrations/bill-and-treasuredata) - [Treasure Data and Braintree](https://www.stacksync.com/integrations/braintree-and-treasuredata) - [Treasure Data and Chargebee](https://www.stacksync.com/integrations/chargebee-and-treasuredata) - [Treasure Data and Coupa](https://www.stacksync.com/integrations/coupa-and-treasuredata) - [Treasure Data and Navan](https://www.stacksync.com/integrations/navan-and-treasuredata) - [Treasure Data and QuickBooks](https://www.stacksync.com/integrations/quickbooks-and-treasuredata) - [Treasure Data and Ramp](https://www.stacksync.com/integrations/ramp-and-treasuredata) - [Treasure Data and Recurly](https://www.stacksync.com/integrations/recurly-and-treasuredata) - [Treasure Data and Stripe](https://www.stacksync.com/integrations/stripe-and-treasuredata) - [Treasure Data and Workday](https://www.stacksync.com/integrations/treasuredata-and-workday) - [Treasure Data and Zuora](https://www.stacksync.com/integrations/treasuredata-and-zuora) ### Developer tools · 9 - [Treasure Data and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-treasuredata) - [Treasure Data and Datadog](https://www.stacksync.com/integrations/datadog-and-treasuredata) - [Treasure Data and Jira](https://www.stacksync.com/integrations/jira-and-treasuredata) - [Treasure Data and JMS](https://www.stacksync.com/integrations/jms-and-treasuredata) - [Treasure Data and LDAP](https://www.stacksync.com/integrations/ldap-and-treasuredata) - [Treasure Data and New Relic](https://www.stacksync.com/integrations/newrelic-and-treasuredata) - [Treasure Data and Opsgenie](https://www.stacksync.com/integrations/opsgenie-and-treasuredata) - [Treasure Data and PagerDuty](https://www.stacksync.com/integrations/pagerduty-and-treasuredata) - [Treasure Data and RabbitMQ](https://www.stacksync.com/integrations/rabbitmq-and-treasuredata) ### E-commerce · 6 - [Treasure Data and Akeneo](https://www.stacksync.com/integrations/akeneo-and-treasuredata) - [Treasure Data and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-treasuredata) - [Treasure Data and EasyPost](https://www.stacksync.com/integrations/easypost-and-treasuredata) - [Treasure Data and Magento](https://www.stacksync.com/integrations/magento-and-treasuredata) - [Treasure Data and Shipwire](https://www.stacksync.com/integrations/shipwire-and-treasuredata) - [Treasure Data and Shopware](https://www.stacksync.com/integrations/shopware-and-treasuredata) ### Human resources · 11 - [Treasure Data and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-treasuredata) - [Treasure Data and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-treasuredata) - [Treasure Data and Hibob](https://www.stacksync.com/integrations/hibob-and-treasuredata) - [Treasure Data and Jobvite](https://www.stacksync.com/integrations/jobvite-and-treasuredata) - [Treasure Data and Lever](https://www.stacksync.com/integrations/lever-and-treasuredata) - [Treasure Data and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-treasuredata) - [Treasure Data and Paylocity](https://www.stacksync.com/integrations/paylocity-and-treasuredata) - [Treasure Data and SmartRecruiters](https://www.stacksync.com/integrations/smartrecruiters-and-treasuredata) - [Treasure Data and Success Factors](https://www.stacksync.com/integrations/success-factors-and-treasuredata) - [Treasure Data and UKG Pro](https://www.stacksync.com/integrations/treasuredata-and-ukg-pro) - [Treasure Data and UKG Ready](https://www.stacksync.com/integrations/treasuredata-and-ukg-ready) ### Marketing · 8 - [Treasure Data and Bingads](https://www.stacksync.com/integrations/bingads-and-treasuredata) - [Treasure Data and Cvent](https://www.stacksync.com/integrations/cvent-and-treasuredata) - [Treasure Data and Demandbase](https://www.stacksync.com/integrations/demandbase-and-treasuredata) - [Treasure Data and Eloqua](https://www.stacksync.com/integrations/eloqua-and-treasuredata) - [Treasure Data and Iterable](https://www.stacksync.com/integrations/iterable-and-treasuredata) - [Treasure Data and Marketo](https://www.stacksync.com/integrations/marketo-and-treasuredata) - [Treasure Data and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/salesforce-marketing-cloud-and-treasuredata) - [Treasure Data and Twitter Ads](https://www.stacksync.com/integrations/treasuredata-and-twitter-ads) ### Security and identity · 6 - [Treasure Data and Active Directory](https://www.stacksync.com/integrations/active-directory-and-treasuredata) - [Treasure Data and Auth0](https://www.stacksync.com/integrations/auth0-and-treasuredata) - [Treasure Data and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-treasuredata) - [Treasure Data and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-treasuredata) - [Treasure Data and Okta](https://www.stacksync.com/integrations/okta-and-treasuredata) - [Treasure Data and OneLogin](https://www.stacksync.com/integrations/onelogin-and-treasuredata) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)