Marketo connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Marketo ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
What tables does the connector support?
The connector supports four table types:
leadsstatic_listsactivity_<typeId>(one table per Adobe Marketo Engage activity type)- Custom objects (one table per custom object, named by its Adobe Marketo Engage API name)
For the schema of each table, see Supported source tables.
Does the connector support incremental ingestion?
Yes, for a subset of tables. The leads, activity_<typeId>, and custom object tables are ingested incrementally using a cursor field (updatedAt, activityDate, and updatedAt, respectively). The static_lists table is refreshed with a full snapshot on each pipeline update.
How much historical data does the connector ingest?
By default, the connector ingests two years of historical data. To change the backfill window, set the sync_start_date option in YYYY-MM-DD format. This option applies only to the initial backfill: after a table's first sync, changing it has no effect unless you run a full refresh. See Set the initial sync start date.
What Adobe Marketo Engage access does the connector require?
The connector authenticates with OAuth 2.0 machine-to-machine (M2M) credentials from a Adobe Marketo Engage custom service. You need administrator access to the Adobe Marketo Engage Admin area to create an API-only user with the Access API permission and register the custom service. See Configure Adobe Marketo Engage.