Skip to content
Quantalog
All docs

Segments & markers

Save the filters you use often, and annotate your charts with deploys, campaigns, and incidents.

Two small things that make the dashboard yours: segments save a filter you keep coming back to, and markers put your deploys and campaigns on the chart so a change in traffic has a cause next to it.

Saved segments

Clicking any row on Analytics filters the whole dashboard by it — a country, a browser, a landing page. Stack a few and you have a view like "mobile visitors from Google". Without saving, that view has to be rebuilt by hand every time you want it.

Once a filter is applied, Save segment appears next to it. Name it and it joins the segment list at the top of the page.

  • Click a saved segment to apply it. Click again on a different one to switch.
  • Pin the ones you use daily — pinned segments sit in the bar as one-click chips, the rest stay in the menu.
  • Segments belong to a workspace, since the pages and campaigns they reference only exist there.
  • Names are unique per workspace, so an existing name is reused rather than duplicated.

Timeline markers

Analytics tells you traffic changed on Tuesday. It cannot tell you a release went out Tuesday morning. Markers close that gap: a labelled vertical line on the traffic chart for anything worth remembering.

The flag icon beside Traffic over time opens the marker dialog. Give it a label, pick a kind, and it appears on the chart from that moment on.

  • Deploy — a release. The default, and the common case.
  • Campaign — an ad going live, a newsletter, a launch post.
  • Incident — an outage or a bug. Drawn in red, so it stands out from routine markers.
  • Note — anything else worth annotating.

Markers default to the current time and can be backdated, which is what you want when recording something that already happened. Several markers landing in the same point on the chart collapse into one line labelled with how many.

Marking deploys automatically

Markers are most useful when nobody has to remember them. Post one from CI over the Platform API and every release annotates itself:

  • POST /v1/markers with your API key, a label, and optionally kind, description, and at.
  • Omit at and the marker is stamped with the moment the request arrives — right for a deploy hook.
  • GET /v1/markers lists the most recent hundred.

A commit sha in description is worth the extra field: six months later it is the difference between "something shipped" and knowing exactly what.