Marketo snapshot

A high-level look at Stitch's Marketo (v1.0) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release Status

Deprecated

 Supported By

Stitch
Stitch Plan

Paid

 Singer GitHub Repository

Marketo Repository

DATA SELECTION
Table Selection

Supported

 Column Selection

Unsupported
REPLICATION SETTINGS
Anchor Scheduling

Supported

 Table-level Reset

Unsupported
Configurable Replication Methods

Unsupported
TRANSPARENCY
Extraction Logs

Supported

 Loading Reports

Supported

Connecting Marketo

Marketo setup requirements

To set up Marketo in Stitch, you need:

  • A paid Stitch plan. While those currently in the Free Trial will also be able to set up Marketo, replication will be paused until a paid plan is selected after the trial ends.

  • Admin permissions in Marketo. Marketo Admin permissions are required to complete portions of the setup process.

Prior to set up, we recommend that you monitor your Marketo API call usage if other applications are also connected to your Marketo account. While Stitch is designed to use only a portion of your allotted API calls, replication may be impacted if numerous applications are using the API.

See the Replication section for more details.

Step 1: Create an API-Only User Role in Marketo

  1. Sign into your Marketo account.
  2. Click the Admin option.
  3. Under Admin, open the Security menu.
  4. Click Users & Roles.
  5. Click the Roles tab.
  6. Click New Role.
  7. In the Create New Role window, do the following:
    • Role Name - Enter a name for the role. If it’s specific to Stitch, make the name specific - something like “Stitch API Role.”
    • Description - Enter a description.
    • Permissions - Click the checkbox next to the Access API option.
  8. Click Create.

Step 2: Create a Stitch Marketo API User

Next, you’ll create an API User for Stitch. Creating a Stitch-specific user will ensure that Stitch is easily distinguishable in any logs or audits.

  1. Click the Admin option.
  2. Under Admin, open the Security menu.
  3. Click Users & Roles.
  4. In the Users tab, click Invite New User.
  5. In the INFO section, enter an email address and first and last name.
  6. Click Next.
  7. In the PERMISSIONS section, click the checkboxes next to the API User Role you created and the API Only option.
  8. Click Next.
  9. In the MESSAGE section, click the Send button to create the user.

Step 3: Create an API Custom Service in Marketo

To generate the API credentials you need to connect Stitch to Marketo, you need to create an API Custom Service and associate it with the Stitch API user.

  1. In Admin, open the Integration menu.
  2. Click LaunchPoint.
  3. Click New and then New Service.
  4. In the New Service window, do the following:
    • Display Name - Enter “Stitch”.
    • Service - Select Custom from the dropdown.
    • Description - Enter a description.
    • API Only User - Select the Stitch user you created.
  5. Click Create.
  6. After the service is created, it’ll display in the Installed Services grid. Click the View Details link to display your API credentials.
  7. Copy the Client ID and Secret into a text file.

Step 4: Whitelist Stitch's IP Addresses in Marketo

  1. In the Integration menu, click Web Services.
  2. In the IP Restrictions section, click the Edit button.

  3. In the Allowed Addresses field, paste one of the IP addresses listed below and then click Add.

    • 52.23.137.21/32

    • 52.204.223.208/32

    • 52.204.228.32/32

    • 52.204.230.227/32

  4. Repeat step 4 until all the Stitch IP addresses are added.
  5. Click the Save button.

Leave the Web Services page open - you’ll need it in the next step.

Step 5: Retrieve Your Marketo REST API Base URLs

  1. On the Web Services page, scroll down to the REST API section.
  2. In this section, find the Endpoint and Identity fields.
  3. Copy these URLs into the text file where you have your Client ID and Client Secret.

Step 6: Add Marketo as a Stitch data source

  1. Sign into your Stitch account.

  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Marketo icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Marketo” would create a schema called stitch_marketo in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Endpoint Base URL field, paste your Marketo REST API Endpoint URL.
  6. In the Identity Base URL field, paste your Marketo REST API Identity URL.
  7. In the Client ID field, paste your Marketo API Client ID.
  8. In the OAuth Client Secret field, paste your Marketo API Client Secret.

Step 7: Define the historical sync

The Sync Historical Data setting will define the starting date for your Marketo integration. This means that:

  • For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Marketo’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 8: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.

  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Marketo, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Marketo Replication

Stitch & Marketo Daily API Call Limits

By default, all Marketo accounts have a maximum number of 10,000 daily account calls. Stitch’s Marketo integration is designed to use up to 8,000 of these calls per day to allow other applications API access to your Marketo account.

When the 10,000 account call limit has been reached, Stitch will be unable to replicate any Marketo data until more API quota is available. If you find that the 10,000 call limit isn’t enough, contact Marketo support to inquire about raising the limit.

Marketo table schemas

activities

View table schema on GitHub
Replication Method :

Incremental

 Replication Key :

activityDate
Primary Key :

id

 API endpoint :

getLeadActivities

The activities table contains info about lead activities.

activities table schema

id
INTEGER

The ID of the activity.

activityDate
DATE-TIME

The date of the activity.

leadId
INTEGER

The ID of the lead associated with the activity.

activityTypeId
INTEGER

The ID of the activity type.

primaryAttributeValue
STRING

Value of the activity’s primary attribute.

primaryAttributeValueId
INTEGER

The ID of the activity’s primary attribute.

attributes
ARRAY

Secondary attributes of the activity.

Click to expand attributes

name
STRING

The name of the secondary attribute.

value
STRING

The value of the secondary attribute.
activities (table), attributes (attribute)

activity_types

View table schema on GitHub
Replication Method :

Full Table

 Primary Key :

id
API endpoint :

getAllActivityTypes

The activity_types table contains metadata about the activity types - form fill, web page visit, lead creation, and so on - available in Marketo.

Filter Deleted Leads

When joined with the activities table, you can use specific activity types to filter out deleted leads, assess list membership, and more. Here are a few noteworthy activity types:

  • Add to List and Remove from List - These events can be used to discover lead list membership.
  • Delete Lead - A delete lead event indicates leads that have been deleted. We recommend using this activity to filter out deleted leads.
  • Add a Lead to a Nurture Program, Change Nurture Track, and Change Nurture Cadence - These events can help you determine what nurture programs a lead is in and lead activity against that program.

activity_types table schema

id
INTEGER

The activity type ID.

name
STRING

The name of the activity type. Ex: Change Nurture Track

description
STRING

The description of the activity type.

primaryAttribute
OBJECT

Primary attributes of the activity type.

Click to expand primaryAttribute

name
STRING

The name of the primary attribute.

dataType
STRING

The data type of the primary attribute.
activity_types (table), primaryAttribute (attribute)

attributes
ARRAY

Secondary attributes of the activity type.

Click to expand attributes

name
STRING

The name of the secondary attribute.

dataType
STRING

The data type of the secondary attribute.
activity_types (table), attributes (attribute)

leads

Replication Method :

Incremental

 Replication Key :
Primary Key :

id

 API endpoint :

getLeads

The leads table contains info about your Marketo leads.

leads table schema

id
INTEGER

The ID of the lead.

acquiredBy
BOOLEAN

Indicates if the lead was acquired by the parent program.

isExhausted
BOOLEAN

Indicates if the lead is currently exhausted in the stream, if applicable.

membershipDate
DATE

The date the lead first became a member of the program.

nurtureCadence
STRING

Cadence of the parent stream, if applicable.

progressionStatus
STRING

The program status of the lead in the parent program.

reachedSuccess
BOOLEAN

Indicates if the the lead is in a success-status in the parent program.

reachedSuccessDate
STRING

The date the lead reached success in the parent program.

stream
STRING

The stream that the lead is a member of, if the parent program is an engagement program.

lists

View table schema on GitHub
Replication Method :

Incremental

 Replication Key :

updatedAt
Primary Key :

id

 API endpoint :

getLists

The leads table contains info about the static lists in your Marketo account.

Note: Due to some of the limitations in Marketo’s API, only static lists will be replicated.

lists table schema

id
INTEGER

The ID of the list.

updatedAt
DATE-TIME

The datetime when the list was most recently updated.

name
STRING

The name of the list.

description
STRING

The description of the list.

programName
STRING

The name of the program associated with the list.

workspaceName
STRING

The name of the parent workspace, if applicable.

createdAt
DATE-TIME

The datetime the list was created.
Related Troubleshooting
Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.