Pixel Custom Events Table

pixel_custom_events_table

The Pixel Custom Events table captures every fire of custom events you've defined on your site (form fills, scroll depth, quiz steps, etc.), including the raw event data payload. One row per event fire. Learn more about tracking custom events with Triple Pixel.

📋
Table Guide
What You Can Answer With This Table

How many times did a specific custom event fire, and how has that trended? — use event_name, count, group by event_date

Which custom events are most active across the site? — use event_name, count, group by event_name

What context did visitors submit with an event (e.g., answers, form values)? — query the data JSON payload (learn more)

What custom events happened during a specific page view? — use page_view_event_id, event_name

Before You Query

Required field: event_date

Custom event properties are flattened into queryable columns automatically when events are defined via the Custom Events Builder. For events not created via the builder, query properties from the raw JSON data payload.

When to Use a Different Table

For attribution of conversion events to channels, campaigns, or ads → use Pixel Custom Conversions. The same event fires appear in both tables: this table has the raw event data payload with no attribution; Pixel Custom Conversions adds channel, campaign, ad, attribution model, attribution window, and conversion value — but only for events marked as conversions.

View the full Triple Whale Data Ontology →

Dimensions

Dimensions are immutable properties that can be used for grouping data.

Title	ID	Type	Description
Event Hour	`event_hour`	string	The hour of the day the pixel custom event occurred, according to a 24-hour clock. Based on the shop time zone at the moment of the event (or the user time zone, if no sales platform is connected). Example values: `07`, `16`, `21`
Event Date	`event_date`	date	The date the pixel custom event occurred. Based on the shop time zone at the moment of the event (or the user time zone, if no sales platform is connected).
Event Day	`event_date.day`	date	The day on which the event occurred. Derived from `event_date`.
Event Week	`event_date.week`	date	The Sunday of the week during which the event occurred. Derived from `event_date`.
Event Month	`event_date.month`	date	The month during which the event occurred. Derived from `event_date`.
Event Quarter	`event_date.quarter`	date	The first month of the quarter during which the event occurred. Derived from `event_date`.
Event Year	`event_date.year`	date	The year during which the event occurred. Derived from `event_date`.
Pixel Custom Event Data	`data`	JSON	The full data payload in raw JSON format, including all event properties defined for the custom event. Learn more about querying pixel custom event data
Event Name	`event_name`	string	The name assigned to the custom event. Example values: `form_fill`, `start_quiz`, `quiz_complete`, `order_sample`, `answer_question`, `request_consultation`
Event Timestamp	`event_timestamp`	timestamp	The time the custom event occurred. Formatted according to the ISO 8601 international standard. Example value: `2022-06-15T19:26:30.000Z`
Page View Event ID	`page_view_event_id`	string	The unique ID for the page view event during which the custom event occurred. Assigned by Triple Pixel. Example value: `9m4rs48lg2elVB52xU`
Triple Pixel ID	`triple_id`	string	The unique ID assigned by Triple Pixel to track visitors across sessions. Example value: `eltlok4y634IRw62AZ`

Derived

Derived fields are metrics that are pre-calculated using multiple measures or advanced formulas.

Title	ID	Type	Description
Pixel Custom Events	`count`	formula	The total number of pixel custom events recorded within the selected timeframe.

Updated 16 days ago