v0.0.12

Three releases' worth of notes — v0.0.10 and v0.0.11 never got their own.

Maps — v0.0.10

A new insight type that measures any metric per country, so you can see where traffic comes from on a map instead of in a list. Every country with traffic is returned; there's no top-10 cutoff to pick. This shipped as the API only — the map in the dashboard comes separately. Countries Pug can't confirm are dropped, so the rows won't sum to your project total.

Stream replicas are a deployment setting — v0.0.11

Self-hosters only: how many copies Pug keeps of each message stream now comes from NATS_STREAM_REPLICAS instead of being baked into the image. It defaults to 1, which is what single-node installs already ran, so nothing changes unless you set it. On a NATS cluster, set it to your cluster size and re-run the migrate job — the job refuses obviously wrong values rather than quietly leaving your streams unreplicated.

Identity resolution in insights — v0.0.12

One person usually shows up in Pug under more than one ID — first as an anonymous visitor, then under the ID your app gives them once they sign in. Funnels and retention used to count those as two separate people; now Pug stitches them back together at query time.

Your numbers will move when you upgrade. Conversion rates, time-to-convert and retention curves go up for any project that calls identify() — the old numbers were splitting one person in two. Trends and unique-visitor counts are deliberately left alone, and visitors who declined cookies are never stitched to anyone. Upgrading is just the images: no migrations, no config changes, no API changes.