SALESFORCE MARKETING CLOUD → SNOWFLAKE
Replicate Salesforce Marketing Cloud data extensions, engagement events, subscribers, sends, and Journey Builder data into Snowflake.
Marketing Cloud spreads data across Data Extensions, subscriber and send objects, engagement events, journeys, assets, Business Units, and shared enterprise data. Supaflow handles Business Unit-aware discovery, shared Data Extensions, Salesforce-synchronized Data Extensions, high-volume engagement events, and Journey Builder data in one Snowflake pipeline. Every connector is included on every Supaflow plan — you pay only for the compute your pipelines consume.
Used by marketing analytics and lifecycle teams that need email send, open, click, and bounce data in Snowflake for attribution and unsubscribe analysis — with no per-row fees.
Every row below is an actual capability in the Salesforce Marketing Cloud connector, not a forward-looking promise.
| Feature | How it works | Limit / caveat |
|---|---|---|
| Object coverage | Data Extensions, shared Data Extensions, Salesforce-synchronized Data Extensions, subscribers, lists, sends, jobs, campaigns, email definitions, Journey Builder metadata, journey activity reporting, and engagement events such as sends, opens, clicks, bounces, unsubscribes, and complaints. | Some enterprise-level views require access from the enterprise parent Business Unit. Availability depends on your Marketing Cloud account type and permissions. |
| Authentication | OAuth 2.0 server-to-server authentication through your tenant-specific Marketing Cloud subdomain. Tokens refresh automatically during long syncs, and optional Business Unit scoping controls which records are visible. | Authentication requires a Marketing Cloud installed package with the right permissions for the data you want to read. |
| Marketing Cloud data access | Supaflow uses the right Marketing Cloud access path for each surface: Data Extensions, subscriber and send objects, Journey Builder metadata, assets, and engagement events. | — |
| Engagement event consolidation | Send, open, click, bounce, unsubscribe, and complaint events consolidate into one engagement-events table by default. Click events retain link-level uniqueness, so multiple clicks by the same subscriber in one email remain distinct. | If Data Views are unavailable for your account, Supaflow can sync the corresponding Marketing Cloud event objects as separate tables instead. |
| High-volume event windowing | High-volume engagement events sync in date windows for reliability against active accounts. Historical backfill start date is configurable. | Direct full pulls can time out on active accounts with large event history. |
| Incremental sync | Engagement and standard objects keep independent incremental positions. A configurable lookback window rechecks the tail of the previous run for late-arriving events. | — |
| Business Unit and shared data | Business Unit scoping, enterprise-shared Data Extensions, local Data Extensions, and Salesforce-synchronized Data Extensions are handled explicitly so discovery matches how your Marketing Cloud tenant is organized. | — |
| Composite primary keys | Data Extensions and Marketing Cloud objects with compound keys keep those keys in Snowflake so incremental merges and joins remain tied to the source model. | — |
| Rate limiting & retry | Supaflow handles Marketing Cloud rate limits, transient failures, and OAuth token refresh automatically during long syncs. | — |
| Destination | Lands directly in Snowflake with auto-generated tables per Data Extension and standard object. Composite primary keys preserved. Engagement events land as a unified table with composite IDs. | — |
Every Supaflow connector is included on every plan at no extra cost. You pay only for compute consumed, measured in Supaflow Credits (1 credit = 1 compute-hour on a Small node). No per-row fees.
Marketing Cloud data is split across tenant subdomains, Business Unit hierarchies, shared Data Extensions, standard objects, Journey Builder, engagement events, and retention policies. Supaflow handles that whole surface under the same usage-based pricing as every other source.
Send, open, click, bounce, unsubscribe, and complaint events can run into millions of rows per month for active accounts. Supaflow reads them in date windows and consolidates them into one engagement-events table by default, while preserving click-level uniqueness for attribution.
Every one of these is something our connector handles specifically. A generic pipeline built in Airflow or a basic ELT tool will hit at least three of them in production.
Failure mode: Marketing Cloud authentication and data access depend on the tenant-specific subdomain from your installed package. A pipeline that assumes a global hostname can authenticate against the wrong tenant or fail outright.
Evidence: Documented Marketing Cloud requirement; the subdomain comes from the installed package URL in your tenant.
Fix: Supaflow asks for the tenant subdomain during setup and uses it consistently across authentication and data reads.
Failure mode: In enterprise Marketing Cloud accounts, Business Unit scoping changes which Data Extensions and records are visible. A pipeline configured for the wrong scope can silently miss shared or parent-account data.
Evidence: Standard Marketing Cloud enterprise-hierarchy behavior. It trips up many teams adopting the connector for the first time.
Fix: Supaflow makes Business Unit scope, shared Data Extensions, and Salesforce-synchronized Data Extensions explicit setup choices.
Failure mode: A full pull of send, open, or click history for an active account can include millions of rows. Retrying the same full pull simply hits the same timeout again.
Evidence: Verified at typical SFMC event volumes (~1M+ events/day for active marketing accounts).
Fix: Supaflow syncs engagement events in date windows. Historical backfill is configurable and runs window by window, so a single failed window does not lose progress on the rest.
Failure mode: The same subscriber can click multiple links in the same email. Pipelines that key clicks too coarsely collapse legitimate click events into one row.
Evidence: Reproducible against any multi-link campaign.
Fix: Supaflow keeps link-level click identity so attribution and engagement analysis do not undercount multi-link activity.
Failure mode: Data Extensions can use row-based or extension-wide retention. Records vanish from the source on schedule, and pipelines that ignore retention settings cannot explain why rows disappeared upstream.
Evidence: Standard SFMC retention behavior, especially common on engagement and behavioral DEs.
Fix: Supaflow captures retention settings during discovery so operators can see which Data Extensions apply retention and configure destination retention to match.
Create a server-to-server installed package in Marketing Cloud, then provide the package credentials, tenant subdomain, and optional Business Unit scope in Supaflow.
SFMC source docs→Pick Data Extensions, subscribers, lists, sends, jobs, campaigns, email definitions, Journey Builder data, and engagement events based on your analytics use case.
Connect your Snowflake warehouse. Each DE and standard object becomes a Snowflake table with composite primary keys preserved.
Snowflake destination docs→Run on a cron or interval schedule. Standard objects use object-level incremental positions, and engagement events run in date windows for reliability.
Schedules docs→Supaflow authenticates with Marketing Cloud through your tenant subdomain, discovers the objects you select, reads Data Extensions, subscribers, sends, engagement events, and Journey Builder data, and lands them in Snowflake with source keys preserved.
Yes. Supaflow supports Business Unit scoping, enterprise-shared Data Extensions, and Salesforce-synchronized Data Extensions so discovery matches how your Marketing Cloud tenant is organized.
Send, open, click, bounce, unsubscribe, and complaint events sync in date windows for reliability. Historical backfill is configurable and runs window by window, so a single failed window does not lose progress on the rest. Click events retain link-level identity so multi-link clicks land distinctly.
Yes. Supaflow captures Data Extension retention settings during discovery. Operators can see which Data Extensions apply retention and configure destination retention to match.
Fivetran and Hevo often price by rows or volume. SFMC engagement event tables can run into millions of rows per month for active marketing accounts, making row-based pricing one of the worst categories of bill shock. Every Supaflow connector is included on every plan at no extra cost. You pay only for compute consumed, measured in Supaflow Credits (1 credit = 1 compute-hour on a Small node). No per-row fees. See the pricing page for the credit packages and free tier.
Yes. Journey metadata, entry events, journey activity reporting, and per-activity counts can land in Snowflake for cross-journey lifecycle and step-conversion analysis.
Yes. The sync agent runs in your own VPC if you want SFMC credentials, subscriber data, and engagement event content to stay in your network. The control plane is managed; the data plane can be managed or self-hosted.
The Salesforce Marketing Cloud source and Snowflake destination, plus other Supaflow connectors you can pair into a Snowflake pipeline.
Source connector overview and capabilities.
Destination connector overview and capabilities.
Pair with the core Salesforce CRM for cross-system reporting in Snowflake.
Other marketing-system source for cross-platform attribution in Snowflake.
CRM-side sync for orgs running both Salesforce and Marketing Cloud.
Browse the full catalog of sources and destinations.
Installed-package setup, OAuth scopes, tenant subdomain configuration, Business Unit setup, and troubleshooting.
Connect your Snowflake warehouse, role requirements, type mapping, and sync semantics.
Every connector is included on every plan. Pay only for compute consumed (Supaflow Credits).
Browse every Supaflow source and destination.
Every connector is included on every Supaflow plan — you pay only for the compute your pipelines consume. Data Extensions, subscribers, sends, engagement events, Journey Builder data, Business Unit-aware discovery, and retention-aware sync.