Salesforce Marketing Cloud Connector

Sync subscribers, email sends, tracking events, journeys, Data Extensions, and Data Views from Salesforce Marketing Cloud (SFMC) into your warehouse. Authenticates via OAuth 2.0 Server-to-Server using an Installed Package.

SourceDestinationBronze

Start Free View Documentation

Why Supaflow

All connectors included

No per-connector fees. Every connector is available on every plan.

Pay for compute, not rows

Credit-based pricing. No per-row charges, no MAR surprises.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Server-to-Server OAuth via Installed Package

Authenticates using Client ID, Client Secret, and Subdomain from an SFMC Installed Package. Access tokens are automatically managed and refreshed.

Data Views Sync

Syncs SFMC system Data Views (_Sent, _Open, _Click, _Bounce, _Unsubscribe, _Complaint) consolidated into a single event table. Also syncs _Job, _Journey, _JourneyActivity, _Subscribers, and SMS/LINE tracking Data Views.

Data Extension Discovery

Automatically discovers standard, shared, Salesforce-synced, and synchronized Data Extensions. Each type is prefixed (ext_, shared_ext_, sf_ext_, sync_ext_) for identification.

Incremental Sync with 30-Day Windowing

Tracking event tables and list_subscribers are synced in 30-day windows for reliability. Configurable lookback (recommended 300-600 seconds) catches late-arriving events.

Supported Objects

Core Objects

subscribers

All subscriber records with email, status, and profile attributes.

lists

Email lists used to organize subscribers.

list_subscribers

Subscriber-to-list membership (synced in 30-day windows).

sends

Email send job records with delivery statistics.

triggered_send_definitions

Definitions for triggered (transactional) email sends.

emails

Email content and template definitions.

campaigns

Marketing campaign records.

journey

Journey Builder journeys with activities, triggers, and goals as JSON fields.

audit_event

Audit log of administrative actions.

security_event

Security events (logins, logouts, password changes).

Data Views (when enabled)

event

Consolidated email tracking from _Sent, _Open, _Click, _Bounce, _Unsubscribe, _Complaint.

data_view_job

Email send job data from _Job.

data_view_journey

Journey metadata from _Journey.

data_view_sms_tracking

SMS send and receive history (requires MobileConnect).

Data Extensions

ext_<name>

Standard Data Extensions you created in your Business Unit.

shared_ext_<name>

Data Extensions shared across Business Units.

sf_ext_<name>

Data Extensions synced from Salesforce CRM.

How It Works

Create an Installed Package in SFMC

In SFMC Setup > Platform Tools > Apps > Installed Packages, create a new package with an API Integration component using Server-to-Server type. Grant Data Extensions Read (Write for Data Views), Contacts Read, Journeys Read, Email Read, Automations Read/Write/Execute, and Tracking Events Read.

Enter credentials in Supaflow

Copy the Client ID, Client Secret, and Subdomain (e.g., mcxyz123abc from your SFMC URL) from the Installed Package into Supaflow.

Configure sync options

Set the Historical Sync Start Date (defaults to 180 days ago). Enable or disable Sync Data Views (enabled by default). Optionally configure Account ID, shared/Salesforce Data Extension inclusion, and rate limits.

Test and save

Click Test & Save to verify authentication and discover available objects including core SFMC objects, Data Views, and Data Extensions.

Use Cases

Email campaign analytics

Sync sends, tracking events (opens, clicks, bounces), and subscriber data into your warehouse to measure campaign performance alongside revenue data from your CRM.

Journey performance reporting

Load Journey Builder data with embedded activity, trigger, and goal JSON into your warehouse. Use Snowflake FLATTEN to extract individual journey activities for step-level analysis.

Data Extension consolidation

Replicate standard, shared, and Salesforce-synced Data Extensions into your warehouse for SQL-based segmentation and cross-extension joins.

Frequently Asked Questions

What SFMC permissions are required?

At minimum: Data Extensions Read, Contacts Read, Journeys Read, Email Read, and Tracking Events Read. For Data Views sync, also grant Automations Read/Write/Execute and Data Extensions Write.

What is the difference between Data Views and tracking event objects?

Data Views are SFMC system tables with richer data (e.g., IsUnique field). When Data Views sync is enabled (default), the six email tracking Data Views are consolidated into a single event table. When disabled, individual tracking event objects (sent_events, open_events, etc.) are available instead.

How do I find my SFMC subdomain?

Your subdomain appears in your SFMC login URL. For example, if your URL is https://mcxyz123abc.auth.marketingcloudapis.com, your subdomain is mcxyz123abc.

Can I sync SFMC data to Snowflake?

Yes. Supaflow loads SFMC data into Snowflake, S3, or other supported destinations. You can also run the pipeline natively inside Snowflake using Snowpark Container Services for zero data egress.

How does incremental sync work for SFMC?

Supaflow uses a 30-day windowed approach for tracking events: each sync fetches events from the last 30 days and merges them with existing data. For Data Extensions, full refresh is used since the SFMC API does not support filtered queries by modification date.