Release Status Released Supported By Stitch
Availability Paid Status Page Marketo Status Page
Default Historical Sync 1 year Default Replication Frequency 12 hours
Whitelisting Tables and columns Destination Incompatibilities None

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 ensures 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.
  9. In the Max Daily API Calls field, either keep the default 40,000 value or use a larger number based on your Marketo API Quota

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 help prevent overages, 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 REST API Call Limits

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

This can be increased or decreased using the integration’s Max Daily API Calls field.

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

Activities and Leads Replication

To efficiently replicate activity and lead data, Stitch’s Marketo integration uses the Bulk API to extract data. While this approach is more efficient than the REST API, it may also impact your overall row count and frequency with which data is replicated.

Leads Replication and Marketo Corona

To incrementally replicate leads data, Marketo requires the authorizing account to have a feature called Corona. Corona allows Stitch to use an updatedAt query parameter to extract only new and updated data from the leads endpoint.

If your account doesn’t have Corona enabled, the leads table will use Full Table Replication.

Additionally, the following message will surface in the extraction logs:

Your account does not have Corona support enabled. Without Corona, each sync of the Leads table requires a full export which can lead to lower data freshness. Please contact Marketo to request Corona support be added to your account.

Bulk API Limits

Part of the extraction process using the Bulk API involves writing and downloading a file of the extracted data. Stitch then pushes the data from this file into your destination.

Marketo currently limits the amount of data pulled on a daily basis to 500MB. Exceeding the limit will pause replication until midnight CT, when it will be possible to resume.

Note: This applies to the activity_[activity_types] and leads tables and is a separate quota from the REST API call limits mentioned previously.


Marketo table schemas

activities_[activity_type]

Replication Method: Key-based Incremental Replication Key : activityDate
Primary Key : marketoGuid API Endpoint: getLeadActivities

In version 1.0 of Stitch’s Marketo integration, the activities table contained all data pertaining to lead activities.

In this version, you can choose to replicate lead activity data for specific activity types. For every activity type defined in your Marketo account, you’ll see an activities_[activity_type] table in the Tables to Replicate tab. For example: activities_click_email contains lead activity data for the click_email activity type.

These tables will contain the fields listed below, along with any fields specific to that activity type.

marketoGuid
STRING

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.

primary_attribute_value_id
INTEGER

The ID of the activity’s primary attribute.

primary_attribute_name
STRING

The name of the activity’s primary attribute.

primary_attribute_value
STRING

The value of the activity’s primary attribute.


Replication Method: Full Table API Endpoint: getAllActivityTypes
Primary Key : id

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

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__name
STRING

The name of the primary attribute.

primaryAttribute__dataType
STRING

The data type of the primary attribute.

attributes

Secondary attributes of the activity type.

If your destination doesn't natively support nested data, this data may be denested into a subtable named activity_types__attributes. Refer to the Singer schema for details on possible attributes.

_sdc_source_key_id
INTEGER

The activity type ID.

_sdc_level_0_id
INTEGER

This column forms part of a composite key for the table. The value will auto-increment for each unique record, beginning with 0.

name
STRING

The name of the secondary attribute.

dataType
STRING

The data type of the secondary attribute.


Replication Method: Incremental Replication Key : updatedAt
Primary Key : id API Endpoint: getCampaigns

The campaigns table contains info about the campaigns in your Marketo account.

id
INTEGER

The ID of the campaign.

updatedAt
DATE-TIME

The time the campaign was most recently updated.

createdAt
DATE-TIME

The time the campaign was created.

active
BOOLEAN

Indicates if the campaign is active. Applicable only to trigger campaigns.

description
STRING

The description of the Smart campaign.

name
STRING

The name of the Smart campaign.

programId
INTEGER

The ID of the parent program, if applicable.

programName
STRING

The name of the parent program, if applicable.

type
STRING

The type of Smart campaign. Possible values are batch or trigger.

workspaceName
STRING

The name of the parent workspace, if applicable.


leads

Replication Method: Key-based Incremental Replication Key : updatedAt
Primary Key : id API Endpoint: getLeads

The leads table contains info about your Marketo leads.

Marketo Corona and Replication Method for Leads

Stitch replicates leads from Marketo using the Bulk API. The Replication Method for this table will vary depending on your Marketo account setup:

  • If Corona is enabled, this table will use Incremental Replication based on an updatedAt timestamp included in the API query.
  • If Corona isn’t enabled, this table will use Full Table Replication.

Read more about Corona.

id
INTEGER

The ID of the lead.

updatedAt
DATETIME

updatedAt is not a field that will display in your destination. This is an API query parameter used to incrementally replicate this table for accounts that have Corona enabled.

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.


Replication Method: Key-based 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.

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.


Replication Method: Incremental Replication Key : updatedAt
Primary Key : id API Endpoint: getPrograms

The programs table contains info about your Marketo programs. Programs can be parents to most types of assets in Marketo and allow you to track membership and success of leads.

id
INTEGER

The ID of the program.

updatedAt
DATE-TIME

The time the asset was most recently updated.

createdAt
DATE-TIME

The time the asset was created.

description
STRING

The description of the asset.

name
STRING

The name of the asset.

url
STRING

The URL of the asset in the Marketo UI.

type
STRING

The type of program. Possible values include:

  • program
  • event
  • webinar
  • nurture
channel
STRING

The channel of the program.

status
STRING

The status of the program. Only applicable to email and engagement programs. Possible values include:

  • locked
  • unlocked
  • on
  • off
workspace
STRING

The name of the workspace.

folder__type
STRING

The type of the parent folder. Possible values are Folder or Program.

folder__value
INTEGER

The ID of the parent folder.

folder__folderName
STRING

The name of the parent folder.



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.