# July 25th, 2025

This release brings new ways to drive buyer action, simplify setup, and better understand demo engagement. Let’s dive in:

### Embed Calendar Links in Demo CTAs

You can now embed live scheduling links directly into demo CTAs - supporting **Calendly, Chili Piper, HubSpot**, and **RevenueHero**.\
Let buyers book meetings *without ever leaving the demo*. One click, zero drop-off.

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

***

### Customize the Buyer Hub Link

Make your **Buyer Hub URLs** more memorable and branded.\
You can now customize the back half of the hub link, like `/customer_name` , instead of random characters.\
Cleaner links = stronger trust + easier sharing.

<div align="left"><figure><img src="https://3394459751-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcTuGT7bBECFxxMZpWaFG%2Fuploads%2FW38TjyZmbXDQFIfMM46c%2FScreenshot%202025-07-25%20at%2016.10.03.png?alt=media&#x26;token=e90e202c-a205-4c59-babf-762a0c095274" alt="" width="563"><figcaption></figcaption></figure></div>

***

### New Look for Demo Analytics

The analytics dashboard just got a visual upgrade:

* **Audience tab**: View sessions, leads, and accounts - with clearer structure and richer data
* **Insights tab**: New performance cards help you spot key patterns at a glance

And we’re not stopping - the next wave of analytics improvements is already on the way.

***

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


---

# 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/changelog/july-2025/july-25th-2025.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.