What viewer and lead data does each integration send?

• Plan: Core and higher plans.
• Sent automatically: a page view of the player, and `mindstamp_video_progress` plus `Reached N%` at 10, 25, 50, 75, 90, 95 and 100 percent.
• Fields: `progress_percent`, `video_id`, `video_token`, `video_title`, `event_label`, `event_category`, `viewer_id`, `page_location`.
• Not sent: answers, clicks, names or emails.
• You configure: the Google Analytics ID on the account, group or video.

• Plan: Pro and higher plans.
• Contact, when Send Views is on: email, first name, last name, phone, and variables that match HubSpot property names.
• View event: video title, start and finish, watched percentage, participation, correctness, interaction count, engagement time.
• Answer and click events: only for the interactions you pick in Select Interactions to Send.
• Property mapping and list changes: only where you set a HubSpot Field or choose lists.
• Needs a viewer email.

• View webhooks: Core and higher plans. Interaction and lead webhooks: Pro and higher plans.
• View: the full view record with answers and interactions.
• Interaction: one record for each answer or click, all sent after the view.
• Lead: the viewer record, once for each known viewer.
• You configure: a toggle and an endpoint on each video.

• Plan: Core and higher plans.
• Receives finished views, known viewers and interactions, with the same fields as the API.
• Arrives when Zapier next checks for new records, usually within minutes.

• Quoted per account. The records and fields are agreed during setup.
• Zapier, webhooks or the API can also carry the data to Salesforce.

Lead data exists only when the viewer is identified. Collect it with lead capture, or pass it with a personalized link or URL parameters such as `?email=`. Variables you pass in the link travel with the view to webhooks, Zapier and HubSpot.

• All integrations
• Pricing