A VSL player that talks to your ad accounts
Your pixel fires on page load, so you retarget people who bounced at second three. TrackPlay fires it on watch time instead.
The pixel fires on page load. That is the problem.
Meta and TikTok optimise toward whatever you send them. Send page views and they find people who load pages. Send watch-time events and purchases, and they go find people who watch and buy. TrackPlay moves the event to the moment that predicts the sale.
Fire at the second attention is paid
Fire Meta, TikTok and Google events at 25, 50, 75, 95 percent or an exact second. The event means attention was paid, not that a page loaded.
Breakdown by campaign
Watch time, drop-off and revenue split by UTM, campaign and creative. See which ad buys watchers and which buys bounces.
Retargeting by watch depth
Build audiences from viewers who reached the pitch instead of everyone who loaded the lander.
And the sale goes back too
The last two links in the chain, handled server-side. See Meta Conversions API, VSL hosting or all features.
Ad blockers and iOS do not get a vote
Events go from our server to Meta CAPI, TikTok Events and GA4, and each purchase carries an event id built from the order, so it is counted once.
Cart postbacks with click ids
We capture the click id on the way in and hand the purchase back with it attached. The sale lands on the ad that earned it.
Teach the algorithm who actually watches.
One embed on the lander, and your ad account starts learning from attention instead of page loads.
Embed
Put the player on your lander. It captures click ids from the major ad platforms the moment the visitor arrives.
Pick the moments
Choose the watch marks that matter and point them at Meta, TikTok or Google, from the browser and from our server.
Let it learn
Purchases post back with the click id attached. Your campaigns optimise on watchers and buyers, not page loads.
Paid traffic questions people actually ask
What exactly gets sent to Meta?
A ViewContent event at your watch milestones and a Purchase when the cart posts the sale back, each with the click id and event time, sent to the Conversions API. The Purchase carries an event id built from the order, so you can deduplicate it against your browser pixel.
Can I fire at an exact second instead of a percentage?
Yes. Percentages or an exact timestamp, set per video and per platform.
What happens when the browser pixel is blocked?
The server-side copy still goes. That is the point of firing from our infrastructure instead of only from the page.
Does this replace my tracker?
No, it feeds it. RedTrack, Everflow, GTM and Segment take the same events, and webhooks cover anything else in the stack.
Which click ids do you capture?
Meta, TikTok and Google click ids plus the other major ad platforms, and affiliate network sub-ids. They ride along on every event and postback.
What does it cost to try?
Nothing. 3,000 plays a month free with the full player and every feature. No card, no time limit.