« HELP CENTER

Flite Metrics 3 > Framework

Event/Session Metadata

This article lists the metadata and supporting information that is tracked for each event. The same items are tracked regardless of the event’s type. Some of this data is about the event, and some of it is about the session of which the event is a part. We go over both here.

The metrics that are mentioned below are NOT available in the standard reports users see in Flite reporting. These metrics are all captured to our database, but again not exposed in our standard reporting. In order to request these metrics, the Flite team will need to build a custom report for an additional fee that can be discussed with your Account Manager.

Event Metadata

In addition to the descriptive data logged when an event is tracked (see Anatomy of an event), there is also some additional metadata that gets recorded. We list this additional data below. 

  • Sequence: An event’s sequence number denotes its order with respect to the other events in the same session. Event 0 is always the Impression event that is logged when the ad is loaded. Each consecutive event is given the next available integer number. Event contexts and triggers use sequence numbers to refer to other events within the session.
  • Server Timestamp: The server-side timestamp for when this event occurred, in milliseconds of Unix time (milliseconds elapsed since the start of 1970, UTC).
  • Client Timestamp: The client-side timestamp for when this event occurred, in milliseconds of Unix time (milliseconds elapsed since the start of 1970, UTC).
  • Component ID: The ID of the component that logged this event. Many Flite components log their own events. For a list of events logged by each of Flite's built-in components, open Ad Studio help and browse to the documentation for each individual component.
  • Component: The name of the component that logged this event.

Session Metadata

In addition to information about your event, a lot of session metadata is also logged along with each event. A session begins when the ad loads (typically because the user has browsed to a page where the ad is running), and ends when the ad unloads (typically because the user has left the page).

The following session metadata is logged by all Flite events:

  • Session ID: The unique 32-digit hexadecimal identifier for this session.
  • URL: The URL of the page where this ad impression is running.
  • User Agent: The user’s browser’s user agent string. This includes information about the user’s environment, OS, browser, etc.
  • Language: The user’s locale and language.
  • Remote IP: The user’s IP address.
  • Latitude/Longitude: The user’s latitude and longitude, based on their IP address.
  • Country Code: The user's two-letter country code. See here for a full list of country codes.
  • Region: The user's region code; for the US and Canada, this is the 2-letter abbreviation of the user’s state/province (see here for list); for other nations, this is a numerical code corresponding to a particular region/province (see here for list).
  • City: The user’s city.