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

# Marketo

Learn how you can push data about visitors engaging with your RepX agent into Marketo

RepX integrates with Marketo, pushing useful information about conversations your website visitors have had into RepX. This includes<br>

* **creating and updating leads and contacts** in Marketo when visitors share their emails in conversations
* **logging the full conversation transcript and summary** as custom activities in the lead and contact records

### Setting up RepX - Marketo integration&#x20;

**Pre-requisites to take care of, before you connect Marketo with RepX:**

* If you've **already connected Marketo with Demo Suite**, make sure to have **1 additional custom activity available**. This one additional activity is what RepX will use.
* If you plan to connect **Marketo with Demo Suite later**, make sure to have **2 custom activities in total available** (one for RepX, one for Demo Suite to consume)
* Assign the correct API user during setup. The user must have the following permissions:
  * Read-Write Activity
  * Read-Write Activity Metadata
  * Read-Write Person
  * Read-Write Schema Custom Field
  * Read-Write Schema Standard Field

### **Connecting and configuring Marketo with RepX**

{% @storylane/embed subdomain="app" linkValue="4qiydc3vwvzz" url="<https://app.storylane.io/share/4qiydc3vwvzz>" %}

1. Access the **Marketo Integration** section in your Storylane dashboard under **Settings > Integrations**.

* Access the **Marketo Integration** section in your Storylane dashboard under **Settings** > **Integrations**.
* Click the **Connect** button.
* Storylane's Support team will provide a secure URL for configuration. Open the URL and click **Configure Marketo.**
* Enter the required credentials:
  * Client ID
  * Client Secret
  * Endpoint URL
  * Identity URL

### **Conversation data in Marketo** <a href="#what-data-does-storylane-sync-to-marketo" id="what-data-does-storylane-sync-to-marketo"></a>

RepX automatically syncs conversation data to Marketo under **custom fields**. Here's the data included:&#x20;

<figure><img src="https://2714158815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5THBKNFo5kBfDJULy3RM%2Fuploads%2FnFGgWD4UjtLpSTSGlxfR%2FScreenshot%202026-10-06%20at%2010.44.16%E2%80%AFAM.png?alt=media&amp;token=391138dc-a26b-47ac-87d7-82df28fb50d3" alt=""><figcaption></figcaption></figure>

| Field name                          | Description                                            |
| ----------------------------------- | ------------------------------------------------------ |
| Storylane RepX total messages count | The total number of messages in a conversation         |
| Storylane RepX last conversation at | Timestamp of the most recent conversation              |
| Storylane RepX conversation topics  | List of topics that were discussed in the conversation |

### **Custom activities in Marketo** <a href="#what-data-does-storylane-sync-to-marketo" id="what-data-does-storylane-sync-to-marketo"></a>

Each RepX conversation also creates a custom activity in Marketo. This activity includes the conversation transcript and more information about the lead. Here's a sample custom activity:

<figure><img src="https://2714158815-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5THBKNFo5kBfDJULy3RM%2Fuploads%2FFFRULR3zSkP41e5dbSvr%2FScreenshot%202026-10-06%20at%2010.43.47%E2%80%AFAM.png?alt=media&amp;token=5bd40b2f-9933-4bd6-b13f-1a2e39c99aff" alt=""><figcaption></figcaption></figure>


---

# 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.storylane.io/repx-chat/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.