Headline
Present an intro, transition, ending, or call to action with polished copy.
Form
Collect viewer details before, during, or after the demo.
Embed
Place another web page or tool inside a cover screen.
Headline widgets
Use a headline widget to frame the story. Common uses include a welcome screen, section break, summary screen, or ending screen with a next step. You can edit the title, description, logo, optional image, alignment, and button actions. Add a second button when viewers need a choice, such as Book a demo and Replay. The Add new CTA shortcut creates a call-to-action cover based on the same headline widget model.Form widgets
Use a form widget to capture viewer information. Common fields include name, email, company, role, and use case. The editor supports text fields and dropdown fields. You can mark fields as required, edit the submit button, and choose what happens after submission, such as moving to the next step.Embed widgets
Use an embed widget when a cover needs to show another web page or embedded tool. Add the source URL in Source URL. Embeds work best for lightweight content that is meant to be viewed inside the demo flow, such as a calendar, form, or supporting page.Cover backgrounds
Cover steps can have their own background. You can keep the default, choose a color or gradient, use an image, or use a glassmorphism-style background derived from demo imagery. Use the cover background when a non-product screen needs stronger visual treatment than the main walkthrough.Custom widgets
Custom widgets exist in the demo schema for teams that need a custom-rendered cover experience. They are configured from the Code tab, not from the no-code editor. Use the no-code editor for headline, form, and embed widgets. Use the schema when you need a custom widget implementation.Related references
- For exact widget fields, see Widgets.
- For cover step structure, see Cover steps.
- For form analytics, see Analytics.