> 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/integrations-demo-suite/integrations-and-data-flow/salesforce.md).

# Salesforce

Create new leads and send demo analytics to SFDC

Storylane directly integrates with Saleforce (SFDC). With the integration, you can:

* Create new leads or contacts
* Update demo analytics for leads or contacts as custom objects

{% hint style="warning" %}

### **Capturing Leads**

There are few ways in which you can identify new leads. You can refer the article on [Lead Tracking](/analytics-and-performance/capture-leads.md) to learn more
{% endhint %}

{% hint style="info" %}
You can also access Storylane demos directly within Salesforce. [Read more.](/integrations-demo-suite/integrations-and-data-flow/salesforce/storylane-app-for-salesforce.md)
{% endhint %}

### How to Integrate

See below Storylane example on how to integrate with SFDC

{% @storylane/embed subdomain="renee" linkValue="w0hydldhat9s" url="<https://renee.storylane.io/demo/w0hydldhat9s>" %}

#### Setup Hub Properties

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

{% hint style="danger" %}
Verify the user connecting Salesforce <> Storylane has the required object permissions ↓&#x20;
{% endhint %}

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

### Integration Features

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

### Custom Objects

Upon successful integration, Storylane creates custom objects in Salesforce to capture engagement data for both **single demos and Hubs**.

* **`StorylaneDemoData__c`** (label: *Storylane Demo Data*) stores engagement details for viewed demos.
* **`StorylaneHubData__c`** (label: *Storylane Hub Data*) stores aggregated engagement data for viewed Hubs.

These records are associated with the relevant **Lead and/or Contact** records, allowing teams to view **demo- and Hub-level engagement, intent, and CTA interactions** directly within Salesforce.

### 🟦 Storylane Demo Data

**Object API Name:** `StorylaneDemoData__c`

<table><thead><tr><th width="167.1744384765625">Field Label</th><th width="191.07550048828125">Field API Name</th><th width="155.502685546875">Data Type</th><th width="231.28277587890625">Description</th></tr></thead><tbody><tr><td>Demo Name</td><td><code>Name</code></td><td>Text</td><td>Name of the demo viewed</td></tr><tr><td>Demo Last Viewed At</td><td><code>DemoLastViewedAt__c</code></td><td>DateTime</td><td>Timestamp of the most recent demo view</td></tr><tr><td>Demo Time (secs)</td><td><code>TimeSpent__c</code></td><td>Number</td><td>Time spent in the demo (seconds)</td></tr><tr><td>Demo Complete (%)</td><td><code>Completion__c</code></td><td>Percent</td><td>Percentage of demo steps completed</td></tr><tr><td>Demo Link</td><td><code>DemoLink__c</code></td><td>URL</td><td>Link to the demo</td></tr><tr><td>Storylane CTA Clicked</td><td><code>CtaClicked__c</code></td><td>URL</td><td>CTA URL clicked within the demo</td></tr><tr><td>Lead Intent</td><td><code>LeadIntent__c</code></td><td>Text</td><td>Engagement-based intent (Low / Medium / High)</td></tr><tr><td>Lead Source</td><td><code>LeadSource__c</code></td><td>Text</td><td>How the viewer was sourced</td></tr><tr><td>Related Lead</td><td><code>Lead__c</code></td><td>Lookup (Lead)</td><td>Associated Lead record</td></tr><tr><td>Related Contact</td><td><code>Contact__c</code></td><td>Lookup (Contact)</td><td>Associated Contact record</td></tr><tr><td>Created Date</td><td><code>CreatedDate</code></td><td>DateTime</td><td>Record creation timestamp</td></tr><tr><td>Last Modified Date</td><td><code>LastModifiedDate</code></td><td>DateTime</td><td>Last updated timestamp</td></tr></tbody></table>

### 🟪 Storylane Hub Data

**Object API Name:** `StorylaneHubData__c`

<table><thead><tr><th width="187.1007080078125">Field Label</th><th width="185.642333984375">Field API Name</th><th width="162.2474365234375">Data Type</th><th>Description</th></tr></thead><tbody><tr><td>Hub Name</td><td><code>Name</code></td><td>Text</td><td>Name of the Hub viewed</td></tr><tr><td>Hub Last Viewed At</td><td><code>HubLastViewedAt__c</code></td><td>DateTime</td><td>Timestamp of the most recent Hub view</td></tr><tr><td>Hub Viewed Content (%)</td><td><code>HubViewedContent__c</code></td><td>Percent</td><td>Percentage of Hub content viewed</td></tr><tr><td>Hub Time (secs)</td><td><code>HubTimeSpent__c</code></td><td>Number</td><td>Total time spent in the Hub (seconds)</td></tr><tr><td>Hub Link</td><td><code>HubLink__c</code></td><td>URL</td><td>Link to the Hub</td></tr><tr><td>Storylane CTA Clicked</td><td><code>CtaClicked__c</code></td><td>URL</td><td>CTA URL clicked within the Hub</td></tr><tr><td>Lead Intent</td><td><code>LeadIntent__c</code></td><td>Text</td><td>Engagement-based intent (Low / Medium / High)</td></tr><tr><td>Lead Source</td><td><code>LeadSource__c</code></td><td>Text</td><td>How the viewer was sourced</td></tr><tr><td>Related Lead</td><td><code>Lead__c</code></td><td>Lookup (Lead)</td><td>Associated Lead record</td></tr><tr><td>Related Contact</td><td><code>Contact__c</code></td><td>Lookup (Contact)</td><td>Associated Contact record</td></tr><tr><td>Created Date</td><td><code>CreatedDate</code></td><td>DateTime</td><td>Record creation timestamp</td></tr><tr><td>Last Modified Date</td><td><code>LastModifiedDate</code></td><td>DateTime</td><td>Last updated timestamp</td></tr></tbody></table>

####

<figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2Fa8qTwrS2aXKx2VSOqttc%2FSCR-20260116-rczh.png?alt=media&amp;token=8c43fee3-ec20-451e-829f-775ce5a530ee" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2FFUpPLl4YLdlZL5J7HKpF%2Fimage.png?alt=media&amp;token=f8c57bc0-1b86-4978-8f31-4516e8b8f7f1" 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/integrations-demo-suite/integrations-and-data-flow/salesforce.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.