Need to integrate events? See the Quick Start Guide for the basic integration pattern.
How Pixel Events Work
Pixel events are generated when:- Tracking pixels are configured in your TrackPlay dashboard
- Trigger conditions are met (specific time or percentage)
- Session rules are satisfied (call once vs. multiple times)
Event Naming Convention
Pixel events follow this naming pattern based on the actual code:- Facebook pixels:
pixel_event_{FB_ID} - Google pixels:
pixel_event_{GOOGLE_ID} - Custom pixels:
pixel_event_{CONTENT_HASH}
Event Data Structure
All pixel events share this data structure:Facebook Pixel Events
Configuration
Facebook pixels are configured with:- Facebook Pixel ID (e.g., “123456789”)
- Trigger timing (time or percentage)
- Call frequency (once per session or multiple times)
pixel_event_123456789
Data:
Google Pixel Events
Configuration
Google pixels are configured with:- Google Ads ID (e.g., “AW-987654321”)
- Conversion Label (e.g., “abc123”)
- Trigger timing (time or percentage)
- Call frequency (once per session or multiple times)
pixel_event_AW-987654321
Data:
Custom Pixel Events
Configuration
Custom pixels are configured with:- Custom HTML/JavaScript code to execute
- Trigger timing (time or percentage)
- Call frequency (once per session or multiple times)
pixel_event_custom_lead_gen
Data:
Complete Integration Example
Data Structure
All pixel events include these fields:time: Time when pixel was triggered (seconds)percentage: Percentage of video completed when triggeredsession_id: Unique device/session identifier
Related Events
- Video Events - Core playback events
- Timed Events - Custom events at specific times
- User Events - Interface interaction events
Configuration
To set up pixel events:- Configure pixels in your TrackPlay dashboard
- Set trigger conditions (time or percentage)
- Choose call frequency (once per session or multiple times)
- Test pixel firing in browser developer tools
- Listen for events in your JavaScript code
