This integration is powered by Singer's Marketo tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Stitch support.
Marketo integration summary
Stitch’s Marketo integration replicates data using the Marketo REST 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.0) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release Status |
Released |
Supported By | |
Stitch Plan |
Paid |
Singer GitHub Repository | |
DATA SELECTION | |||
Table Selection |
Supported |
Column Selection |
Supported |
REPLICATION SETTINGS | |||
Anchor Scheduling |
Supported |
Advanced Scheduling |
Unsupported |
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
- Sign into your Marketo account.
- Click the Admin option.
- Under Admin, open the Security menu.
- Click Users & Roles.
- Click the Roles tab.
- Click New Role.
- 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.
- 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.
- Click the Admin option.
- Under Admin, open the Security menu.
- Click Users & Roles.
- In the Users tab, click Invite New User.
- In the INFO section, enter an email address and first and last name.
- Click Next.
- In the PERMISSIONS section, click the checkboxes next to the API User Role you created and the API Only option.
- Click Next.
- 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.
- In Admin, open the Integration menu.
- Click LaunchPoint.
- Click New and then New Service.
- 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.
- Click Create.
- After the service is created, it’ll display in the Installed Services grid. Click the View Details link to display your API credentials.
- Copy the Client ID and Secret into a text file.
Step 4: Whitelist Stitch's IP Addresses in Marketo
Completing this step is required only if you have IP Restriction enabled in Marketo. You can check if this setting is enabled by clicking Admin > Web Services and looking in the IP Restrictions section. If this setting isn’t enabled, skip ahead to the next step.
- In the Integration menu, click Web Services.
- In the IP Restrictions section, click the Edit button.
-
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
-
- Repeat step 4 until all the Stitch IP addresses are added.
- 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
- On the Web Services page, scroll down to the REST API section.
- In this section, find the Endpoint and Identity fields.
- 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
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Marketo icon.
-
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. - In the Endpoint Base URL field, paste your Marketo REST API Endpoint URL.
- In the Identity Base URL field, paste your Marketo REST API Identity URL.
- In the Client ID field, paste your Marketo API Client ID.
- In the OAuth Client Secret field, paste your Marketo API Client Secret.
- 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.
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 tables and columns to replicate
To complete the setup, you’ll need to select the tables and columns you want to replicate to your data warehouse.
Check out the Schema section to learn more about the available tables in Marketo and how they replicate.
- In the list of tables that displays - or in the Tables to Replicate tab, if you skipped this step during setup - locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A green checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A green checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
Note: If you change these settings while a replication job is still in progress, they will not be used until the next job starts.
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.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
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
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 2.0 of this integration.
This is the latest version of the Marketo integraiton.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs
> customers
), while case is maintained in PostgreSQL destinations (CusTomERs
> CusTomERs
). Refer to the Loading Guide for your destination for more info.
activities_[activity_type]
Replication Method : |
Key-based Incremental |
Replication Key : |
activityDate |
Primary Key : |
marketoGuid |
API endpoint : |
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
The ID of the activity. |
activityDate
The date of the activity. |
leadId
The ID of the lead associated with the activity. Reference: |
activityTypeId
The ID of the activity type. Reference: |
primary_attribute_value_id
The ID of the activity’s primary attribute. |
primary_attribute_name
The name of the activity’s primary attribute. |
primary_attribute_value
The value of the activity’s primary attribute. |
activity_types
Replication Method : |
Full Table |
Primary Key : |
id |
API endpoint : |
The activity_types
table contains metadata about the activity types - form fill, web page visit, lead creation, and so on - available in Marketo.
id
The activity type ID. Reference: |
||
name
The name of the activity type. Ex: |
||
description
The description of the activity type. |
||
primaryAttribute
Primary attributes of the activity type.
|
||
attributes
Secondary attributes of the activity type.
|
campaigns
Replication Method : |
Key-based Incremental |
Replication Key : |
updatedAt |
Primary Key : |
id |
API endpoint : |
The campaigns
table contains info about the campaigns in your Marketo account.
id
The ID of the campaign. |
updatedAt
The time the campaign was most recently updated. |
createdAt
The time the campaign was created. |
active
Indicates if the campaign is active. Applicable only to trigger campaigns. |
description
The description of the Smart campaign. |
name
The name of the Smart campaign. |
programId
The ID of the parent program, if applicable. Reference: |
programName
The name of the parent program, if applicable. |
type
The type of Smart campaign. Possible values are |
workspaceName
The name of the parent workspace, if applicable. |
leads
Replication Method : |
Key-based Incremental |
Replication Key : |
updatedAt |
Primary Key : |
id |
API endpoint : |
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.
id
The ID of the lead. Reference: |
acquiredBy
Indicates if the lead was acquired by the parent program. |
isExhausted
Indicates if the lead is currently exhausted in the stream, if applicable. |
membershipDate
The date the lead first became a member of the program. |
nurtureCadence
Cadence of the parent stream, if applicable. |
progressionStatus
The program status of the lead in the parent program. |
reachedSuccess
Indicates if the the lead is in a success-status in the parent program. |
reachedSuccessDate
The date the lead reached success in the parent program. |
stream
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 : |
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.
id
The ID of the list. |
updatedAt
The datetime when the list was most recently updated. |
name
The name of the list. |
description
The description of the list. |
programName
The name of the program associated with the list. |
workspaceName
The name of the parent workspace, if applicable. |
createdAt
The datetime the list was created. |
programs
Replication Method : |
Key-based Incremental |
Replication Key : |
updatedAt |
Primary Key : |
id |
API endpoint : |
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
The ID of the program. Reference: |
|||
updatedAt
The time the asset was most recently updated. |
|||
createdAt
The time the asset was created. |
|||
description
The description of the asset. |
|||
name
The name of the asset. |
|||
url
The URL of the asset in the Marketo UI. |
|||
type
The type of program. Possible values include:
|
|||
channel
The channel of the program. |
|||
status
The status of the program. Only applicable to email and engagement programs. Possible values include:
|
|||
workspace
The name of the workspace. |
|||
folder
Details about the asset’s parent folder.
|
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.