« HELP CENTER

Flite Metrics 3 > Framework

Event Types

There are four top-level event types that Flite ads track: 

  • Impression: When the ad is loaded on a page.
  • Interaction: When a user interacts with an ad in some way.
  • Content: When something happens to a piece of content in your ad.
  • Notation: An event that is fully dependent on, and must occur in the context of, another event. It provides some additional information about its parent event, rather than being an independent event of its own.

Impressions

Flite ads make a distinction between three different impression subtypes:

  • Full: An impression that loads the Flash ad, and is able to handle expansions.
  • Limited: An impression that loads a Flash ad in an environment where expansions cannot be handled.
  • Backup: An impression that loads a backup image instead of the Flash ad.

Interactions

Flite ads track many different user interactions. For this reason, there are many different Interaction subtypes. We list these below. For built-in components, please refer to the individual component documentation for details about the interactions by those components. For third-party Flite Hub components, please refer to that component’s documentation for details.

  • Hover: When the user hovers over an ad for one second or more. This can also be used for hovers that force an action; for instance, in the Gallery Component, a hover can be used to show navigation controls.
  • Select: When the user selects something. This is typically used for selecting something that opens a URL outside of the ad (clickthroughs, shares, etc.).
  • Deselect: When the user deselects something.
  • Navigate: When the user navigates from one piece of content to another. This is typically used in Navigation Components, but can be used in any component where the user navigates between different pieces of content. For instance, the Feed Component uses this interaction subtype as well.
  • Scroll: When the user engages a scrollbar by either dragging the scroller or clicking the track.
  • Control: When the user engages a standard control element like a play or pause button, volume control, etc.
  • Legacy: This subtype is used for old Flite Platform 2 widgets or components that are integrated into an Ad Studio 3 ad. It should not be used for any other reason.

Content events

There are only two Content event subtypes that are currently used.

  • View: When a piece of content is brought into view. This is only used for content- or functionality-driven components. We do not typically use this for basic components (e.g. Shape, Text, Button, etc.) or for navigation components (e.g. Gallery, Button Set, Grid, etc.). However, when a Flite Hub component is loaded (e.g. Feed or Twitter), a Content View event is tracked.
  • Play: When the content starts playing. This is currently used for video components (Video:URL and Video: YouTube) only, when the video starts playing.

Notations

Only one Notation event subtype is currently tracked.

  • Update: An update about an event that is in progress. For instance, a video Play event records Update Notations when the video playback reaches certain milestones (one-quarter mark, halfway mark, etc.). The Hover event intermittently records Update Notations to indicate that the user's mouse pointer is still hovering over the ad, and records another Update Notation when the mouse pointer rolls out, ending the Hover event.