Marketo Append Tool

The Marketo Append tool uses an incoming data stream that you specify to retrieve corresponding records from your Marketo instance. Using the Append tool is most helpful in situations where you have a list of email addresses, or other data that you are already working with, and want to join that data with additional information from Marketo, or see if they already exist in your Marketo instance.

Tool Configuration

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

Incoming Field

This drop-down will show the list of fields that you have used as input for the tool. Marketo will use this field to find lead records with this field value in the Marketo instance.

Incoming Field Type

What type of records the incoming field is (email, SFDC id, etc.).

Output Fields

The fields you want to retrieve from the Marketo database. These fields as well as the fields that were passed into the tool will be returned in the output data stream.

If the output fields that you select are also contained in the incoming data stream, the output field coming from Marketo is renamed with a 2 at the end.

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 sends 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):

2012-02-28T14:00:00-06:00

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:

2012-02-28 14:00:00

Or, if you were only 4 hours earlier than UTC, it would be returned to you like this:

2012-02-28 16:00:00

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: