Marketo integration summary

Stitch’s Marketo integration replicates data using the Marketo REST API and Marketo Bulk API. Refer to the Schema section for a list of objects available for replication.

Marketo feature snapshot

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

STITCH
Release status

Released on June 26, 2018

Supported by

Stitch

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-marketo

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Marketo

Marketo setup requirements

To set up Marketo in Stitch, you need:

  • 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

Step 4.1: Verify your Stitch account's data pipeline region

The IP addresses you’ll whitelist depend on the Data pipeline region your account is in.

  1. Sign into your Stitch account, if you haven’t already.
  2. Click User menu (your icon) > Manage Account Settings and locate the Data pipeline region section to verify your account’s region.
  3. Locate the list of IP addresses for your region:

Keep this list handy - you’ll need it in the next step.

Step 4.2: Add Stitch's IP addresses to Marketo's Web Services whitelist

  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 you retrieved in the previous step.
  4. Repeat step 4 until all the Stitch IP addresses for your data pipeline region 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 replication start date

The Sync Historical Data setting defines the starting date for your Marketo integration. This means that data 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.

Marketo integrations support the following replication scheduling methods:

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.

Step 9: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Marketo integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

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

Marketo Daily REST API call limits

By default, all Marketo accounts have a maximum number of 50,000 daily account calls.

The integration’s Max Daily API Calls field dictates the quantity of your total API quota Stitch is allowed to use per 24 hour period. Note: This includes API usage from other apps. By default, Stitch’s Marketo integration will use up to 40,000 of these calls per day, which can be increased or reduced by setting a Max Daily API Calls value.

When the integration detects that the source account’s quota usage has exceeded the specified Max Daily API Calls limit, 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

To incrementally replicate leads data, Marketo requires the authorizing account to have the ability to filter using the updatedAt field. This 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 this filter enabled, Stitch will use the createdAt field to incrementally replicate leads data. Note: This will result in data for this table using Append-Only loading.

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.


Marketo table reference

activities

In version 1 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 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.

Replication Method

Key-based Incremental

Primary Key

marketoGuid

Replication Key

activityDate

Useful links

activities schema on GitHub

Marketo API method

Join activities with on
activity_types
activities.activityTypeId = activity_types.id
leads
activities.leadId = leads.id

activityDate

DATE-TIME

activityTypeId

INTEGER

campaignId

INTEGER

leadId

INTEGER

marketoGuid

STRING

primary_attribute_name

STRING

primary_attribute_value

STRING

primary_attribute_value_id

INTEGER

activity_types

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

Replication Method

Full Table

Primary Key

id

Useful links

activity_types schema on GitHub

Marketo API method

Join activity_types with on
activities
activity_types.id = activities.activityTypeId

attributes

ARRAY

dataType

STRING

name

STRING

description

STRING

id

INTEGER

name

STRING

primaryAttribute

OBJECT

dataType

STRING

name

STRING

campaigns

The campaigns table contains info about your Marketo campaigns

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updatedAt

Useful links

campaigns schema on GitHub

Marketo documentation

Join campaigns with on
programs
campaigns.programId = programs.id

active

BOOLEAN

createdAt

DATE-TIME

description

STRING

id

INTEGER

name

STRING

programId

INTEGER

programName

STRING

type

STRING

updatedAt

DATE-TIME

workspaceName

STRING

leads

The leads table contains info about your Marketo leads.

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

  • If updatedAt filtering is enabled, this table will use updatedAt as the Replication Key
  • If updatedAt filtering isn’t enabled, this table will use createdAt as the Replication Key. Additionally, data will be loaded using Append-Only loading.

Read more about replicating this table.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

Marketo API method

Join leads with on
activities
leads.id = activities.leadId

acquiredBy

BOOLEAN

id

INTEGER

isExhausted

BOOLEAN

membershipDate

DATE

nurtureCadence

STRING

progressionStatus

STRING

reachedSuccess

BOOLEAN

reachedSuccessDate

STRING

stream

STRING

lists

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

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

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updatedAt

Useful links

lists schema on GitHub

Marketo API method

createdAt

DATE-TIME

description

STRING

id

INTEGER

name

STRING

programName

STRING

updatedAt

DATE-TIME

workspaceName

STRING

programs

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.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updatedAt

Useful links

Marketo documentation

programs schema on GitHub

Marketo API method

Join programs with on
campaigns
programs.id = campaigns.programId

channel

STRING

createdAt

DATE-TIME

description

STRING

folder

OBJECT

folderName

STRING

type

STRING

value

INTEGER

id

INTEGER

name

STRING

status

STRING

type

STRING

updatedAt

DATE-TIME

url

STRING

workspace

STRING


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.