Lead Capturing
Identify leads from your interactive demo and track analytics
Last updated
Identify leads from your interactive demo and track analytics
Last updated
Demos can be used to increase your lead pipeline. With Storylane demos, you can capture new leads and send them to your CRM or marketing platform (along with their session analytics on engagement).
There are 3 main ways in which you can identify leads who watched your interactive demo:
Lead forms can be added as a step in any demo flow. They can be inserted anywhere in your guided flow - beginning, middle, or end. Lead forms provide ways to gather user information such as name and email address while they are engaged.
You can use:
This form provides two fields: email and name (optional) that are configurable. The form can be added as a step in any flow to collect user info.
You can build your own custom form, and copy and paste its embed code through the inbuilt lead form guide. Most commonly, we see forms built from:
Pardot, which requires a custom setup
The lead form can be added as a specific step to your flow. We recommend going with this option if you either need to customize your form or have additional fields to collect.
Tracking UTMs inside the demo
The most common example is to pass UTM params in the URL where you embed the demo or to add it in the CTAs.
The UTMs will be sent to your CRM only if you have the Storylane integration with HubSpot/Marketo/Pardot and the UTM mapping.
If you need any additional information or need assistance, just contact us (support@storylane.io)
You can also configure your custom lead forms even before the demo starts on your website as a gated tour. Most commonly, we see:
Custom forms are being added to the landing page and users are redirected to demos after they fill out the form;
Forms are used as an overlay on top of the demo. Once the form is filled out, the demo is loaded.
Tracking UTMs outside the demo and Cookie tracking
👉 Cookie Tracking
Storylane can capture leads using your marketing cookie, and associate leads with demo analytics.
Cookie tracking has two primary use cases:
External Lead Form Before Demo
The form is filled out 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
>>> Read more about cookie tracking here.
👉 Tracking UTMs
When a demo is embedded on the website, and someone clicks the CTA, Storylane allows you to utilize UTM parameters to track and capture it.
The UTMs will be sent to your CRM only if you have the Storylane integration with HubSpot/Marketo/Pardot and the UTM mapping.
If you need any additional information or need assistance, just contact us (support@storylane.io)
Leads can also be identified by passing 'email' as a URL param either in the demo share URL or the domain where the demo is embedded.
As a result, whenever someone engages with the demo, you get notified about it in your Slack (provided it's integrated with your Storylane account) and the data gets passed on to your CRM/ Marketing stack.
One of the ways we use this at Storylane is in our weekly product update emails. Most of our product emails carry a GIF of our new releases. We link this to the actual releases demo that we create and add the email param to the demo URL.
This not only helps us understand the engagement patterns of our prospects, customers, and dormant users but also keeps the revenue teams, who spend the majority of their time inside the CRM, updated on the lead activity. We then also reach out to the prospects and dormant users whenever they show consistent engagement with our product demos.
See an example of passing the 'email' param in the demo share URL below:
Example of passing 'email' param to landing page URL that has demo embedded in it. Storylane embed code in the page will pick the email param from the parent window URL:
Try Interactive Demo Yourself 👇
