CDP · Segment
Segment + TrackPlay
If Segment is your pipe, video should not be the one thing that bypasses it.
CDP
How it works
Copy
analytics.track('Video Progress', {percentComplete: 75})
1
Track calls for player events
Video Played, Video Paused, Video Progress at 25, 50, and 75 percent, Video Completed, and CTA Clicked. Every call carries the video code, straight into your existing source.
Destinationsyours
GA4on
Metaon
Warehouseon
2
Fan out from there
Send it wherever Segment already sends everything else.
Where conversions travel
The sale completes on your cart's domain after the video page is gone, so it is not a browser event. TrackPlay carries conversions server-side to Meta CAPI, GA4, and TikTok Events API, and your cart's own Segment source stays the system of record for orders.
Segment questions
Yes: Video Played, Video Paused, Video Progress at 25, 50, and 75 percent, Video Completed, and CTA Clicked, each with the video code.
TrackPlay injects Segment's standard analytics.js snippet with your write key on pages where your video is embedded. Create or open a JavaScript source in Segment, copy its write key, and paste it into the Integrations tab.
No. Purchases happen on your cart's domain and travel server-side to Meta CAPI, GA4, and TikTok. Your cart's own Segment source keeps owning order data.
Yes. Once the events are in Segment, every destination you have wired, including warehouses, receives them like any other track call.
The rest of your stack
TrackPlay talks to the tools you already sell with.
Browse all integrations ▶See which video earned the sale.
Free plan, 1,000 plays a month, no card.
Free plan. No card required.