Marketo connector

Beta

This feature is in Beta. Workspace admins can enable it from the Previews page by opting into the Lakeflow Connect for Marketo preview. See Manage Databricks previews.

Use the managed Marketo connector in Lakeflow Connect to ingest lead, activity, static list, and custom object data from Adobe Marketo Engage into Databricks.

Feature availability

The connector is available on AWS, Azure, and GCP with the following feature support:

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported Supported for the leads, activity_<typeId>, and custom object tables. The static_lists table is refreshed with a full snapshot on each pipeline update.
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported Supported for the leads, activity_<typeId>, and custom object tables. The static_lists table is refreshed with a full snapshot on each pipeline update.
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported

Authentication methods

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Supported Adobe Marketo Engage custom service Client ID and Client Secret.
Basic authentication (username/password)	Not supported

Authentication method	Availability
OAuth U2M	Not supported
OAuth M2M	Supported Adobe Marketo Engage custom service Client ID and Client Secret.
Basic authentication (username/password)	Not supported

Ingest from Marketo in 3 steps

Before you start, review the Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

1. Configure Marketo for ingestion (Admins). Set up Marketo to authenticate with Databricks.
2. Create a Unity Catalog connection (Admins). Create a connection in Catalog Explorer so non-admins can create pipelines.
3. Create an ingestion pipeline (Admins or non-admins). Select any supported interface and create a pipeline from an existing connection.