Segment + TrackPlay: video events
If Segment is your pipe, video should not be the one thing that bypasses it. Every player event arrives as a track call.
Track calls, fanned out everywhere
TrackPlay injects Segment’s standard analytics.js snippet with your write key on pages where your video is embedded.
- Every call carries the video code
- Sent wherever Segment already sends everything else
- Warehouses receive them like any other track call
Live in three steps
One write key. No code.
Open a JavaScript source
Create or open one in Segment.
Copy its write key
Paste it into the Integrations tab.
Watch events arrive
Player events land in your source, then every destination.
The events Segment receives
Standard track calls, each with the video code.
Video Played- Playback starts
Video Paused- Playback pauses
Video Progress- At 25, 50 and 75 percent watched
Video Completed- Video finished
CTA Clicked- A CTA is clicked
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.
Works with the rest of your stack
Send the same events wherever you measure. Browse all integrations
Segment questions
Does TrackPlay send video events to Segment?
Yes: Video Played, Video Paused, Video Progress, Video Completed, and CTA Clicked, each with the video code.
How does the Segment integration load?
TrackPlay injects Segment's standard analytics.js snippet with your write key on pages where your video is embedded.
Does TrackPlay send purchases to Segment?
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.
Can I route TrackPlay events to my warehouse?
Yes. Once the events are in Segment, every destination you have wired, including warehouses, receives them like any other track call.