Add your pixel ID
- In Meta Events Manager, copy the ID of the pixel you use for your ads.
- In Mindstamp, open Integrations.
- On the Facebook card, select Connect.
- Paste the ID into Facebook Pixel ID, then select Save.
Paste your Meta Pixel ID into the Facebook integration in Mindstamp for your account, a group, or one video. On Core and higher, the player then fires a PageView, two custom events for each click or answer, and progress events at 50 percent, 95 percent, and the video’s end, all from the viewer’s browser.
| Event | When the player fires it | What it carries | Plan |
|---|---|---|---|
| PageView | Once, when playback starts. | The pixel loads with your ID and records a page view. | Core and higher |
| MindstampInteraction | On each click, question answer, or comment. | interaction_type, interaction_value, correct, video_title, viewer_id, and more. | Core and higher |
| MindstampButtonClick, MindstampQuestionReply, and similar | Next to each MindstampInteraction, named after the element and the action. | The same parameters, under a name you can pick out in Events Manager. | Core and higher |
| MindstampProgress50, 95, and 100 | At 50 and 95 percent, and when the video plays to its end. | progress_percent, current_time, duration, video_title, and viewer_id. | Core and higher |
Paste your pixel ID. In Mindstamp, open Integrations, select Connect on the Facebook card, enter the ID in Facebook Pixel ID, and select Save. The app uses the Facebook name for the Meta Pixel. A video’s own ID wins, then its group’s, then the video owner’s account ID. See the Meta Pixel setup guide.
Core and higher. Player events on your page, the route for firing your own pixel events, also start on Core. See pricing.
No. Anonymous views fire the same events. The events carry a Mindstamp viewer ID and no name or email fields. To pass a known lead to your CRM, use HubSpot or webhooks.
During playback. The viewer’s browser fires the pixel when playback starts, at each click or answer, and at 50 and 95 percent and the real end of the video. An ad blocker in that browser can stop the events, so check them in the Test Events tool in Events Manager.
Yes for audiences. Meta custom audiences can use pixel custom events, such as MindstampProgress95 or MindstampQuestionReply. For custom conversions, confirm in your Meta account that a rule can use the event before you plan on it. An ad account allows 100 custom conversions.
Mindstamp fires the browser pixel only. Meta recommends the Conversions API alongside the pixel, and Mindstamp does not send it. For a server-side record of each view and answer, use webhooks and your own code.
Where to paste the pixel ID, every event name, and how to check them.
Explore →Listen for answers and clicks in the browser and fire your own pixel events, on Core and higher.
Explore →Where retargeting ads fit in multi-channel lead nurturing.
Explore →Send video progress events to your GA4 property as each viewer reaches 10 to 100 percent of a video.
Explore →See every view, answer, and click in Mindstamp, whatever you send to other tools.
Explore →Ask for a name and email inside the video, so a view can belong to a known person.
Explore →Each link opens the page we used for the steps, versions, and limits above.
Facts checked October 12, 2026 against the Mindstamp app and Meta Pixel’s documents. Meta Pixel can change its product. Before you rely on the data, send one test view and check that it arrives.
Paste your pixel ID, play one test view, and find MindstampInteraction in Test Events.