Events reference

Capture analytics events from the Experiences SDK by listening to the onEventTriggered callback. Each callback invocation delivers a single event payload (a data object) that describes what happened.

These docs use tables as a formatting choice to list and explain the fields that can appear in the event payload. They are not database tables.

How events work

• Source of truth: Events are emitted by the Experiences SDK at runtime. Your integration decides whether and where to forward them.
• Event identity: Each callback contains an event_category and an event_action that describe what happened.
• Event fields: Some fields are always present (common fields). Others are included only for specific surfaces (Story, Moment, Video, Widget, Ad, Interaction) or specific actions.
• Variants: Some fields are grouped under variants (for example, User (Variant) and Tech (Variant)). In these tables, the Field column shows the group name and the Field data column shows the nested field name.

Set up event collection

• iOS: onEventTriggered
• Android: onEventTriggered

Event categories

Use the pages below to see which event_action values exist for each event category, and which category-specific fields are included in those events.

• Moments: See Events // Moments.
• Stories: See Events // Stories.
• Videos: See Events // Videos.
• Widgets: See Events // Widgets.
• Ads: See Events // Ads.
• Interactions: See Events // Interactions.

Common fields

The tables below document the common fields that can appear in the callback payload.

Data export (optional)

Some integrations forward SDK events to a data warehouse. If you have an export pipeline, you might see fields and variants represented in tables.

Don’t assume you have access to internal warehouse schemas. Treat this section as an SDK reference unless your WSC Sports representative confirmed a data export for your account.