> 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/sharing-demos/socials-and-email-campaigns.md).

# Socials & Email Campaigns

Share Storylane demos across your marketing channels

* [Email Campaigns](#share-in-email-campaigns)
* [Social Platforms](#share-across-social-platforms)

### 👉 Share in Email Campaigns

Easily embed your interactive demo in email campaigns via HubSpot, Marketo, Outreach, and 15+ email providers

<div align="left"><figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2FvMm6cRB4mpJHXt519lUJ%2FScreenshot%202026-02-16%20at%201.56.42%E2%80%AFPM.png?alt=media&amp;token=0e0ca423-d400-46b9-ba30-a841d183a09a" alt="" width="563"><figcaption></figcaption></figure></div>

### How it works

1. Click on the "Share" button
2. Navigate to the "Email Campaign"
3. Select your Email Provider
4. Click "Copy" to copy the link and paste it into your email

When sharing your demos via email campaigns, you can pick your email providers, such as HubSpot, Marketo, Pardot, and others, to track and personalize the data. Storylane supports 15+ different email providers:

* Active Campaign
* Apollo
* Campaign Monitor
* Constant Contact
* HubSpot
* Intercom
* Klaviyo
* Lemlist
* Lusha
* Marketo
* Outreach
* Pardot
* Reply
* Salesloft
* Woodpecker
* ChurnZero

{% hint style="info" %}
Not only that, you can also send demo events to your CRM, MAP,  data warehouse and more. \
See all [integrations](/integrations-demo-suite/integrations-and-data-flow.md) that Storylane supports here.
{% endhint %}

### 👉 Share across social platforms

Directly share demos as links or GIFs on LinkedIn and X (Twitter), bringing your product closer to where your buyers are.

<div align="left"><figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2FaO77YZR4oWGP8EJ4iYHf%2FScreenshot%202026-02-16%20at%201.57.35%E2%80%AFPM.png?alt=media&amp;token=cea6e190-cf15-4f9d-b109-3f70b0de8c36" alt="" width="563"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://2431356420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN8hWd9k2Pbb6YSWO4pUQ%2Fuploads%2FPJGpUaX37dt9JvZJFR7t%2FScreenshot%202026-02-16%20at%201.58.26%E2%80%AFPM.png?alt=media&amp;token=2286d12b-308e-4b38-870b-3ca481b5989d" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Tip: Want to track the performance of your post? You can easily add a LinkedIn pixel to the demo code to measure your impact >>> [**Learn more about it here**](broken://pages/t9J8dJwHpAWdXYR7Liuw)**!**
{% endhint %}

#### What about Facebook, Bing, and other networks?

For social networks where we don't have a direct integration, you can [download a GIF](/sharing-demos/exports-and-downloads.md#download-as-a-gif) of your demo and include it in your post for more visual impact. This is great for catching attention with an eye-catching demo preview.

{% hint style="info" %}
If you need help or have any questions, feel free to contact us at <support@storylane.io>.
{% endhint %}


---

# 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/sharing-demos/socials-and-email-campaigns.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.
