« HELP CENTER

Flite Metrics 3 > Framework

Anatomy of an event

Each event tracked by a Flite ad has many different properties. We discuss all of these properties here.

  • Type: The high-level category that this event falls into. Flite ads fall into four Types: Impressions, Interactions, Content events, and Notations. See Event Types for more details.
  • Subtype: This is a refinement of the event’s Type, categorizing it more precisely. For instance, Interactions have many different subtypes depending on how the user interacted with the ad – Hover, Scroll, Control, Navigate, etc. See Event Types for more details.
  • Mode (Interactions only): This indicates the mechanics of the Interaction – e.g. Click, Drag, Rollover, etc. Keystrokes are not currently tracked; only mouse interactions are tracked.
  • Detail: This gives additional detail about this event. For each event Type and Subtype, the Detail field may mean different things. For video Control Interactions, it is the function of the control (Play, Pause, etc.); for Navigate Interactions, it’s the name of the layer you are navigating to; for Scroll Interactions, it’s the name of the layer being scrolled; etc.
  • Context: A number indicating the event that provides the context for this event. Contexts are typically Content events, though an Impression can provide the context as well. For example, a video play Content event provides the context for Interactions like pausing, seeking, and muting that video, as well as for Notations that indicate the video's progress. Viewing a feed article provides the context for scrolling the article or clicking through to its source URL. See Event Relationships for more details.
  • Trigger (Content events only): A number indicating the event that triggered this event. Only events of type Content have triggers, and those triggers are typically Interactions. For instance, a video play Content event may be triggered by a button click Interaction. However, for automatic events, the trigger may not be an Interaction. For instance, suppose you have a video in your ad that begins playing as soon as the ad loads. The trigger in this case is the ad Impression itself. See Event Relationships for more details.
  • Event Data: Key-value pairs that list additional event-specific data. For instance, scroll events track the starting and ending position of the scroll; link clicks track the target URL of the link; video pause tracks the time at which the video was paused; etc.
  • Event/Session Details: In addition to the key properties and event-specific data described above, there is a lot of additional metadata and supporting information that is tracked for each event. See Event/Session Metadata for details.