The Marketo static list destination exports cohorts into Marketo as a static list, sending them to a destination folder or program of your choice. Use Marketo's tools for in-app messaging, push notifications, and email campaigns to better engage your users.

{% callout type="note" title="" %}
This page covers the Marketo Static List destination. Unlike the [Marketo Cohort](/docs/data/destination-catalog/marketo) destination, this integration automatically exports cohorts as a static list in Marketo.
{% /callout %}

## Use cases

- Create a marketing campaign targeted at a cohort of users created in Amplitude.
- Automate emails from Marketo based on activities tracked in a cohort.
- Reduce the number of fields in Marketo by syncing cohorts to lists instead of fields.

## Considerations

- Email values are case-sensitive. If you use email addresses to map users between Amplitude and Marketo, the email address must be consistent between both systems.
- Marketo generates Amplitude users that don't already exist in Marketo.
- The integration doesn't support cohorts larger than 3,000,000.

## Set up the integration

### Marketo setup

{% callout type="note" title="" %}
These steps require Marketo Administrator privileges.
{% /callout %}

You need your Marketo Client ID, Client Secret, and REST API Endpoint. For more detailed instructions, refer to [Marketo's documentation](https://developers.marketo.com/blog/quick-start-guide-for-marketo-rest-api/).

1. Create a role with "Read-Write Person" and "Read-write Assets" permissions under "Access API".
2. Create an API-only user and associate it with the API role you created.
3. Go to **Admin > Integration > Launchpoint** to create a new service. Set 'Service' to 'Custom' and select the API Only User you created in the last step.
4. On the service, click **View Details** and copy the `Client ID` and `Client Secret`.
5. Go to **Admin > Integration > Web Services** and copy the REST API Endpoint. **Important**: Remove the `\rest` at the end of the endpoint. If you don't remove it, the integration doesn't work correctly.

{% callout type="example" title="Example Keys" %}

- `Client ID:` `97890c99-9999-46e4-bccc-351071cd5c3b`
- `Client Secret:` `xzy3XYZxyZqIroHtliA7mDKTx7NUXyZZ`
- `REST API Endpoint:` `https://133-CDN-660.mktorest.com`
{% /callout %}

### Amplitude setup

1. In Amplitude Data, click **Catalog** and select the **Destinations** tab.
2. In the Cohort section, click **Marketo Static List**.
3. Enter the name for the connection.
4. Paste the Client ID, Client Secret, and REST API endpoint you copied from Marketo.
5. Assign the Amplitude field mapping for email. The mapping must be a unique identifier.
6. Save when finished.

## Send a cohort

To sync your first cohort, follow these steps:

1. In Amplitude, open the cohort you want to sync, then click **Sync**.
2. Select **Marketo Static List**, then click **Next**.
3. Choose the account you want to sync to.
4. Choose the folder or program type and provide the folder or program ID.
   a. Find the program ID in the URL: it's the 4-5 digits between the G and A in the URL of the selected program.
5. Choose the sync cadence.
6. When finished, save your work.

Cohort users may take a few minutes to appear on Marketo's side, depending on cohort size.

## Troubleshooting

### User discrepancies between Amplitude and Marketo

Some destinations like Marketo may return a 2XX response indicating the cohort synced successfully from Amplitude. The third-party destination may silently drop users who don't meet their criteria, and Amplitude may not receive notice of this exclusion. To check whether a user transferred successfully, review the CSV file from Amplitude. Amplitude works to identify cases where users aren't included at third-party platforms by analyzing response codes, but detecting every instance of silent user exclusion isn't always possible. If you encounter issues, refer to the [third-party sync troubleshooting guide](/docs/data/destinations/syncs) for help investigating and diagnosing cohort sync discrepancies.