Create free account
Solutions Paid traffic

A video 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.

Create your free account See pricing
75%Fire events at any watch mark
3Server-side destinations, deduped
1,000Free plays a month, no card
Events · todaylive
75% watched → Meta CAPI312
50% watched → TikTok Events495
Purchase postback → Meta41
Browser + server, deduplicatedon
CAPI event sent · 75% watched

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.

01 / 05
Chapter 01

Watch-time events

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.

Event rules3 active
75% watched → Meta CAPIfired
50% watched → TikTok Eventsfired
Pitch reached (12:40) → GA4waiting
Chapter 02

Server-side delivery

Events go from our server to Meta CAPI, TikTok Events and GA4, deduplicated against the browser pixel. Ad blockers and iOS do not get a vote.

Deliverydeduped
Browser pixelblocked
Server eventdelivered
Chapter 03

Retargeting by watch depth

Build audiences from viewers who reached the pitch instead of everyone who loaded the lander. Warm traffic that actually heard the offer.

Audiencesby watch depth
Loaded the page4,812
Watched 50%+1,391
Reached the pitchyour retargeting list
Chapter 04

Cart postbacks with click ids

We capture the click id on the way in and hand the purchase back to the platform with it attached. The sale lands on the ad that earned it.

Purchase$118.00
fbclidcaptured
Sessionstitched
Sent to Metaattributed
Chapter 05

Breakdown by campaign

Watch time, drop-off and revenue split by UTM, campaign and creative. See which ad buys watchers and which buys bounces.

Breakdownby utm_campaign
hook-a · TikTok★ $1.98 / play
hook-b · Meta$0.61 / play
How it works

Teach the algorithm who actually watches.

One embed on the lander, and your ad account starts learning from attention instead of page loads.

Click idscaptured
fbclid · ttclid · gclidon arrival
Affiliate sub-idsride along
1

Embed

Put the player on your lander. It captures click ids from the major ad platforms the moment the visitor arrives.

Event rulesyours to set
75% → Meta CAPIbrowser + server
Pitch reached → TikTokbrowser + server
2

Pick the moments

Choose the watch marks that matter and point them at Meta, TikTok or Google. Browser and server side, deduplicated.

Optimisation signalthis week
Watch-time events2,140
Purchases, click id attached41
3

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

A conversion event with the click id, event time and your chosen watch mark, sent to the Conversions API and deduplicated against the browser pixel.
Yes. Percentages or an exact timestamp, set per video and per platform.
The server-side copy still goes. That is the point of firing from our infrastructure instead of only from the page.
No, it feeds it. RedTrack, Everflow, GTM and Segment take the same events, and webhooks cover anything else in the stack.
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.
Nothing. 1,000 plays a month free with the full player, watermarked. No card, no time limit.

Send your ad account a better signal.

Create a free account, embed one video, and fire your first watch-time event today.

Create your free account

Free plan. 1,000 plays a month. No card.