Fire ad pixels on VSL watch time
Send Meta, TikTok and Google Ads an event when a viewer crosses a watch-time milestone, from the browser and from our server.
The milestone that predicts a buyer
From the browser and from our server.
Pick the second
Fire at 25%, 50%, 75% or a timestamp you choose: the milestone that predicts a buyer on your offer.
A server-side copy
At 25, 50, 75 and 100 percent and at any timed event you name, our server posts a ViewContent to Meta CAPI and the TikTok Events API. A blocked pixel does not stop it.
Then send the real sale
When your cart posts back, the order goes to the ad platform as a purchase, attributed to the play.
Stop teaching Meta to find bouncers
A page-load pixel reports every two-second bounce. Fire on watch time and the algorithm finds people who listen.
The whole player, on every plan
Questions about Watch-Time Pixel Firing
When can a pixel fire?
At 25%, 50% or 75% of the video, or at a timestamp you choose. Pick the milestone that predicts a buyer on your offer.
Which ad platforms are supported?
Meta, TikTok and Google Ads. Events go to the Meta Conversions API and the TikTok Events API from our server as well as from the browser.
What happens if the browser pixel is blocked?
The server-side copy still goes: our server sends Meta and TikTok a ViewContent at your watch milestones whenever the session carries a click id or a known email. Purchases carry an event id built from the order, so the browser and server copies of a sale count once.
Can purchases be sent too?
Yes. When your cart posts back, the order goes to the ad platform as a purchase, attributed to the play that earned it.
Why not fire on page load?
A page-load pixel reports every two-second bounce as a signal, and the ad platform finds you more of them. Firing on watch time optimizes for people who listen.