If your demo is in Storylane, you can bring it over instead of recording it again. AtriumKit reads the demo’s public page, the same one your visitors see, and rebuilds it as a guided demo you can edit.
Before you start
- The demo has to be public. Open its share link in a private window: if it plays without signing in or entering an email, it can be imported. Turn off an email gate in Storylane first if it has one.
- It has to be yours to copy. The importer asks you to confirm it’s your company’s demo, or that you’re allowed to copy it.
- Your Storylane demo isn’t changed. Importing only reads it.
Import it into your workspace
- In Storylane, open the demo, click Share and copy the link. It looks like
https://app.storylane.io/share/…. The demo’s own link (…/demo/…) works too, onapp.storylane.io, on your Storylane subdomain (yourcompany.storylane.io) or on your own domain (demo.yourcompany.com). So does the embed code from your website. - In AtriumKit, click New demo in the sidebar, then Import from Storylane.
- Paste the link, tick the box to confirm it’s yours to copy, and click Import demo.
- AtriumKit downloads the screenshots, then opens the new demo in the editor. A message says how many steps came across, and what was left out.
The demo is a draft. Check it, then click Publish.
Import it without an account
On atriumkit.com/import/storylane, paste the link and click Import my demo. Your demo opens on a page where you can play it, and keep it by creating a free account. An import nobody keeps is deleted after 7 days. If you change your mind, Delete this demo on that page removes the copy straight away.
Signed in, the same page imports into your workspace, or click Get a link to share instead to make that no-account link for someone else.
What comes across
- Every flow, as chapters one after another: the first flow, then the chapters of your chapter menu in its order, then any others. A chapter starts with its own popup, or with a card naming it. A flow that only a button leads to (a quiz answer, say) ends the demo when it’s over, as it did in Storylane.
- A chapter menu in the middle of the screen with up to four items becomes the first card, with a button for each chapter. A menu in a corner, or with more items, becomes the chapters in order.
- Screenshots, one screen per page of the demo, named after the page. HTML pages, including Storylane’s newer captures, come across as a screenshot of the page.
- Tooltips, with their text and the box they highlight. They advance with Next. A heading in the text becomes the step’s title.
- Hotspots, as Dot steps: a pulsing dot with their text, on the button they point at, which viewers click to go on. If AtriumKit can’t find a button there (a text link, say), the dot sits where Storylane’s beacon was, and the message says how many to check. Switch a step to Pulse to highlight the whole button instead.
- Popups, as cards: the first is the intro, the last the outro, and the ones in between are chapters. A popup’s first heading becomes the card’s title.
- Buttons, with where they go. A button that opens a link, a meeting link, another chapter or another step still does. A step with two buttons gets both, as choices. A button that led to a Storylane lead form opens your demo’s own call to action instead, when the demo has one.
- Videos in popups. The popup’s text comes across, with a Watch the video button that opens the video where Storylane hosts it. If you leave Storylane, upload the video somewhere else and change the button’s link.
- Narration. Each step’s voiceover comes across as uploaded narration, with captions when Storylane had them. Narration plays for viewers on the Pro and Team plans.
- Personalization tokens like
{{first_name}}become variables, with the default values you set in Storylane, so the text reads the same. Tokens with no match here, like a rep’s name or a date, are written in as text. - The demo’s title and description.
What doesn’t
- Video clips and lead forms. Add a form step in AtriumKit if you need one.
- Pictures on popups. AtriumKit cards show text and buttons, and the message says how many pictures were left out.
- Positions on HTML captures. Storylane HTML demos come across as a screenshot of each page, with each step’s text, but their tooltips point at elements of the page. Select each step and drag its box into place. For editable HTML, record the flow again with the Chrome extension.
If it doesn’t work
- “Storylane sent the demo’s page without the demo in it”: Storylane does that when it gets many requests at once. Nothing was saved. Try again in a minute.
- “That Storylane demo needs a password, an email or a sign-in”: make it public in Storylane, then import it again.
- “Storylane says that demo doesn’t exist or isn’t public”: the link is wrong or the demo was deleted. Check it opens in a private window.
- “That’s a Storylane hub”: import each demo in the hub from its own link.
- Some screenshots couldn’t be downloaded: the steps on them are left out and the message says how many. Try the import again in a minute.