> 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/hubs-docs/integrations-hub/integrations/pardot.md).

# Pardot

Storylane integrates seamlessly with Pardot, enabling you to:

* Sync demo data with existing leads.
* Automatically create new leads if they don’t already exist.
* Log demo session activity on the Pardot timeline.
* Capture leads directly via Pardot forms.

Follow these step-by-step instructions to set up the integration:

***

### **Step 1: Add the Storylane Code to Your Website (Optional)**

This step enables lead attribution tracking. Add the following code snippet to the `<head>` tag of your website:

```javascript
(function(){"use strict";function e(t){const r=t.head;if(!r)return;const i=t.querySelector('script[src="https://js.storylane.io/js/v2/storylane.js"]'),n=t.querySelector('script[src="https://js.storylane.io/js/v1/storylane.js"]');if(i||n)return;const s=t.createElement("script");s.type="text/javascript",s.async=!0,s.src="https://js.storylane.io/js/v2/storylane.js",r.appendChild(s)}e(window.document)})();
```

> 💡 [Learn more about lead attribution here.](https://docs.storylane.io/storylane-knowledge-base/tracking-and-analysing/lead-attribution)

***

### **Step 2: Connect Pardot with Storylane**

1. **Contact Support:** Reach out to your sales contact or Storylane support team to initiate the integration process.
2. **Set Up the Integration:**
   * When the Pardot integration modal opens, click **Connect.**
   * Select your relevant Pardot account.
   * Enter your **unit ID** in the provided field.
   * Finalize the setup by logging in to your Pardot account when prompted.

***

### **What Data Does Storylane Sync to Pardot?**

#### **Custom Properties**

Storylane automatically syncs demo data to Pardot under custom fields. Here's the data included:

| **Property Name**                  | **Description**                    | **Data Type** |
| ---------------------------------- | ---------------------------------- | ------------- |
| Storylane Demo Name                | Last demo viewed                   | String        |
| Storylane Demo Viewed At           | Last demo view timestamp           | DateTime      |
| Storylane Demo Time (secs)         | Time spent on demo (seconds)       | Integer       |
| Storylane Demo Complete (%)        | Percentage of steps completed      | Percent       |
| Storylane Demo Link                | Link to the demo                   | URL           |
| Storylane Demo CTA Clicked         | CTA URL clicked                    | URL           |
| Storylane Demo Checklist Completed | Indicates if the checklist is done | Boolean       |
| Storylane Demo Sessions            | Total number of demo sessions      | Integer       |

***


---

# 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/hubs-docs/integrations-hub/integrations/pardot.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.