Marketo (Edge)

Configure Marketo as a Source in your Pipeline

Perform the following steps to configure your Marketo Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Marketo.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Marketo Source.

   • In the Connect to Marketo section:

     • REST API Endpoint: The REST API Endpoint of your Marketo instance. For example, https://123-ABC-456.mktorest.com/rest.

     • REST API Identity: The REST API Identity of your Marketo instance. For example, https://123-ABC-456.mktorest.com/identity.

     • Client ID: The Client ID of the LaunchPoint custom service.

     • Client Secret: The Client Secret of the custom service.

     • REST API Call Limit (Optional): The maximum number of Marketo REST API calls that Hevo can make in a day. Leave it blank if you do not want to limit the number of calls. Hevo recommends allowing at least 8,000 calls a day. Read API Request Limits.

7. Click Test & Continue to test the connection to your Marketo Source. Once the test is successful, you can proceed to set up your Destination.

   When you click this button, Hevo checks that the Client ID and Client Secret are valid by obtaining an access token from the REST API Identity URL and reading the activity types of your Marketo instance.

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To ingest a child object, you must also select its parent object. For example, to ingest the List Membership object, you must also select the List object. The Data Model lists the child objects of each parent object.

In the first run of the Pipeline, Hevo ingests all the data available for the selected objects in your Marketo instance. In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:

Hevo ingests the child objects of a parent object along with it.

Hevo reads leads using the Marketo Bulk Lead Extract API. In the first run, Hevo exports the leads by the time they were created. In the subsequent runs, it exports the leads that were updated since the previous run. Hevo ingests all the fields of the Lead object that Marketo lists for your instance, including your custom lead fields.

Hevo reads each activity object using the time of the activity. In the first run, Hevo ingests all the activities that Marketo retains for your instance. Marketo deletes older activities as per its data retention policy, so Hevo cannot ingest activities older than the retention period. If you pause the Pipeline for longer than the retention period, the activities of that period are not ingested.

Pipelines with this Source support only the Merge load mode.

API Request Limits

Marketo allows 50,000 API calls per day for a subscription, 100 API calls per 20 seconds, and up to 10 concurrent API calls for an instance. The daily limit resets at 12:00 AM CST. Read Marketo REST API. These limits are shared by all the applications that use the Marketo API of your instance.

Hevo counts its API calls against the REST API Call Limit that you specify while configuring the Source, using the daily API usage that Marketo reports for the API-only user. If the limit is reached, Hevo stops ingesting the objects for the day and resumes from the last saved position after the Marketo day resets. If Marketo returns a rate limit error, Hevo waits and retries the request. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

Click to view ERD

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline: