Sharing your Supademo

Now that you’ve created, edited, and personalized your Supademo, we’ll walk through how to share and embed it. Ideally, you share your Supademo far and wide — whether you embed it on your homepage, add it to docs, use it within training, or disseminate the link in onboarding emails.


This guided showcase will walk through:

  • Sharing your Supademo as a link or embed
  • Grouping multiple demos into a Showcase Collection, which help you chunk out and group multiple Supademos into a single link or embed that can be shared
  • Sharing any Supademo as an in-app product tour
  • How to export Supademo as an MP4 video or as a GIF export
  • How to export Supademo as a SOP (standard operating procedure) guide for use in PDFs or word docs, and training

✨ 3 tips and tricks from the Founder

Tip 1. Use Showcase collections to create modular walkthroughs of complex products Showcases help you package and share your Supademos in a modular, self-paced, section-by-section format. This is incredibly helpful for demonstrating complex products or multiple features within sales follow ups, onboarding, or training. This is also incredibly useful within expos, trade shows, and conferences!
Tip 2. Share from one Supademo in multiple ways You can utilize one Supademo in multiple ways - by sharing as a link, embedding in docs, triggering it as an in-app product modal overlay, or by exporting as a GIF/MP4 or SOP guides.
Tip 3. Share Supademo with a trackable link for session-level data You can create a personalized link for a Supademo by creating one for a specific viewer (i.e. where you enter their details), or by using UTM parameters (i.e. adding ?v_email=EMAIL to the end of your share link). In both cases, you can get notified when that specific viewer interacts or engages with your Supademo, and see THEIR specific data under that analytics for that Supademo. This helps you focus on the most engaged prospect or customer.

Ready for the next lesson?

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.