> 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/changelog/june-2025/june-27th-2025.md).

# June 27th, 2025

As we wrap up June, we’re delivering one last wave of updates to help you finish the month strong. From smoother analytics to easier debugging and fresh integrations. Here’s what’s new:

### **Google Tag Manager (GTM) Integration**

Connect Storylane with Google Tag Manager to track, measure, and optimize demo engagement. Leverage GTM’s flexibility to trigger events, collect richer data, and sharpen your marketing analytics.\
[Learn how to set up GTM with Storylane →](https://docs.storylane.io/integrations/integrations/google-tag-manager)

Or, try the interactive demo below 👇

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

### **Debug Mode for the /share Page**

We’ve introduced a new **Debug Mode** to help you test and troubleshoot CORS behavior on your share pages.

* **How to enable:** Add `?debug=true` to any Storylane `/share` page URL.
* **What it does:** Logs Storylane CORS messages directly in your browser’s devtools console, making it easier to spot and resolve integration issues.

👉 *Example:*\
`https://yourdemo.storylane.io/share/abc123?debug=true`

### **Storylane Desktop App for Mac (improvement)**

* View all demos and folders in a **flattened list** for simpler navigation.
* Improved **screen ordering (sequence)** for new and existing demos to ensure consistent editing.

### **Buyer Hub Analytics Enhancement**

The Buyer Hub now provides clearer visibility into how buyers engage with the same content across multiple sessions. This makes it easier to analyze buyer intent and optimize your outreach.

<figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FaLuIJoCF17opQ5MJCLfk%2FScreenshot%202025-07-01%20at%2017.10.20.png?alt=media&amp;token=8adaf650-f8c2-4e2e-97c2-2a9ace47d0dc" alt=""><figcaption></figcaption></figure>

### **Demo Player Autoplay (improvement)**

We’ve refined and fixed the autoplay experience in the demo player, delivering smoother transitions and a more reliable viewing experience for your prospects.

Thanks for trusting us.\
If you have any questions, feel free to reach out at <support@storylane.io>.<br>


---

# 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/changelog/june-2025/june-27th-2025.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.