Marketo Input Tool
The Marketo Input tool reads Marketo records based on specific parameters. Use the Marketo Input tool if you do not have any data to start with, or to sample data from your Marketo instance. If you have data that you want to join to additional data from Marketo, the Marketo Append tool is a better option.
Gallery tool
This tool is not automatically installed with Designer. To use this tool, download it from the Alteryx Analytics Gallery.
Configure the tool
Marketo Credentials
URL: The Marketo REST Instance to retrieve records from. This information is found in Marketo (Admin > Integration > Web Services > REST API).
Client ID: Client ID for the API Role user. This information can be found in Marketo (Admin > Integration > LaunchPoint).
Client Secret: Client Secret for the API Role user. This information can be found in Marketo (Admin > Integration > LaunchPoint).
More information about setting up the web service and user roles for accessing the Marketo REST API can be found on the Marketo REST Documentation site.
Options
Two types of Marketo records can be retrieved:
- LeadRecords: These are lead records and there will be one record for each lead.
- Lead Activity Records: These records track the activities for each lead. There are potentially many Lead Activity Records for each Lead Record.
Based on the selections of the type of record, different options are available, and based on that selection there will be parameters available to configure-some are optional and some are required. The table below details which parameters are required based on your chosen configuration.
| Record Type | Option Type | List | Activity Types (1-10) | Output Fields | Start Date/Time |
|---|---|---|---|---|---|
| Lead Records | By Activity Type | Optional | Required | Optional | Required |
| Lead Records | By List ID | Required | N/A | Optional | N/A |
| Lead Records | By Lead Changes | Optional | N/A | N/A | Required |
| Lead Activity | By Activity Type | N/A | Required | N/A | Required |
| Lead Activity | By Lead Changes | N/A | N/A | N/A | Required |
Parameters
Lists: All static lists for the Marketo instance specified in the configuration are listed here (smart lists are not currently available via the API)-only 1 list selection is allowed per request.
Activity Types: All activity types available in Marketo are listed here, there is a maximum of 10 activity type selections per request.
Output Fields: All available fields available in the Marketo instance will be listed. If no selection is made the default list of fields will be returned: Email, Lead ID, First Name, Last Name, Updated At, Created At.
Start Date/Time: Specifies the starting point in the database to begin retrieving records.
Data Considerations
Error messaging such as authentication failures, etc. will be displayed in the configuration window. Error messaging such as missing configuration selections will be shown over the tool in the workflow.
The tool send records in batches of 300 records or less, each batch counts as a separate API call towards the daily limit set by Marketo.
The Marketo REST API limits accounts to 10,000 requests per day, requests to the REST API do not count towards the SOAP API daily limitations.
You want to make sure to maintain Marketo field structures in Alteryx, before writing back to Marketo to avoid errors. The Marketo connector will convert the data to the proper datatypes before outputting to Marketo as long as the field names are valid. If the field names are not found in Marketo, the output will fail.
Datetime fields
All dates in Marketo are stored with a UTC offset. This format is comprised of the local time with an appended offset that can be positive or negative. For example, a datetime value in Marketo might look like this, with the date inserted into Marketo is from a timezone that is 6 hours earlier than UTC time (Mountain Daylight Time):
Reading data from Marketo
To make it easier for Alteryx Artisans to work with these datetime values, Alteryx will convert the datetime value read from Marketo to a machine local datetime value. This allows Artisans to work with the datetime values in their local times. For example, the datetime value above would look like this in an Alteryx workflow or app, assuming you are also 6 hours earlier than UTC time:
Or, if you were only 4 hours earlier than UTC, it would be returned to you like this:
Writing date to Marketo
When datetime values are written back into Marketo using either an insert or update operation, Alteryx will convert the value(s) back to the format that Marketo expects. This is done by calculating the local machine UTC offset and appending that to the end of the datetime value. Alteryx will put a 'T' between the date and time portions of the datetime value as shown in the examples above.
Using the examples above, if a datetime value was written from a timezone with an offset of -6:00, like this:
And then later written back to Marketo (unmodified), from a computer with a UTC offset of -4:00 hours, it would be written back into Marketo like this:
Both times are identical and represent the same moment in time.