Skip to main content
Events that fire when conversion tracking pixels are triggered based on video engagement. These events correspond to Facebook pixels, Google pixels, and custom tracking pixels configured in your dashboard.
Need to integrate events? See the Quick Start Guide for the basic integration pattern.

How Pixel Events Work

Pixel events are generated when:
  1. Tracking pixels are configured in your TrackPlay dashboard
  2. Trigger conditions are met (specific time or percentage)
  3. Session rules are satisfied (call once vs. multiple times)
Each pixel configuration creates a corresponding event that you can listen to.

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)
Event: 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)
Event: 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)
Event: 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 triggered
  • session_id: Unique device/session identifier

Configuration

To set up pixel events:
  1. Configure pixels in your TrackPlay dashboard
  2. Set trigger conditions (time or percentage)
  3. Choose call frequency (once per session or multiple times)
  4. Test pixel firing in browser developer tools
  5. Listen for events in your JavaScript code