Skip to content
Data warehouse ⇄ Marketing

Apache Kylin to Salesforce Marketing Cloud integration — real-time data sync

Keep Apache Kylin and Salesforce Marketing Cloud 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 Apache Kylin and Salesforce Marketing Cloud

Flow Apache Kylin data into Salesforce Marketing Cloud in real time — no exports, no schedulers, no custom scripts.

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

Apache Kylin is where your team models customers, product usage, and revenue into trusted tables; Salesforce Marketing Cloud runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Common use cases

  • 01 Expose Kylin query results to operational dashboards without granting access to the underlying Hadoop data.
  • 02 Sync Kylin aggregates into a cloud warehouse to combine them with data Kylin does not cover.
  • 03 Sync Contacts and Subscriber Key subscription status between Marketing Cloud and a CRM so suppression and opt-in state stay current before the next send.
  • 04 Stream Event Notification Service callbacks for transactional sends, bounces, opens, and clicks into a database in near real time alongside CRM contact records.

Common sync patterns

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Apache Kylin holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in Apache Kylin appear on the matching record in Salesforce Marketing Cloud, so targeting, routing, and personalization use up-to-date context.

Activate a modeled audience

A segment or score built in Apache Kylin — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Salesforce Marketing Cloud, so campaigns target the people your data actually points to instead of a static export.

What you can sync between Apache Kylin and Salesforce Marketing Cloud

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.

Apache Kylin objects Salesforce Marketing Cloud objects How this pairing syncs
Build Jobs Batch jobs that compute or refresh segments, monitored via the REST API. Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. Build Jobs is specific to Apache Kylin and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Projects Top-level workspaces that group models, tables, and jobs. Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. Projects is specific to Apache Kylin and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Models Star-schema definitions over source tables that determine what can be queried. Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Models is specific to Apache Kylin and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Cubes / Indexes Pre-computed aggregate structures that answer queries at low latency. Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). Cubes / Indexes is specific to Apache Kylin and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Source Tables Hive or other upstream tables that builds read from. Data Extensions Custom relational tables that store subscriber, audience, and arbitrary business data; rows are read via GET /data/v1/customobjectdata or SOAP Retrieve and upserted via the synchronous rowset PUT or the async /data/v1/async/dataextensions rows endpoint. This is the primary two-way surface. Source Tables is specific to Apache Kylin and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Segments Time-ranged build units that partition pre-computed data. Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. Segments is specific to Apache Kylin and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

How changes propagate between Apache Kylin and Salesforce Marketing Cloud

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.

Apache Kylin Salesforce Marketing Cloud Interval-based propagation

DetectionStacksync polls Apache Kylin for changes on an incremental schedule, reading only records changed since the previous pass. Data freshness follows segment build and refresh jobs, so integrations poll query results.

DeliveryEach detected change is written to Salesforce Marketing Cloud through its API, with automatic retries and rate-limit backoff.

Salesforce Marketing Cloud Apache Kylin Sub-second propagation

DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.

DeliveryApache Kylin does not accept inbound record writes, so this direction carries requests rather than records: Apache Kylin's output flows back as field updates on the originating Salesforce Marketing Cloud records.

Rate-limit considerations

  • Apache Kylin: No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage.
  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
What ships with Apache Kylin ⇄ Salesforce Marketing Cloud

Connect Apache Kylin and Salesforce Marketing Cloud for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Kylin–Salesforce Marketing Cloud connection.

Real-time

Real-time sync

Changes in Apache Kylin or Salesforce Marketing Cloud instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Kylin or Salesforce Marketing Cloud 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 Apache Kylin or Salesforce Marketing Cloud record.

Observability

Monitoring

Track your Apache Kylin ⇄ Salesforce Marketing Cloud sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Kylin and Salesforce Marketing Cloud.

How the Apache Kylin and Salesforce Marketing Cloud connectors work

Apache Kylin

Integration surface
SQL over JDBC/ODBC plus a REST API for queries and administration
Authentication
Username/password (HTTP basic authentication on the REST API)
Change detection
Not applicable for row-level capture; data freshness follows segment build and refresh jobs, so integrations poll query results
Capabilities
read
Rate limits
No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
How it works

How to connect Apache Kylin to Salesforce Marketing Cloud — 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 Apache Kylin and Salesforce Marketing Cloud 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
    Apache Kylin connected
    Salesforce Marketing Cloud connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Kylin and Salesforce Marketing Cloud 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 · Apache Kylin ⇄ Salesforce Marketing Cloud
    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
    Apache Kylin Salesforce Marketing Cloud
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Kylin and Salesforce Marketing Cloud 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 352 integrations available for Apache Kylin and Salesforce Marketing Cloud.

Popular · 8 of 352
All Apache Kylin integrations All Salesforce Marketing Cloud 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