Calculated metrics with segments in Customer Journey Analytics

When you need this

Filtering an entire Workspace panel with a segment scopes every metric in it to that population - which is exactly wrong when you need one metric scoped to a segment while a second metric in the same table stays unscoped for comparison (mobile conversion rate next to overall conversion rate, in the same row). That comparison is only possible by building the segment into the calculated metric's formula itself.

It's also what makes a metric portable: a calculated metric with its segment baked in behaves the same way whether it's used in a freeform table, a summary panel, or shared into another analyst's project - a panel-level segment filter doesn't travel with the metric at all.

How to work with it correctly

1. Build the segment component directly into the calculated metric formula, not around it. Inside the Calculated Metric Builder, a segment can be dragged in as a container around a metric component - the resulting metric only counts activity within that segment, regardless of what else is on the panel.

Metric: Mobile Conversion Rate
Formula:
  [Segment: Device Type = Mobile] { Orders }
  ÷
  [Segment: Device Type = Mobile] { Sessions }

# Both the numerator and denominator are scoped to the same segment -
# scoping only one side produces a number that looks like a rate
# but isn't measuring the same population top and bottom.

2. Scope both sides of a ratio to the same segment, deliberately. The most common mistake is segmenting the numerator (mobile orders) while leaving the denominator unscoped (total sessions across all devices) - the result isn't a rate, it's a share, and reads misleadingly like the wrong thing if the person building the report doesn't catch it.

3. Name the metric so its segment scope is obvious without opening the formula. "Mobile Conversion Rate" tells a report reader what population it covers; "Conversion Rate 2" requires opening the builder every time someone questions the number.

4. Reuse an existing named segment rather than rebuilding the logic inline. If "Mobile visitors" is already a defined segment in the data view, reference it in the calculated metric instead of recreating the same device-type logic freehand - so a later definition change (a new device category) only has to be updated in one place.

How to verify it worked

• Drop the calculated metric into a freeform table with a panel-level segment applied to something unrelated (like date range only) and confirm the metric still reflects only its own built-in segment, not the panel's filter - proving the scoping travels with the metric.
• Manually cross-check the metric's value against the same numerator and denominator built as separate, panel-filtered metrics for a single date - the numbers should match exactly, confirming the formula's segment logic is equivalent to filtering the whole panel to that population.
• Place the segment-scoped metric next to its unscoped counterpart in the same row and confirm the two numbers are plausible relative to each other - a mobile rate wildly higher than the overall rate with no other explanation is worth checking the formula for an unscoped denominator.

Illustrative, not a measured result: a report that used to require two separate panels - one filtered to mobile, one unfiltered - to compare conversion rates side by side might collapse into a single table once both rates exist as properly segment-scoped calculated metrics.

The Calculated Metric Builder's segment-container interaction has changed across CJA releases - verify current builder behavior against Adobe's own documentation before training analysts on it.

FAQ

Is a segment-scoped calculated metric the same as filtering the whole panel?

No - a panel-level segment filter scopes every metric in that panel to the same population and doesn't travel if the metric is copied elsewhere. A segment built into the calculated metric's own formula stays scoped wherever the metric is used, which is what makes it possible to show a scoped and an unscoped metric side by side in one table.

Can a calculated metric use more than one segment?

Yes - different components of the same formula can each carry their own segment container, which is how you'd build something like a ratio comparing two different segments directly inside one metric, rather than two segments applied uniformly to the whole formula.