Route
List the actual paths: browse → compare → stall → buy, or browse → support → leave. Delete journeys that only exist in the brand film.
Custom method page
A public sketch of how Switch Routehub reads customer routes and names Behavioral Segmentation Analytics work so it can survive a Thai trading calendar.
Four plates
Teams often want a single map. We refuse that. A segment that cannot be traced through these four plates is still a persona with extra charts.
List the actual paths: browse → compare → stall → buy, or browse → support → leave. Delete journeys that only exist in the brand film.
Keep recency and frequency. Add one third axis. Ban vanity scores that cannot change a media or CRM action within a quarter.
Write inclusion, exclusion, volume floor, and sunset. If two cohorts overlap more than a fifth of members, one name must die.
Define shocks: Songkran, 11.11, monsoon delays, influencer weeks. Composition change fires an alert even when total volume looks healthy.
What the atlas is not
The Atlas is a judgment framework. It does not ingest events, train a model, or output lookalike audiences. Those jobs stay in your stack. We use the Atlas in Cohort Signal Architecture so students argue about names with the same vocabulary.
If your team only needs the language, read the journal notes on recency in Thai retail and on micro-segment splits. If you need the craft with critique, take a room.
A Bangkok multi-category retailer arrived with seven “behavioral” segments. Three were recency relabelled. One was a persona named after a campaign. Two overlapped almost completely after identity joins. One — “category retreat after first appliance buy” — survived all four plates. That single name funded a quieter CRM track and killed a lookalike that had been targeting recent buyers as if they were still browsing.
The Atlas did not invent that segment. It forced the other six to fail in public.
Browse courses or write to the studio with the plate where your current map breaks.