Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
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 Azure 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 Azure 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 |
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 |
Ingest from Marketo in 3 steps
Before you start, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.
- Configure Marketo for ingestion (Admins). Set up Marketo to authenticate with Azure Databricks.
- Create a Unity Catalog connection (Admins). Create a connection in Catalog Explorer so non-admins can create pipelines.
- Create an ingestion pipeline (Admins or non-admins). Select any supported interface and create a pipeline from an existing connection.