| title | Copy data from Marketo (Preview) | ||
|---|---|---|---|
| description | Learn how to copy data from Marketo to supported sink data stores using a copy activity in an Azure Data Factory or Synapse Analytics pipeline. | ||
| titleSuffix | Azure Data Factory & Azure Synapse | ||
| ms.subservice | data-movement | ||
| ms.topic | how-to | ||
| ms.date | 01/26/2025 | ||
| ms.author | makromer | ||
| author | kromerm | ||
| ms.custom |
|
[!INCLUDEappliesto-adf-asa-md]
Important
This connector is at End of Support stage. You are recommended to migrate to ODBC connector by installing a driver.
This article outlines how to use the Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Marketo. It builds on the copy activity overview article that presents a general overview of copy activity.
This Marketo connector is supported for the following capabilities:
| Supported capabilities | IR |
|---|---|
| Copy activity (source/-) | ① ② |
| Lookup activity | ① ② |
① Azure integration runtime ② Self-hosted integration runtime
For a list of data stores that are supported as sources/sinks, see the Supported data stores table.
Currently, Marketo instance which is integrated with external CRM is not supported.
Note
This Marketo connector is built on top of the Marketo REST API. Be aware that the Marketo has concurrent request limit on service side. If you hit errors saying "Error while attempting to use REST API: Max rate limit '100' exceeded with in '20' secs (606)" or "Error while attempting to use REST API: Concurrent access limit '10' reached (615)", consider to reduce the concurrent copy activity runs to reduce the number of requests to the service.
[!INCLUDE data-factory-v2-connector-get-started]
Use the following steps to create a linked service to Marketo in the Azure portal UI.
-
Browse to the Manage tab in your Azure Data Factory or Synapse workspace and select Linked Services, then click New:
:::image type="content" source="media/doc-common-process/new-linked-service.png" alt-text="Screenshot of creating a new linked service with Azure Data Factory UI.":::
:::image type="content" source="media/doc-common-process/new-linked-service-synapse.png" alt-text="Screenshot of creating a new linked service with Azure Synapse UI.":::
-
Search for Marketo and select the Marketo connector.
:::image type="content" source="media/connector-marketo/marketo-connector.png" alt-text="Screenshot of the Marketo connector.":::
-
Configure the service details, test the connection, and create the new linked service.
:::image type="content" source="media/connector-marketo/configure-marketo-linked-service.png" alt-text="Screenshot of linked service configuration for Marketo.":::
The following sections provide details about properties that are used to define Data Factory entities specific to Marketo connector.
The following properties are supported for Marketo linked service:
| Property | Description | Required |
|---|---|---|
| type | The type property must be set to: Marketo | Yes |
| endpoint | The endpoint of the Marketo server. (i.e. 123-ABC-321.mktorest.com) | Yes |
| clientId | The client ID of your Marketo service. | Yes |
| clientSecret | The client secret of your Marketo service. Mark this field as a SecureString to store it securely, or reference a secret stored in Azure Key Vault. | Yes |
| useEncryptedEndpoints | Specifies whether the data source endpoints are encrypted using HTTPS. The default value is true. | No |
| useHostVerification | Specifies whether to require the host name in the server's certificate to match the host name of the server when connecting over TLS. The default value is true. | No |
| usePeerVerification | Specifies whether to verify the identity of the server when connecting over TLS. The default value is true. | No |
Example:
{
"name": "MarketoLinkedService",
"properties": {
"type": "Marketo",
"typeProperties": {
"endpoint" : "123-ABC-321.mktorest.com",
"clientId" : "<clientId>",
"clientSecret": {
"type": "SecureString",
"value": "<clientSecret>"
}
}
}
}For a full list of sections and properties available for defining datasets, see the datasets article. This section provides a list of properties supported by Marketo dataset.
To copy data from Marketo, set the type property of the dataset to MarketoObject. The following properties are supported:
| Property | Description | Required |
|---|---|---|
| type | The type property of the dataset must be set to: MarketoObject | Yes |
| tableName | Name of the table. | No (if "query" in activity source is specified) |
Example
{
"name": "MarketoDataset",
"properties": {
"type": "MarketoObject",
"typeProperties": {},
"schema": [],
"linkedServiceName": {
"referenceName": "<Marketo linked service name>",
"type": "LinkedServiceReference"
}
}
}For a full list of sections and properties available for defining activities, see the Pipelines article. This section provides a list of properties supported by Marketo source.
To copy data from Marketo, set the source type in the copy activity to MarketoSource. The following properties are supported in the copy activity source section:
| Property | Description | Required |
|---|---|---|
| type | The type property of the copy activity source must be set to: MarketoSource | Yes |
| query | Use the custom SQL query to read data. For example: "SELECT * FROM Activity_Types". |
No (if "tableName" in dataset is specified) |
Example:
"activities":[
{
"name": "CopyFromMarketo",
"type": "Copy",
"inputs": [
{
"referenceName": "<Marketo input dataset name>",
"type": "DatasetReference"
}
],
"outputs": [
{
"referenceName": "<output dataset name>",
"type": "DatasetReference"
}
],
"typeProperties": {
"source": {
"type": "MarketoSource",
"query": "SELECT top 1000 * FROM Activity_Types"
},
"sink": {
"type": "<sink type>"
}
}
}
]To learn details about the properties, check Lookup activity.
For a list of data stores supported as sources and sinks by the copy activity, see supported data stores.