Ledger layer
Issue, expire, adjust, and burn — named so a campaign rename cannot orphan last year’s history. If finance and product disagree on a row, the Observatory stops until the row is named once.
Custom studio page
A method, not a product name. We use it whenever a mobile loyalty programme has more motion than meaning — points moving, passes updating, dashboards glowing, and nobody able to say whether guests are still attached.
Three layers we actually look at
Issue, expire, adjust, and burn — named so a campaign rename cannot orphan last year’s history. If finance and product disagree on a row, the Observatory stops until the row is named once.
Thai retail time is not ISO weeks. We map school holidays, festival fortnights, and monsoon travel before we draw a cohort. A “bad week” that happens every April is not an anomaly.
Repeat after non-discounted visits, intended burns versus clearance burns, and quiet hours that do not collide with wallet pings. This is the layer most vendor dashboards skip.
Observatory Circle seats leave with a two-page brief: the definitions you agreed, the window you will keep using, and one decision finance can fund or stop. We do not deliver a 40-slide pack. If your board requires slides, you already know how to make them; we refuse to impersonate a consultancy deck.
The method is taught inside Loyalty Signal Architecture and practised, with your live programme, only on Observatory Circle. Field Notes readers get the glossary and templates without the clinic.