A Segment is a saved, reusable set of filter criteria that you build once and apply anywhere in the Blue Triangle portal that supports it — giving you (and anyone you share it with) a consistent, repeatable view of the same slice of data, without rebuilding the same filters on every page.
Not the same as Environment or Session Variable. Segments are unrelated to the per-visitor tagging fields formerly called Traffic Segment (now Environment) and AB Testing Segment (now Session Variable). Those are configured by your Blue Triangle representative in the site's tag setup and show up as individual filter fields. A Segment, by contrast, is a self-service saved combination of filters that you build and manage yourself. See the Environment and Session Variable articles linked below for those.
What a Segment is
A Segment is a collection of filters — Device, pages visited during the session, performance thresholds, and so on — saved under a name so you can re-apply the exact same definition instead of resetting filters by hand. Segments are managed from a dedicated Segment management page, where you can:
-
Create and edit a segment
-
Clone an existing segment
-
Delete a segment
-
Copy a segment from one site to another within your account
Each site is currently limited to 10 saved segments.
A segment's data origin (for example RUM vs. Native) is locked in when you create it, since data origin determines which filters are even available — you choose it first, before defining the rest of the segment's criteria.
Applying a Segment
On a supported page, an Apply Segment control sits at the top of the filters menu (and at the top of the filter modal on pages that open filters in a modal, like the Data Science comparison wizard). Clicking it opens a list of your available segments to choose from; selecting one and applying it fills in the page's filters as if you'd set them manually. Once applied, the button relabels to Change Segment, with a small "x" next to it to remove the segment.
A few behaviors worth knowing:
-
Local filters layer on top, and override rather than combine. If you apply a segment and then also set a local filter that overlaps with something the segment defines (for example the segment defines an average and you set a percentile on the page), your local filter setting wins for that field — it doesn't merge with the segment's setting.
-
Applying a segment does not reset your other filters. Anything else you already had set stays as-is.
-
Segments are stored in session storage. An applied segment will still be there if you refresh the page, but it won't carry over into a new tab or survive closing the browser.
Comparing with Segments
On pages that support comparisons — currently Revenue Calculator, Bottom of the Sales Funnel, Data Science (Custom Comparison), and the RUM/Native Aggregate Waterfall pages — you can compare Segment vs. Segment or Segment vs. a custom filter set. When you open a comparison, it defaults to comparing against whatever segment (if any) is already applied on the main view; from there you can change or remove the comparison segment independently. Unlike the main applied segment, a comparison segment selection isn't saved — it won't still be there the next time you load the page.
Where Segments are available today
Segments support is rolling out page by page rather than all at once. As of this writing, it's live on:
-
Revenue Calculator
-
Performance Detail (RUM and Native)
-
Performance Overview
-
JavaScript Errors — Native and Real User, including drilldowns
-
Bottom of the Sales Funnel
-
RUM and Native Aggregate Waterfall (object-level trending)
-
Data Science / Custom Comparison
-
A set of preconfigured Dashboard widgets (performance, revenue, conversions, bounce rate, device and geography breakdowns, and more)
Still in progress or pending further work: Customer Journey, Revenue Attribution, and Revenue Opportunity (the latter two need process updates on top of the core Segments work), and Session Details.
Known limitations (current state)
-
Segment-defined performance criteria currently support averages only — percentile-based conditions aren't supported inside a segment yet.
-
A page-based condition in a segment (e.g. "Home has 10+ hits") evaluates at the session level — it looks for sessions containing a matching page hit, not a restriction that only that page's data is included in the session.