> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/integrations/marketo.md).

# Marketo

Connect Adobe Marketo to create and update leads from survey responses.

Zigpoll integrates with Adobe Marketo Engage to automatically create or update leads and add them to static lists based on survey responses.

## Setup

1. Navigate to **Integrations** in your Zigpoll dashboard
2. Find **Marketo** and toggle it on
3. Enter your Marketo credentials:
   * **REST API Endpoint** — Your Marketo REST API URL (e.g., `https://xxx-xxx-xxx.mktorest.com`). Find this in **Admin > Web Services > REST API**.
   * **Client ID** — Create a custom service in **Admin > LaunchPoint** and copy the Client ID.
   * **Client Secret** — The Client Secret from the same LaunchPoint custom service.
4. Click **Save** to store your credentials

## Using Marketo in Action Logic

Once connected, Marketo actions appear in both the survey's **Settings → Workflows → Actions** tab (survey-level) and **Question Logic** (question-level) action dropdowns.

### Add to Marketo List

Select **add to marketo list** from the action dropdown and choose a static list from the selector. When the action conditions are met:

1. A lead is created or updated in Marketo using the respondent's email address
2. Survey response data is stored as custom fields on the lead
3. The lead is added to the selected static list

{% hint style="info" %}
This action requires the respondent to provide an email address. If no email is available, the action will be skipped.
{% endhint %}

## Requirements

* A Marketo Engage subscription with REST API access
* An API-only user role with a LaunchPoint custom service configured
* The custom service must have permissions to manage leads and lists


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/integrations/marketo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.