The thread
1
Someone watches
You embed one snippet. The player starts, and TrackPlay opens a session for that
viewer: where they came from, which ad, which affiliate, which device.
2
The video does its job
Autoplay with sound on one click. A CTA at the exact second the offer lands. A pixel at
75% watched, not on page load. A form when they want the rest, not before they care.
3
They buy
Every cart link on the page is silently tagged with that session. The session rides
into the checkout.
4
The sale comes back
Your cart posts it back. TrackPlay joins it to the session, and so to the play, the
ad, the affiliate, and the split-test arm.
5
You find out what worked
Not “4,812 people pressed play”. Which second moved the buyer.
The pieces
The player
What the viewer sees, and every lever that makes it sell.
The embed
One snippet. ClickFunnels, GoHighLevel, Kajabi, WordPress, or your own build.
Integrations
Your cart posts the sale back so it can be credited.
Analytics
Retention, funnel, source economics, player quality.
Split tests
Winner picked on real sales, with a real significance test.
The API
Send events and conversions from your own backend.
Viewer identity
Session, device, profile: how one viewer stays one viewer across a sale.
Two ideas worth understanding early
The session is the thread. Almost everything here (a conversion, a custom event, a CRM tag, a retention curve split by buyer) works by landing on the viewer’s session. When something comes back unattributed, it is because the session never reached it. The Custom Events API is blunt about this: it tells you"attributed": false rather than guess, because a fabricated session would corrupt your
traffic sources and your affiliate payouts.
A custom event is not a conversion. Events are things that happened. Conversions are
money. TrackPlay keeps them apart on purpose, so a quiz completion can never quietly
inflate your revenue, ROAS or EPC.
Ready? Get your first video live.