How to Use Wistia to Capture Leads From Product Videos

The short answer: upload the demo to a folder, add a Wistia Form at the point the video has earned an email, ask for consent in a checkbox, export the entries by hand on Business or connect HubSpot through Signals with a static list, embed the video on a page that loads the HubSpot tracking script, then compare form conversions and heatmaps against a baseline, with an agent pulling the weekly numbers through Wistia's MCP server.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

The job: a product demo on your features page that should produce named leads, not only plays. Wistia can gate the video, identify the viewer and pass the viewing history to HubSpot. Each piece has a precondition, and Wistia's troubleshooting guide traces most sync problems to a skipped setup step. For tiers and prices, see the Wistia glossary entry.

Before you start:

• The plan arithmetic. Forms are on Business at $99 a month with monthly billing; the HubSpot connection needs Business + Signals at $412 (pricing, checked on 24 October 2026). For example, if the gate produces 30 qualified leads a month, Signals costs ($412 - $99) / 30 = $10.43 more per lead than exporting them by hand.
• An Owner or Manager login. Only those roles can open the Integrations page (HubSpot guide).
• A static list in HubSpot. Wistia Form entries can only go to static lists.
• A test page that loads your HubSpot tracking code, or the willingness to let Wistia load it for you.
• A baseline. Plays, play rate and conversions for the current ungated video over the last 30 days, from its analytics, so there is something to compare with.

Step 1: Upload the demo into a folder

Everything in Wistia lives in a folder. From the home page, open the Upload menu, choose the file, pick My Library or Shared Library and select or create the folder (upload guide).

Step 2: Place the form where the video has earned it

Open Customize and select Form (Wistia Forms guide). Choose the behaviour: at a specific time, which pauses the video and takes over the player, or On hover, which slides in from the left while the video keeps playing. Then decide whether viewers may skip it.

My recommendation: place it after the problem is shown and before the answer, and allow skipping on the first test, so you learn how many people want the rest rather than how many you can corner.

Step 3: Ask only for what sales will use, and for consent

Click Edit form to change the button text, ask for first and last name, and add fields: text, dropdown or a single checkbox. Use the checkbox for marketing consent. Under the GDPR, consent is a freely given, specific, informed and unambiguous statement or clear affirmative action (GDPR, Article 4(11)), and Article 13 of the ePrivacy Directive makes prior consent the rule for marketing email to individuals (ePrivacy Directive). Ask your legal team for the wording; this is not legal advice.

Step 4: The free route, exporting entries by hand

Without any integration, entries are still recorded. Open the video's Analytics, then the Conversion tab, scroll to Form submissions and click Export; the spreadsheet is sent to your account email (Wistia Forms guide). The Audience page exports every identified viewer across videos, and Notifications can email you each new lead (lead generation tools). For the first month, a weekly import into HubSpot is enough to see whether the gate produces leads worth paying for.

Step 5: Connect HubSpot through Signals

On the Integrations page, open the Marketing Automation tab, select HubSpot and click Connect, then sign in to the right HubSpot instance (HubSpot guide). Tick Auto-load HubSpot tracking if some pages lack the script, save, and look for the green Connected badge. Make HubSpot the Primary integration, or Wistia Form entries will not sync. Back in the form, choose the static list, and map each custom field to a HubSpot property from the drop-down under it.

Step 6: Embed the video on a tracked page

On the video's page, click Embed, choose the Inline Standard embed with responsive sizing and click Copy Code (embedding guide). The page has to load both the HubSpot tracking code and Wistia's player script; a CMS that strips the script from an iframe embed breaks the tracking.

The HubSpot cookie that ties a viewer to a contact is stored in the visitor's browser, and Article 5(3) of the ePrivacy Directive requires consent before storing or reading that kind of information unless it is strictly necessary. Check that your cookie banner covers it before the page goes live.

Step 7: Turn viewing events into a HubSpot list

For each identified viewer, Wistia sends Played 1%, 25%, 50%, 75% and 100% milestones, clicks on links in the video and form submissions to the contact timeline, with a heatmap of the session (HubSpot guide). In HubSpot, build an active list with the Wistia HubSpot v2 Play filter, Media ID equal to your video and Percent Watched of at least 75%, then hand that list to a nurture or to sales. Filter on the Media ID rather than the name, because names change.

Step 8: Let an agent pull the weekly numbers

Connect Wistia's MCP server: in Claude, go to Customize, then Connectors, add a custom connector and paste https://api.wistia.com/mcp/api; in Claude Code, run claude mcp add --transport http wistia https://api.wistia.com/mcp/api (MCP guide). Then ask, for example: "For every video in the Product demos folder, list plays, play rate and form conversions for the last seven days, and flag any video whose conversions fell week on week."

The server reads media aggregates, form and CTA conversions and second-by-second engagement. Every action asks for approval by default; Wistia's guide suggests letting read-only actions run and keeping anything that creates or deletes on ask each time. The agent reports, and a person decides what to change in the form or its placement.

Where Wistia's guides say it breaks

• HubSpot is not the Primary integration. Wistia Form submissions then do not sync (MAP troubleshooting).
• No list chosen in the form. Leads stay in Wistia and never reach the email provider (lead generation tools).
• Viewing on a Wistia media page. Without auto-load, that page carries no HubSpot script, so leads can arrive with no viewing data.
• Testing while logged in to Wistia. You are already identified, so the form hides; open the page in a private window.
• Two tools at once. A video takes one form and one call to action, and they cannot overlap.

How to know it worked

Set the gated video against your baseline: form conversions per 100 plays, and what happened to the play rate once the gate went in. A gate that halves the plays can cost more pipeline than it creates. For a cleaner read, embed the same video on two comparable pages for the same weeks, one gated at the midpoint and one at the end.

Signals is sold on measuring pipeline and revenue impact. A tool that reports its own contribution to pipeline is grading its own homework, so the comparison above is the check it cannot run on itself. Later, if you want that check run continuously across channels, a causal attribution tool like Causality Engine does it. Disclosure: I founded it.

FAQ

Can I use a HubSpot form instead of a Wistia Form?

Yes. Once the integration is connected, a HubSpot form section appears in Customize, with HubSpot's control over fields and styling. The trade-off, per the HubSpot guide, is that its data goes only to HubSpot and is not stored in Wistia.

Does every video need a form?

No, but tracking rests on the cookie that a form submission sets, and cookies do not carry across browsers or devices. Every video a lead can watch without submitting is a gap in their history (HubSpot guide).

Why do leads arrive in HubSpot without viewing data?

Usually a missing tracking script, or the video was watched on a Wistia media page or share link instead of your embed. A form submission captures the lead but carries no ongoing viewing data by itself (MAP troubleshooting).