CS Events Table

cs_events_table

The CS Events table logs ticket lifecycle events like creation, closure, reopening, assignment, and message activity. One row per event.

📋
Table Guide
What You Can Answer With This Table

How many tickets are being created vs. closed each day? — filter by event_type, group by event_date

What percentage of closed tickets get reopened? — compare ticket-reopened vs. ticket-closed event counts

What types of ticket activity are most common? — group by event_type

Are events triggered by agents or by automations? — use user_id (NULL for automated events)

Before You Query

Required field: event_date

Event type filter: Use event_type to analyze specific lifecycle events. Values include ticket-created, ticket-closed, ticket-reopened, ticket-message-created, ticket-updated, ticket-assigned, ticket-unassigned.

Automated events: user_id is NULL when the event was triggered by an automation rule rather than a support agent.

Key Relationships
Table Join Key What the Join Enables
CS Messages object_id to ticket_id Message content, sender details, and AI intents for the ticket associated with the event

When to Use a Different Table

Need ticket metadata (agent, priority, status, tags, surveys) → CS Tickets table. CS Tickets has richer ticket-level detail; CS Events records when lifecycle changes happened but not the full ticket context.

View the full Triple Whale Data Ontology →

Table	Join Key	What the Join Enables
CS Messages	`object_id` to `ticket_id`	Message content, sender details, and AI intents for the ticket associated with the event

Dimensions

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

Title	ID	Type	Description
Event Date	`event_date`	date	The date the CS 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 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`.
Shop ID	`shop_id`	string	The unique ID of the shop (often corresponds to the shop domain). Can be used to group or filter data by shop in multi-store reports. Example values: `example-US.myshopify.com`, `example-EU.myshopify.com`
Shop Name	`shop_name`	string	The name of the shop. Can be used to group or filter data by shop in multi-store reports. Example values: `example-US`, `example-EU`
Platform	`platform`	string	The customer support platform through which the event was generated. Example value: `gorgias`
Event Created Date	`created_at`	timestamp	The time the event was created, in UTC. Formatted according to the ISO 8601 international standard. Example value: `2026-02-28 22:25:32`
Event ID	`event_id`	string	The unique identifier for the event, assigned by the CS provider. Example value: `15715626681`
Event Type	`event_type`	string	The type of CS event. Example values: `ticket-created`, `ticket-closed`, `ticket-reopened`, `ticket-message-created`, `ticket-updated`, `ticket-assigned`, `ticket-unassigned`
Object ID	`object_id`	string	The ID of the object this event relates to (e.g., a ticket or message). Example value: `380365041`
Object Type	`object_type`	string	The type of object this event relates to. `Ticket` for ticket lifecycle events (e.g., created, closed, reopened); `TicketMessage` for message events (e.g., a new message on a ticket). Example values: `Ticket`, `TicketMessage`
User ID	`user_id`	string	The ID of the user (agent) who triggered this event. NULL when the event was triggered automatically (e.g., by an automation rule). Example value: `416121112`

Updated 3 days ago