Marketo connector reference

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

Find reference information for the Marketo connector, including supported tables, connector options, and destination schemas.

Supported source tables

The Marketo connector supports the following source tables:

Source table	Primary key	Description	Sync mode	Cursor field
leads	id	Person records in your Adobe Marketo Engage instance, including identity, demographic, and lead-scoring fields. Ingested through the Bulk Extract API.	Incremental	updatedAt
static_lists	id	Static lists used for audience targeting and segmentation. Ingested through the REST API.	Full refresh only
activity_<typeId>	marketoGUID	One table per Adobe Marketo Engage activity type, where <typeId> is the numeric activity type ID (for example, activity_1). Each table shares a set of fixed columns and adds type-specific attribute columns. Ingested through the Bulk Extract API.	Incremental	activityDate
<customObjectApiName>	marketoGUID	One table per custom object, named by its Adobe Marketo Engage API name. The schema is discovered at run time. Ingested through the Bulk Extract API.	Incremental	updatedAt

Source table	Primary key	Description	Sync mode	Cursor field
leads	id	Person records in your Adobe Marketo Engage instance, including identity, demographic, and lead-scoring fields. Ingested through the Bulk Extract API.	Incremental	updatedAt
static_lists	id	Static lists used for audience targeting and segmentation. Ingested through the REST API.	Full refresh only
activity_<typeId>	marketoGUID	One table per Adobe Marketo Engage activity type, where <typeId> is the numeric activity type ID (for example, activity_1). Each table shares a set of fixed columns and adds type-specific attribute columns. Ingested through the Bulk Extract API.	Incremental	activityDate
<customObjectApiName>	marketoGUID	One table per custom object, named by its Adobe Marketo Engage API name. The schema is discovered at run time. Ingested through the Bulk Extract API.	Incremental	updatedAt

Connector options

Set the following option on a table object in your pipeline definition. See Set the initial sync start date.

Option	Description
sync_start_date	The initial sync start date, in YYYY-MM-DD format. This is the earliest date from which to sync historical data. If you don't set it, the connector ingests two years of history by default. 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.

Option	Description
sync_start_date	The initial sync start date, in YYYY-MM-DD format. This is the earliest date from which to sync historical data. If you don't set it, the connector ingests two years of history by default. 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.

Destination table schemas

leads

Primary key: id Cursor field: updatedAt

Field	Data type
id	STRING
firstName	STRING
lastName	STRING
email	STRING
leadScore	BIGINT
unsubscribed	BOOLEAN
leadSource	STRING
company	STRING
createdAt	TIMESTAMP
updatedAt	TIMESTAMP

Field	Data type
id	STRING
firstName	STRING
lastName	STRING
email	STRING
leadScore	BIGINT
unsubscribed	BOOLEAN
leadSource	STRING
company	STRING
createdAt	TIMESTAMP
updatedAt	TIMESTAMP

static_lists

Primary key: id Sync mode: Full refresh only

Field	Data type
id	BIGINT
name	STRING
description	STRING
createdAt	TIMESTAMP
updatedAt	TIMESTAMP
programName	STRING
workspaceName	STRING

Field	Data type
id	BIGINT
name	STRING
description	STRING
createdAt	TIMESTAMP
updatedAt	TIMESTAMP
programName	STRING
workspaceName	STRING

activity_<typeId>

Primary key: marketoGUID Cursor field: activityDate

Every activity table includes the following fixed columns:

Field	Data type
marketoGUID	STRING
leadId	STRING
activityDate	TIMESTAMP
activityTypeId	STRING
campaignId	STRING
primaryAttributeValueId	STRING
primaryAttributeValue	STRING

Field	Data type
marketoGUID	STRING
leadId	STRING
activityDate	TIMESTAMP
activityTypeId	STRING
campaignId	STRING
primaryAttributeValueId	STRING
primaryAttributeValue	STRING

Each activity table also adds one column per attribute defined for that activity type in Adobe Marketo Engage. The connector discovers these attributes from Adobe Marketo Engage metadata, keeps their original names, and maps their types using the Adobe Marketo Engage data type to Spark type mapping.

<customObjectApiName>

Primary key: marketoGUID Cursor field: updatedAt

Custom object schemas are discovered at run time from Adobe Marketo Engage and vary by instance. Every custom object table includes marketoGUID, createdAt, and updatedAt, followed by the object-specific fields defined in your subscription. Field types follow the Adobe Marketo Engage data type to Spark type mapping.

Adobe Marketo Engage data type to Spark type mapping

The connector maps Adobe Marketo Engage data types to Spark types for all columns discovered at run time, such as activity attributes and custom object fields. Matching is case-insensitive.

Adobe Marketo Engage data type	Spark type
integer	BIGINT
string, text, email, url, phone, reference	STRING
float	DOUBLE
currency	DECIMAL(38, 4)
boolean	BOOLEAN
date	DATE
datetime	TIMESTAMP
array, email_list	ARRAY<STRING>
Any other type	STRING

Adobe Marketo Engage data type	Spark type
integer	BIGINT
string, text, email, url, phone, reference	STRING
float	DOUBLE
currency	DECIMAL(38, 4)
boolean	BOOLEAN
date	DATE
datetime	TIMESTAMP
array, email_list	ARRAY<STRING>
Any other type	STRING