# Tracking and Analyzing

* [Usage Tracking](#usage-tracking)
* [UTM Tracking](#utm-tracking)
* [Cookie Tracking](#cookie-tracking)
* [Export Analytics](#export-analytics)

###  👉 Usage Tracking

Storylane automatically gathers analytics for each demo. Vew the summary in the "Analytics" page.  

Storylane supports 3 levels of analytics:

* [Global Analytics](#global-analytics)
* [Single Demo Analytics](#single-demo-analytics)
* [Session Analytics](#session-analytics)

{% hint style="info" %}
At Storylane, you can also use **UTM parameters** - to track where a lead is coming from. You'll be able to track these in the analytics dashboard.

![](/files/fcUnxph0Lnhfe3PBU5u1)
{% endhint %}

#### **Global Analytics**

To view the global analytics of all your Storylane demos, navigate to the left sidebar:

* On the "Visitors" >"**All sessions**" page, you can see all the viewers across your demos
* Click on **"Analytics"** to see the global analytics for all your demos in one place
* The "Visitors" > "**Accounts**" page gives you an overview of all the companies visiting your demos

#### **Single Demo Analytics**

To view the analytics of a specific demo you've published, find your demo and click the " # Views" button right below the image of the demo card.

#### **Session Analytics**

You can see more data about each viewer by clicking on a specific session record on the "Visitors" -> "All sessions" page. The individual view shows the exact step that a viewer took in your demo, as well as the time the viewer spent on each step.

Try Interactive Demo Yourself 👇 

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

Below are the common terms we use and their explanations:

* **Total views -** Number of times the demo was opened
* **Engaged -** Number of times viewers interacted with the demo
  * Calculated % `(engaged sessions/total sessions * 100)`
* **Leads -** Viewers that were identified in the demo. See [Lead Tracking](/analytics-and-performance/capture-leads.md) to learn how to capture leads in the demo. If leads can't be identified, then you will see an "unknown lead"
  * Calculated % `(CTA clicked/engaged sessions * 100)`
* **CTA Clicked -** Viewers who clicked on the CTA button to go to a specific URL (for example, to sign up or request a demo)&#x20;
  * Calculated % `(CTA clicked/engaged sessions * 100)`
* **Last View -** last time the demo was viewed
* **Time Spent -** overall time spent by a viewer in the demo
* **Completion -** percentage of guided steps in a demo that the viewer has completed
* **Intent -** score based on time spent, steps completed and CTA interactions

***

### 👉 UTM Tracking

* [Automatic UTM Tracking for CTAs](#id-1.-automatic-utm-tracking-for-ctas)
* [Custom UTM Parameters for CTAs](#id-2.-custom-utm-parameters-for-ctas)
* [Hidden Fields for UTM in Forms](#id-3.-hidden-fields-for-utm-in-forms)

#### 1. Automatic UTM Tracking for CTAs ✨

As long as your demo is embedded on a webpage with UTM parameters in the URL, we’ll take care of the rest! Storylane’s `<script>` tag will automatically pass those UTMs to all CTA buttons within your demo. Just sit back and let the data roll in!

**Example:** If your URL is `https://storylane.io?utm_source=google&utm_medium=cpc`, the CTAs in your demo will carry those UTMs—no extra setup needed! 🎉\
🔗 [**Watch it in Action**](https://www.loom.com/share/e1a1288b86734c9bba3085b57ab1ab96?sid=b0f01b89-7238-4a0a-b518-49845434d1c2)

#### 2. Custom UTM Parameters for CTAs 🎨

Want specific tracking? Manually add UTMs to CTA URLs right in the Storylane editor! When you do this, your chosen UTMs will override any from the parent URL, so you’re fully in control.

**Example:** Add a URL like `https://storylane.io/?utm_source=email&utm_medium=newsletter` and track away!\
🔗 [**See How it Works**](https://www.loom.com/share/c4b0190c419a4c0ab907cf8fc192ed6b?sid=b933930f-87c7-4536-a505-62ac98d9bda4)

#### 3. Hidden Fields for UTM in Forms 📥

Got a form in your demo? Set up hidden fields to automatically grab UTM data from the parent URL when a visitor submits. These fields will automatically capture UTM data from the parent URL when the form is submitted. Easy insights, no hassle! The hidden fields in forms will pass the UTM parameters to your CRM.  \*You will need your CRM integrated inside Storylane\*&#x20;

***

With these quick steps, you’re all set to track your campaigns and get the scoop on what drives traffic to your demos! 📈

***

## 👉 Cookie Tracking?

🍪 **The following requirements must be met for cookie tracking to work:**

1. The demo is embedded on your website
2. You are tracking cookies on your website
3. The lead has filled out a form on your website

{% hint style="info" %}
Cookie tracking **will not work** if any of the following are true:

1. Cookies are not available (the user didn’t accept the cookies)
2. The user is using a different Cookie Account (different browser windows with different email accounts, even if it’s on the same device)
3. If the lead form is within the Storylane demo
4. If the demo is shared through the /share URL
   {% endhint %}

​\*\*Please note that cookie tracking does not work with the Direct Share URL.​Cookie tracking has two primary use cases:

* External Lead Form Before Demo
  * The form is filled first, **then** the lead is passed to the demo.
* The user has filled out a form already on your website and is a returning visitor

***

### 👉 **Export Analytics**

You can export your analytics data anytime for the time range.&#x20;

1. **If you want to export sessions:**

* Go to "Visitors" and then the **All sessions** page&#x20;
* Click on the "Export sessions" button at the top right corner to export a `.csv` format
* You will be emailed a report in a few minutes

2. **If you want to export leads:**

* Go to "Visitors" and then the **Leads** page&#x20;
* Click on the "Export leads" button at the top right corner to export a `.csv` format
* You will be emailed a report in a few minutes

3. **If you want to export accounts:**

* Go to "Visitors" and then the **Accounts** page&#x20;
* Click on the "Export accounts" button at the top right corner to export a `.csv` format
* You will be emailed a report in a few minutes

{% hint style="info" %}
*Note: If you do not receive an email while exporting the CSV file:*

1. *Check the Spam folder*
2. *Ensure the Storylane domain is whitelisted*
   {% endhint %}

{% hint style="info" %}
**Integrations**

Take a look at our [Integrations](/integrations/integrations-and-data-flow.md) page to learn more about our in-depth integrations and custom events that are sent to various platforms
{% endhint %}

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


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.storylane.io/analytics-and-performance/tracking-and-analyzing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.