Storylane

Basically if you want to provide a walk-through of a website, then Storylane is well suited. I can't think of a scenario where it is less appropriate unless you are trying to use it for something it isn't intended for. I'm not sure if it will work with a WASM page, so if you are working with WASM, you should at least test that out.

Incentivized

• Allows you to easily grab the visual assets to create a walk through.
• The analytics that are integrated give you a very specific view of engagement.
• Even the most complex web pages can be saved in Storylane, definitely a robust engine.

Incentivized

• The relationship between "pages" and "steps" can get very confusing if you are having to do a mass revamp of a saved story.
• Some of the interface is less than intuitive than it could be.
• I'm not a fan of mouse over features, I realize it is a modern metaphor, but it's a bad one.

Incentivized

They are both good products and pretty similar. Navattic definitely had some strong features, but with Storylane, they were incredibly responsive to requests for help and feature requests and it just "looked" better. Storylane also "felt" better in terms of working with it. There were some design flow decisions made with Navattic that I found to be a bit counterintuitive.

Incentivized

• We were getting thousands of engagements on our Story's.
• We are able to use them as an educational resource when potential clients asked a question.
• The SDR's were able to use them as assets to create interest.

Incentivized