Changelog
What we shipped, and why
Major releases to Beacon — analytics, attribution, install and dashboard. Written for the people using it, not for a release note generator.
November 2026
- Analytics
Funnels: see exactly where a session gives up
Funnels is a new page in the dashboard. Build a path out of the pages and events your site already sends and Beacon shows how many sessions reached each step, what percentage of the first step that is, and how many dropped off on the way.
- Up to six steps, each a page path or an event name
- Steps must happen in order, with anything else allowed in between
- Dropdowns only offer pages and events that actually arrived in the period
- Up to ten saved funnels per site, on every plan including Starter
- Analytics
Events, entry and exit pages, bounce rate, and cleaner data
Custom events are now a first-class page: every name sent through beacon.track() appears automatically with its count, visitors and conversion, so a goal needs no configuration. Traffic gained top pages, entry and exit pages, a bounce rate and CSV export.
- New Events page with per-event count, visitors, conversion and change
- Top pages by any pageview, plus entry and exit page tables
- Bounce rate counted per session, not per pageview
- Crawlers, unfurlers and headless browsers are dropped at ingest
- Traffic export as CSV for pages, entry, exit, channels and campaigns on Growth
- Dashboard
A blog that search engines can actually read
Posts ship as pre-rendered HTML with their own title, canonical URL, Open Graph tags and Article structured data, so links are indexable the moment they go live. A sitemap and RSS feed are generated on every build.
- Four indexable blog pages in the first release
- sitemap.xml, robots.txt and an RSS feed generated at build time
- No separate CMS or database table to maintain
- Analytics
Today and yesterday, with an honest upper bound
The range picker is now a dropdown with Today, Yesterday and the three rolling windows. Single days are plotted per hour, so a Tuesday afternoon still has a shape instead of one flat bar.
- Yesterday ends at 23:59:59 and cannot leak today's events
- Previous-period comparisons line up with the calendar day
- Plan retention still clamps longer ranges server-side
- Install
The tracker console no longer writes to your analytics
Testing the snippet used to send real events from the dashboard into the selected site, which is how /dashboard pages ended up in customer landing-page reports. The console is now a local simulator: it shows each call and its payload without touching ingest.
- No dashboard paths can appear in customer analytics
- Every simulated result is labelled as local
- Real verification still requires an event from your own domain
October 2026
- Attribution
First touch and last touch, stored on the lead
Beacon keeps the campaign that started the session and the campaign that preceded the conversion, then writes both onto the lead record. You can rebuild either report months later without re-instrumenting anything.
How the two models differ - Install
Framer, Webflow and WordPress install paths
The Install page now gives platform-specific instructions for HTML, Next.js, Framer, Webflow and WordPress, including where the snippet belongs and how to publish. Framer uses Site Settings → General → Custom Code, at the end of head, on all pages.
- Verification needs one real pageview from the published domain
- Campaign URLs show attribution immediately in Traffic
- Country and device appear as soon as the edge reports them
Try the current release
One script tag, no cookies, and each lead keeps the campaign and landing page it arrived with. Free up to 10,000 visits a month.