Load Salesforce Marketing Cloud data to DuckDB

Salesforce Marketing Cloud Engagement REST API provides access to marketing activities such as content management, journey builder interactions, and messaging orchestration. Everything needed to build a working Salesforce Marketing Cloud → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Salesforce Marketing Cloud to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Salesforce Marketing Cloud to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Salesforce Marketing Cloud API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Salesforce Marketing Cloud API at a glance

These values come from the Salesforce Marketing Cloud API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Salesforce Marketing Cloud API?

Requests require an OAuth 2.0 Bearer token provided in the Authorization header. The token is obtained by POSTing credentials to the tenant-specific authentication base URL.

1. Get your credentials

1. Log in to Salesforce Marketing Cloud Engagement and navigate to Setup by clicking your user profile icon in the upper-right corner. 2. Under the Platform Tools menu, go to Apps > Installed Packages. 3. Click New to create a new package, then give it a name and description. 4. After saving, scroll to the Components section and click Add Component. 5. Select API Integration and then Server-to-Server. 6. Select the necessary scopes (permissions) for your integration and click Save. 7. Once saved, locate the component details page for your integration to retrieve the Client ID, Client Secret, and Authentication Base URI.

2. Add them to .dlt/secrets.toml

Copy
[sources.salesforce_marketing_cloud_source]
client_id = "your_client_id_here"
client_secret = "your_client_secret_here"
auth_base_uri = "https://your_subdomain.auth.marketingcloudapis.com"
rest_base_uri = "https://your_subdomain.rest.marketingcloudapis.com"
account_id = "your_account_id_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Salesforce Marketing Cloud data can I load into DuckDB?

These are the Salesforce Marketing Cloud endpoints dlt can load into DuckDB:

---

How do I load only new Salesforce Marketing Cloud records?

The Salesforce Marketing Cloud API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "data_extensions", "endpoint": {
    "path": "/data/v1/customobjects",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Salesforce Marketing Cloud pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v2/token and /platform/v1/endpoints from the Salesforce Marketing Cloud API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def salesforce_marketing_cloud_source(client_id=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{subdomain}.rest.marketingcloudapis.com",
            "auth": {"type": "bearer", "token": client_id},
        },
        "resources": [
            {"name": "data_extensions", "endpoint": {"path": "/data/v1/customobjects", "data_selector": "items"}},
            {"name": "data_extension_data", "endpoint": {"path": "/data/v1/customobjectdata/key/{key}/rowset", "data_selector": "items"}}
        ],
    }
    yield from rest_api_resources(config)


def load_salesforce_marketing_cloud_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="salesforce_marketing_cloud_pipeline",
        destination="duckdb",
        dataset_name="salesforce_marketing_cloud_data",
    )
    load_info = pipeline.run(salesforce_marketing_cloud_source())
    print(load_info)


if __name__ == "__main__":
    load_salesforce_marketing_cloud_to_duckdb()

Run it with python salesforce_marketing_cloud_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Salesforce Marketing Cloud data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("salesforce_marketing_cloud_pipeline").dataset()
df = data.data_extension_data.df()
print(df.head())

SQL:

Copy
SELECT * FROM salesforce_marketing_cloud_data.data_extension_data LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Salesforce Marketing Cloud to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Salesforce Marketing Cloud loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Salesforce Marketing Cloud data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack