Marketo Connector for Data Prep¶
User Persona: Data Prep User or Marketo Admin
This document covers all configuration fields available during connector setup. Some fields may have already been filled out by your Administrator at an earlier step of configuration and may not be visible to you. For more information on Data Prep's connector framework, see Data Prep Connector setup. Also, your Admin may have named this connector something else in the list of Data Sources.
Configure Data Prep¶
This connector allows you to connect to Marketo as an import source. The following fields are used to define the connection parameters.
- Name: Name of the data source as it will appear to users in the UI.
- Description: Description of the data source as it will appear to users in the UI.
You can connect Data Prep to multiple Marketo accounts. Using a descriptive name can be a big help to users in identifying the appropriate data source. If you are a Data Prep SaaS customer, inform Data Prep DevOps how you would like this set.
- Marketo REST Endpoint: Your Marketo REST API Endpoint.
- OAuth Client ID: The Client ID of your service in Marketo.
- OAuth Client Secret: The Client Secret of your service in Marketo.
- Timeout: The number of seconds to wait until a timeout error cancels a running operation. The default is 60 seconds, for most situations this is adequate.
If you connect to Marketo through a proxy server, these fields define the proxy details.
Web Proxy: 'None' if no proxy is required or 'Proxied' if the connection to the Marketo REST Endpoint should be made via a proxy server. If a web proxy server is required, the following fields are required to enable a proxied connection.
Proxy host: The host name or IP address of the web proxy server.
Proxy port: The port on the proxy server for Data Source.
Proxy username: The username for the proxy server.
Proxy password: The password for the proxy server.
Leave username and password blank for an unauthenticated proxy connection.
Marketo Connector leverages the Marketo REST API and OAuth. This step must be completed by a Marketo Admin.
In order to establish connectivity, the Marketo Administrator must:
- Create a "Custom Service” in Marketo.
- Obtain OAuth credentials for the "Custom Service" to identify the client (Data Prep Connector) that is accessing Marketo.
Create a "Custom Service" in Marketo¶
A custom service is required to connect to Marketo using the REST API. The below steps will guide you in creating a custom service.
- Navigate to the admin area of your Marketo application.
- Click Users & Roles in the Security section.
- Select the Roles tab and click New Role to create a new Role.
- Enter a Role Name and select the permissions for the Role. The Access API permissions are specific to the REST API.
- Now that an API Role is created, select the Users tab and click Invite New User.
- Enter the new user information and select the role that was just created with API access. The API Only option can be selected to denote the user as an API Only user.
- Now that a new user has been created, a new service will need to be created. Click the LaunchPoint option (Admin > Integration > LaunchPoint).
- Click New Service.
- Select the Custom service type and enter a display name and description.
- Select the user you created.
Obtain the OAuthClientId and OAuthClientSecret Values¶
To obtain the OAuthClientId and OAuthClientSecret, navigate to the LaunchPoint option on the Admin area. Click the View Details link for the desired service. A window containing the authentication credentials is displayed.
Obtain the REST Endpoint URL¶
The REST Endpoint can be found on your Marketo Admin area on the Integration -> Web Services option in the REST API section. Note the Identity Endpoint will not be needed.
Data Import Information¶
Via Browsing & Via SQL Query¶
See the following table for the list of visible Objects and example SQL queries.
Marketo Connector Data Objects:¶
Some objects in Marketo may or may not be present based on your configuration and some may run into the 500 column import maximum (this is a default setting, please reach out to your Data Prep Customer Success contact if this is inadequate). There are also several SQL Query examples in the table below.
|Activities||Custom Activities for your Marketo organization.
|ActivityBulkExports||Returns a list of activity export jobs that were created in the past 7 days.|
|Campaigns||Campaigns for a Marketo organization.|
|Channels||Channels for a Marketo organization.|
|Companies||Companies for a Marketo organization.
This object is only available for Marketo subscriptions which do not have a native CRM sync enabled.
|CustomObjects||Custom objects for a Marketo organization.|
|Emails||Emails for a Marketo organization.|
|LeadBulkExports||List of lead export jobs that were created in the past 7 days.|
|LeadPartitions||Lead Partitions for a Marketo organization.|
|Leads||Leads for a Marketo organization.
Based on your organization's Marketo configuration, the Lead object may contain > 500 columns. You may receive a truncation error when attempting to import > 500 columns using the default Data Prep Library configuration.
|Lists||Lists for a Marketo organization.|
|NamedAccounts||Named Accounts for a Marketo organization.
|Opportunities||Opportunities for a Marketo organization.
|OpportunityRoles||Opportunity Roles for a Marketo organization.
|Programs||Programs for a Marketo organization.
|SalesPersons||Sales Persons for a Marketo organization.
|Tags||Tags for a Marketo organization|