Skip to main content
A lead form asks a viewer for information as part of the demo experience. Decide what you need to follow up and why before adding a gate: asking for more information can create friction for someone who only wants to explore.
  1. Publish the reviewed demo and open Share → Link.
  2. Create a named link or open an existing link’s Lead form & tracking settings. Expand Advanced settings and enable Require lead info. Availability depends on the workspace plan.
  3. Email is required. You can also require a name or company, limit the form to work email, and configure allowed or blocked email domains. Choose only the restrictions appropriate to the audience.
  4. Save the link and open it in a separate browser session. Check the form, its required fields, the result after submission, and the rest of the demo. If the link is used for an embed, test the actual embedded destination too.
This setting belongs to the share link. Another link can have different settings, and an unrestricted plain URL can offer a different path to the demo. Review the demo’s access setting and active links if you intend all recipients to use a controlled link. Do not assume that adding a form to one link changes every way to open the demo. Suppose a campaign sends visitors to a product tour and the team wants an email for follow-up. Create a named link for that campaign, require lead info, and start with the email field. Before distributing it, open the link in a separate session and submit a test address your team is allowed to use. Confirm that the demo opens and that the submission appears in Leads under the expected link. If you restrict email domains, test both an intended address and an address that should be rejected. A work-email rule can exclude legitimate users who use a personal address; an allowlist can exclude a partner or a customer with a different domain. Make those trade-offs deliberately. If the campaign also has an unrestricted link or a public plain URL, test those paths too so the team’s expectations match what a viewer can actually access.

Review and follow up

Open the demo’s Leads view to find submissions and, where available, filter by share link. Review the details before updating a status, assigning an owner, adding notes, or exporting a list. A form submission is a signal that someone provided information; it is not by itself proof of their needs or permission to contact them in every context. Use appropriate test details when checking the flow and follow your organization’s rules for handling the resulting test record. Explain clearly to real viewers why information is requested and handle it according to your team’s privacy practices.

Improve the experience

Compare the share link’s traffic and demo engagement over a meaningful period, but do not infer the cause of a drop from a number alone. Try the experience yourself and ask whether the form appears at a useful moment, whether the request makes sense, and whether domain restrictions exclude intended viewers. Review the form and follow-up process before changing it. See Learn from engagement. When comparing campaigns, note which link, time period, audience, and restrictions produced each result. A link with a form and a link without one serve different journeys. Do not interpret a count of demo views as a count of distinct people, or a lead submission as proof that a viewer completed the demo.