Skip to content
pugdocs

Changelog, page 2

Releases Oct 5, 2026 – Jun 22, 2026.

2026

SSO

Single sign-on and verified domains

Org admins set it all up under Settings > SSO & domains.

New

  • Verify a domain your org owns with a DNS TXT record.
  • Auto-join adds anyone who signs in through SSO with an email on a verified domain, as a Viewer or Member.
  • Stop people on the domain from creating orgs of their own.
  • Require SSO makes SSO the only way in for the domain: passwords and email links stop working.
  • Connect your company’s identity provider, such as Okta, Microsoft Entra ID, Keycloak or any other OIDC provider, to your verified domains. The sign-in page sends people on those domains to it.

See SSO & domains.

Billing

Plans and billing

New

  • Settings > Billing shows your org’s plan, its monthly event allowance and how much of it you’ve used. Upgrade by card, and manage payment in the customer portal.
  • A meter in the sidebar tracks usage, and a banner warns as you near or pass the allowance.
  • Going over the allowance never blocks, slows or drops an event.

Changed

  • Your usage period starts on the day your org signed up, not on the 1st of the month.

Self-hosted servers have no plans or limits unless billing is turned on.

Insights

Bot traffic is left out by default

New

  • Headless browsers, synthetic monitors and scrapers are recognized by their user agent and tagged with $bot and $bot_reason. Nothing is dropped.
  • Insights, the Overview and dashboards leave bot traffic out. So do Events, Live and Profiles, which have an Include bots toggle to bring it back.
  • Bots carry a robot mark wherever they’re listed.
  • excludeAutomatedBrowsers in the web SDK stops tracking browsers driven by automation, such as your end-to-end tests.

Changed

  • Only events received since tagging began carry the tag, so older bot traffic still counts.

Insights

Funnels and retention follow people through sign-in

A person often shows up under two IDs: an anonymous one, then the ID your app gives them at sign-in. Funnels and retention counted them as two people. Pug now joins them when it runs the query.

Changed

  • Conversion rates, time to convert and retention rise for any project that calls identify(), past data included.
  • Trends and unique visitor counts are unchanged, and cookieless visitors are never joined to anyone.

See Anonymous to identified.

Insights

Map any metric by country

New

  • Map measures one metric per country, such as events, unique users, or the sum or average of a numeric property, for every country with traffic.
  • Dashboard tiles can show a map.
  • The Overview’s maps use it, so they cover every country instead of the top 50.
  • Countries Pug can’t confirm are left out, so a map can add up to less than the project total.

The Insights API runs it as INSIGHT_TYPE_MAP.

Privacy, SDKs

Count visitors without cookies

New

  • In cookieless mode the web SDK sends events with no identity and writes nothing to the device. Pug derives an ID from the request’s IP address and user agent, hashed with a salt that changes daily, and stores neither.
  • @pug-sh/browser 0.1.0 starts in cookieless mode. optInTracking() moves a visitor who accepts your banner to full tracking, and the SDK can honor Global Privacy Control.
  • beforeSend edits or drops any event before it leaves the browser, and sensitive URL parameters are redacted by default.
  • Unique users, funnels and retention leave cookieless IDs out by default, since a returning visitor gets a new one each day. Event totals and session metrics count them.

Changed

  • In 0.1.0, consent defaults to cookieless rather than granted, beforeSend replaces sanitizeUrl, and IDs stored by 0.0.x are discarded. See Upgrading.

Dashboard

Web analytics on the Overview

New

  • The Overview switches between Web analytics and Product analytics, and remembers your choice.
  • Visitors, pageviews, sessions, bounce rate, visit duration and pages per session, each compared with the previous period.
  • Sources by referrer and UTM source, medium and campaign, Pages with entry and exit pages, Locations by country, region and city on a map, and Devices by browser, OS and device.
  • Click a row to filter the whole view by it, or open the panel in Insights.

MCP

Ask AI agents about your analytics

Pug serves its analytics API as a Model Context Protocol server at /mcp, so an agent can answer a question about your data without you writing the query.

New

  • Twelve read-only tools run insights, browse events and activity, look up profiles by Pug ID or by your own ID, and check an erasure request.
  • A client connects with a project’s private key, sent as x-api-key or as a bearer token.

SDKs

SDKs for the web, Node.js and Flutter

New

  • @pug-sh/browser captures page views, clicks, scrolls, form interactions, rage clicks and dead clicks once initialized.
  • @pug-sh/node sends events and identifies from your backend, and reads your analytics back.
  • pug_flutter tracks events, identity and sessions in Flutter apps.

Pug's first release

Pug is open-source product analytics. Your website, app or server sends events, and you explore them in the dashboard or through the API.

New

  • Insights: trends, funnels, retention, top-K rankings of events, property values or users, and user flow, a Sankey diagram of how sessions move between events.
  • Dashboards of insight tiles. Make one public and anyone with its link can view it.
  • Profiles for every visitor and signed-in user, with their events and sessions.
  • Events browses the raw event stream, and Live maps the visitors of the last few minutes and what they did.
  • Each project reports in its own timezone.
  • The Profiles API erases a person’s data on request, and Pug doesn’t store visitors’ IP addresses.
  • Container images on GitHub’s registry to self-host Pug.

Type to search...

↑↓ navigate↵ selectEsc close