Flowtag Docs

Event Browser

Explore event volume, names, and property values.

The Event Browser is where you work with events rather than visitors. It has three available screens — Statistics, Catalog, and Explorer — plus a Feed that is not yet released. Opening the Event Browser lands you on Statistics.

Statistics

Volume and trend for every event type in a range you set to the minute.

Four cards summarise the range: Total Events, Event Types, Avg Events / Session, and Sessions with Events (shown against total sessions). Each carries a comparison badge against the immediately preceding window of the same length — pick the last 24 hours and it compares against the 24 before that. Definitions are in Metrics.

Below the cards, an area chart shows total event volume over time, and a ranked table lists each event type with its count, trend, and share of the total.

Selecting a type from the filter pills switches the view: the chart adds that type's own line against the total, and the table is replaced by four cards for that type alone — its Events, Share of Total, Trend, and Rank. Click a type in the table to jump straight to it in the Catalog.

Catalog

The Catalog answers "what have we ever sent, and with what values". It is a three-level drill-down:

  1. Event names — every distinct name recorded for the selected type.
  2. Property keys — the properties seen on the selected event.
  3. Property values — the distinct values seen for the selected key, with counts.

Each level has its own search box and pages in as you scroll. Your position is kept in the URL, so a particular slice of the catalog can be linked to directly.

Two reserved display values appear among property values: null for properties that were present but empty, and (other) for values beyond the 500-distinct ceiling Flowtag keeps per property. Seeing a large (other) bucket means that property is high-cardinality — an ID or a timestamp — and would be better split into a lower-cardinality field.

Property values longer than 256 characters are stored truncated.

Explorer

The Explorer presents the same catalog data as an expandable property tree, optimised for scanning rather than drilling. Use it to survey what a set of events looks like; use the Catalog when you know which property you want to inspect and need its values ranked.

Feed

A real-time stream of events as they happen. Marked Soon in the sidebar and not yet available — the screen is a placeholder. For near-real-time confirmation that events are arriving, use the Active (last 30 min) card on the Dashboard and the Statistics screen with a short range.

Working with custom events

The Event Browser is most useful for events you send yourself. A workflow that works well:

  1. Instrument the action with flowtag.capture(), using a stable name and putting the varying detail in properties.
  2. Confirm it arrives on Statistics with a short range, filtered to the event type.
  3. Once volume builds, use the Catalog to check the property values are what you expect — this is where typos, undefined, and accidentally high-cardinality values become obvious.

Events are throttled on both the client (once per second per event name) and the server (once per session every 3 seconds). If you fire several events in a tight loop, expect to see fewer than you sent. This is a quota guard, not a bug — see rules and limits.

On this page