Skip to content
Resources / Glossary

Payload (event properties)

The object you write alongside the event name, carrying contextual properties that land on the event row in your database.

CallsAlso called: properties, event properties

About this term

This page is part of the Skene analytics instrumentation glossary. Use it as a reference when writing specs, dashboards, or playbooks.

Canonical glossary index: /resources/glossary

Definition

The payload is the object you write for an event: supabase.from('events').insert({ name: 'checkout_completed', plan_tier: 'pro', amount: 99 }). Each key maps to a column on the event table, queryable in filters and breakdowns.

Payload properties are what let a report split one event into segments, such as checkouts by plan tier. Most analytics tools accept whatever keys and types a payload carries, so the same property can arrive as a string in one release and a number in the next. A schema registry, sometimes called a tracking plan, records the payload shape each event should carry. A renamed, dropped or retyped key is an altered payload, and the event count looks normal while the breakdowns built on that key change.

Why payloads break quietly

Most SDKs accept arbitrary keys, so renaming plan to plan_tier does not raise an error. The new event keeps flowing under the new name. Any dashboard filter or breakdown that referenced plan silently returns nothing.