Connecting to Marketo

Marketo is a cloud lead management and marketing solution.

Data integration: Skyvia supports importing data to and from Marketo, exporting Marketo data to CSV files, replicating Marketo data to relational databases, and synchronizing Marketo data with other cloud apps and relational databases.

Backup: Skyvia Backup supports Marketo backup.

Query: Skyvia Query supports Marketo.

Marketo-Specific Features and Limitations

Marketo API support selecting data from certain objects only by their identifying fields. These are the following objects: Companies, Opportunities, OpportunityRoles, SalesPersons, and all the custom objects. Thus, you cannot get data from these tables unless values of some of their identifying fields of the records you want to get are explicitly specified. You can specify these IDs, for example, by filtering data from these tables by IDs.

Marketo Connections

To connect to Marketo, you need to specify the domain to connect to, client id, and client secret.

marketo-connection-new

You need to specify the following parameters for Marketo connection:

Name - connection name that will be used to identify the connection on the Connections page and when selecting a connection for a package.
Client ID - a GUID value, representing Marketo API client id.
Client Secret - Marketo API client secret. To configure access to Marketo and get client id and client secret for the connection, see this instruction in Marketo documentation.
Domain - the address of your Marketo subdomain.
Metadata Cache - Determines how often to update cached metadata for the connection. By default, Skyvia caches metadata of available objects for cloud sources. You can configure how often the cache is refreshed automatically or reset in manually on the Connection Details page of the corresponding connection by clicking the Clear link in the Metadata cache parameter in the Parameters pane. The following values are available for this setting:
oDisabled - the metadata cache is not created, and metadata are queried automatically whenever the connection is opened.
oOne Hour - the metadata cache expires after one hour since the previous refresh, and it is refreshed after this when the connection is opened.
oOne Day - the metadata cache expires after one day since the previous refresh, and it is refreshed after this when the connection is opened.
oOne Week - the metadata cache expires after one week since the previous refresh, and it is refreshed after this when the connection is opened.
oOne Month - the metadata cache expires after one month since the previous refresh, and it is refreshed after this when the connection is opened.
oInfinite - the cache is never reset automatically. Default value.