# comparisons

> Claude/Codex skill by [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars · Updated 2026-10-22

How to structure A vs B comparisons in Fullstory — when to use dimensionality (event/session properties) vs separate segments (user-level properties), and why the distinction matters for correctness.

## Install

```sh
git clone https://github.com/fullstorydev/fullstory-skills /tmp/fullstory-skills && ln -s /tmp/fullstory-skills/skills/comparisons ~/.claude/skills/comparisons
```

## From README

Comparisons When the user asks to compare A vs B, the right mechanism depends on what the comparison axis is. Use the decision table below to classify it — the user doesn't need to know this distinction exists. Event/session properties → dimensionality If the comparison axis describes the context of an individual event at the moment it fired — not the user who triggered it — use dimensionality. Common examples: device type, browser, OS, page URL, element. But the rule is the principle, not the list: if the property travels with the event, not the user, it belongs here. Express it as a single topn metric with the comparison axis as the grouping dimension. Example: "rage clicks on mobile vs desktop" → fullstory:buildmetric(query="rage clicks by device type", outputtype="topn"). The result table shows mobile and desktop as separate rows.

## Links

- HTML page: https://omgskills.com/library/fullstorydev/fullstory-skills/skills/comparisons/
- GitHub: https://github.com/fullstorydev/fullstory-skills
- Author: [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md)

## More from this repo

- [friction-analysis](https://omgskills.com/library/fullstorydev/fullstory-skills/skills/friction-analysis/index.md) — Finds where users struggle on a page or flow and whether a suspected problem is real.
   - [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars
- [general-analysis](https://omgskills.com/library/fullstorydev/fullstory-skills/skills/general-analysis/index.md) — Fullstory analytics workflow — the default way to answer any question about user behavior.
   - [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars
- [session-review](https://omgskills.com/library/fullstorydev/fullstory-skills/skills/session-review/index.md) — Used when diagnosing user-reported issues, investigating bugs, analyzing user behavior, or validating UI correctness...
   - [@fullstorydev](https://omgskills.com/library/fullstorydev/index.md) · 11 stars