<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>What&apos;s new in Vero</title>
    <link>https://getvero.dev/changelog/</link>
    <description>Product updates and release notes for Vero analytics.</description>
    <language>en</language>
    <atom:link href="https://getvero.dev/changelog.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>One AI connection can now read all your sites</title>
      <description>When your AI client signs in, or when you create a read-only key in «Connect your AI», tick the box to let it read every other site you see too, in every workspace. Ask it to compare two sites and it reads both; the site you set it up on stays the default. Every read still checks that you see the site and that its workspace is on Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-17-one-ai-connection-can-now-read-all-your-sites</guid>
      <pubDate>Tue, 17 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The free teardown now weighs the trackers your homepage loads</title>
      <description>Besides your stack, pages and traffic range, the teardown at getvero.dev/teardown now opens your homepage in a real browser without accepting anything and measures, gzipped, the analytics, ad, session recording, tag manager and cookie banner scripts it loads, grouped by kind. Scripts that load only after consent are not counted. Next to the total you see what Vero weighs with every module.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-15-the-free-teardown-now-weighs-the-trackers-your-homepage-loads</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Leaked passwords are refused at sign-up and when you change yours</title>
      <description>When you sign up, reset your password or change it, Vero now refuses a password that has appeared in a known data breach and asks you to pick another. Only the first 5 characters of its hash leave Vero to check, never the password itself. It applies on every plan. The security page at getvero.dev/security now also explains how your account and your AI’s MCP access are protected.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-15-leaked-passwords-are-refused-at-sign-up-and-when-you-change-yours</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Sending an invitation in Team no longer shows an error</title>
      <description>Since yesterday, sending an invitation from Team showed «An unexpected error occurred» right after you sent it. The invitation was created and its email went out, but the screen failed instead of confirming it and adding it to the list. Nothing is lost: each invitation you sent while it failed was created and emailed. Now the screen says «Invitation sent to …» and lists the invitation, as it did before.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-15-sending-an-invitation-in-team-no-longer-shows-an-error</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Connect your AI agent by signing in, no key</title>
      <description>Give your AI client the Vero MCP URL, sign in to Vero and pick the site to share. There is no key to copy. It works with Claude on claude.ai, Claude Code and ChatGPT, depending on your ChatGPT plan. Access is read-only and covers only sites you can see, and any connection you revoke from «Connect your AI» stops answering at once. Keys still work for clients that prefer them.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-15-connect-your-ai-agent-by-signing-in-no-key</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your beta, explained on the Account page</title>
      <description>The Account page now opens with a «Your beta» card: what the beta includes, the founding discount and how you keep it, what happens when the beta ends and what I ask in return. There is no end date yet, and you will get notice by email and in the dashboard. A small Beta badge beside the logo takes you there, and on larger screens the «Report something» button now shows its label instead of only an icon.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-15-your-beta-explained-on-the-account-page</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Connect your AI to your site data</title>
      <description>The new «Connect your AI» screen, under Configure, lets your coding agent read your site data: Claude Code, Cursor, VS Code, Windsurf, Codex, Claude Desktop or any MCP client. Create a read-only key for the site, copy the command or config for your client with the key already in it, and ask your agent a question. The screen confirms by itself once the agent has read your data. The key can read and cannot send or change anything.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-15-connect-your-ai-to-your-site-data</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A quicker way in from your beta invitation</title>
      <description>The new beta invitation link takes you straight in: you choose a password and you are inside, with no second confirmation email. Invitations sent before today still ask you to confirm your address. The first setup step already has the site you applied with, and sign-up asks for your name, so your team and your emails show it instead of the start of your address.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-a-quicker-way-in-from-your-beta-invitation</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A welcome on your first visit to the dashboard</title>
      <description>The first time you reach your dashboard after setting up your site, Vero welcomes you and points to three places: Overview, Revenue and the «Get set up» checklist. The setup steps now ease in one after another instead of swapping abruptly, and coming back to a half-finished setup shows a placeholder instead of a blank screen. The sign-up screen now shows sample pieces of the dashboard with demo data: revenue, live visits, revenue by source and an AI insight.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-a-welcome-on-your-first-visit-to-the-dashboard</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Cleaner account screens</title>
      <description>Sign-in, two-factor, forgot and reset password, verify email and team invitations show only the form, centered, in one consistent look. The demo panel stays on sign-up. If you arrive from your beta invitation email, sign-up greets you as invited and already has your address. &quot;Check your email&quot; now says where the link went, with the troubleshooting folded under &quot;Didn&apos;t get the email?&quot;.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-cleaner-account-screens</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The top bar no longer overlaps the period selector on a laptop screen</title>
      <description>On a laptop-width screen, the live visitor count in the top bar of the dashboard and the public demo (and the «Demo» label in the demo) slid under the period selector. Now the live count shortens with an ellipsis when space runs out, and nothing covers the period selector.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-the-top-bar-no-longer-overlaps-the-period-selector-on-a-laptop-screen</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Unsubscribing from the weekly digest no longer asks you to sign in</title>
      <description>The «Unsubscribe» link in the weekly digest used to open Notifications in the dashboard, so you had to sign in first. Now it opens a page with one button that turns the digest off, no sign-in needed. If your mail app shows its own unsubscribe button next to the sender, that button turns it off directly too. Only the weekly digest stops: alerts and account emails keep arriving. You can turn it back on in Notifications at any time.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-unsubscribing-from-the-weekly-digest-no-longer-asks-you-to-sign-in</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The shortest period is now called «24H», not «Today»</title>
      <description>The shortest period in the period selector was called «Today», but it has always covered the last 24 hours, so at 9:00 it already included yesterday afternoon. Its button now reads «24H», next to «7D», «30D» and «90D». Where the period is written out, in the CSV export and on the Pages screen, it says «Last 24 h». The numbers stay the same, only the name changes. The public demo uses the new name too.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-the-shortest-period-is-now-called-24h-not-today</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Expired invitations now say so in Team</title>
      <description>In Team, an invitation that had passed its expiry stayed in the list as «Invited» and still counted in the pending number under the card title. Now the row says «Invitation expired», and it no longer counts as pending. Cancel still removes it, and you can invite the same address again from the form.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-expired-invitations-now-say-so-in-team</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Overview lists now match the totals when a period starts partway through an hour</title>
      <description>On the Overview, some periods start partway through an hour: a custom date range, or any period read in a time zone that does not start on a UTC hour. In those periods the totals at the top counted the visits from that first partial hour, but the lists below left them out. That covers top pages, referrers, UTM sources, countries, languages and devices, so the lists could add up to less than the totals. Now the lists count that hour too, and they match the totals.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-the-overview-lists-now-match-the-totals-when-a-period-starts-partway-through-an-hour</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Cancelling a pending invitation now asks first</title>
      <description>In Team, Cancel on a pending invitation used to cancel it in one click. Now it asks first and names the address. It also says what happens next: the emailed link stops working at once, the person is not told, and you can invite the same address again at any time.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-14-cancelling-a-pending-invitation-now-asks-first</guid>
      <pubDate>Sat, 14 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Each later month over the Pro cap now gets its own email and 7 days</title>
      <description>On Pro, going over your tier’s cap is never charged. When a second month in a row goes over, we email you the tier that fits and give you 7 days before the dashboard’s stats lock. Before, each later month over the cap locked the stats again right away, with no new email. Now each one gets the same email and its own 7 days first, so a lock never comes without a warning.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-12-each-later-month-over-the-pro-cap-now-gets-its-own-email-and-7-days</guid>
      <pubDate>Thu, 12 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>An invitation stops working when the person who sent it no longer runs the workspace</title>
      <description>In Team, owners and admins send invitations. An invitation kept working after its sender was removed from the workspace or changed to member, so it could still bring someone in. Now it stops working as soon as that happens: the invited person sees that the invitation is no longer valid, and a current owner or admin can invite them again from Team.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-11-an-invitation-stops-working-when-the-person-who-sent-it-no-longer-runs-the-workspace</guid>
      <pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A member limited to some sites no longer sees them all when those sites are deleted</title>
      <description>In Team, an admin can limit a member to some sites. If every one of those sites was deleted, that member could suddenly see all the sites in the organization. Now they see none until an admin gives them access again in Team, under the member’s site access.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-11-a-member-limited-to-some-sites-no-longer-sees-them-all-when-those-sites-are-deleted</guid>
      <pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Two-step sign-in now protects every way into your account</title>
      <description>Signing in with Google or GitHub skipped the code, so two-step sign-in did not cover that route. Now, with two-step sign-in on, you sign in with your email and password and then the code, and Google or GitHub can no longer skip it.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-11-two-step-sign-in-now-protects-every-way-into-your-account</guid>
      <pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The anonymous visitor code is now different on each website</title>
      <description>Vero counts visitors with an anonymous code that changes every day. That code is now also different on each website, so a visitor cannot be linked across two sites that use Vero, not even on the same day. Your counts work as before.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-11-the-anonymous-visitor-code-is-now-different-on-each-website</guid>
      <pubDate>Wed, 11 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Periods with little traffic now count each visitor exactly</title>
      <description>Pageviews, sessions and revenue were never affected, but on sites and periods with little traffic two different visitors could occasionally count as one, so the Visitors figure and the Overview chart could be off by a few on unfiltered periods of a day or longer, and so could All sites. Now periods with little traffic count each visitor exactly, and very busy ones still use an estimate with a small margin, as before.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-09-periods-with-little-traffic-now-count-each-visitor-exactly</guid>
      <pubDate>Mon, 09 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>AI insights now count each visit once for a referrer</title>
      <description>Totals, the Sources card and sales attribution were not affected, but AI insights and the weekly digest counted every event a visit sent, such as scrolls, time on page, leaving or each page of the visit, so a sentence could credit a referrer with more than your whole site’s total. Now each visit counts once, the same way the Sources card counts it, and the Spanish text no longer leaves metric names in English.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-09-ai-insights-now-count-each-visit-once-for-a-referrer</guid>
      <pubDate>Mon, 09 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Install Vero from Cursor or Claude Code with one prompt</title>
      <description>The framework guides in the install step and in Settings → Install now have a Copy prompt button, on every plan. Paste it into Cursor, Claude Code or another AI editor: it edits your own code to add the script and pass the visit id to your checkout, which is what ties a sale to the visit that brought it. You still connect the webhook under Connect your sales, past payments are not imported, and a visit from localhost does not count.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-install-vero-from-cursor-or-claude-code-with-one-prompt</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A renewal no longer alerts as a new sale on Hobby</title>
      <description>On Hobby, once a customer’s earlier sales had passed the 30-day retention, a monthly renewal could reach you as a new sale. Now a charge the provider marks as a renewal sends no alert when no stored visit ties it to a checkout.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-a-renewal-no-longer-alerts-as-a-new-sale-on-hobby</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See which source found the customer and which closed the sale</title>
      <description>Revenue now puts the source that found a customer beside the one that closed the sale, once the period has 5 sales with a visit on record. It also shows the average visits and pages on the day of the first payment, and the share paid on that day’s first visit. With no cookies it links the visits of one day and repeat purchases by the same customer id, so someone who comes back on another day before buying cannot be linked.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-see-which-source-found-the-customer-and-which-closed-the-sale</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The heatmap now tells you when to publish</title>
      <description>The heatmap on the Overview now puts its conclusion in words: which hour to publish just before and, when the sales allow it, which part of your day most of them come in. With too little data it says nothing.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-the-heatmap-now-tells-you-when-to-publish</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See what your Direct traffic is made of</title>
      <description>Sources now splits the visits with no referrer and no tag, on every plan. Those opened inside an app such as Instagram or TikTok carry its name, and that part is certain. The rest is a reading of the entry page: home page, likely typed or bookmarked; inner page, likely a direct link; thank-you page, likely back from checkout. Visits from before this shipped show as Before this was measured. From the user agent Vero keeps only the app’s name, never the user agent.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-see-what-your-direct-traffic-is-made-of</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your sites now tells you which one to open first</title>
      <description>If you have more than one site, each card on Your sites shows visitors and revenue with their change against the period before, and a site with no events in 24 h or a drop today is marked and comes first. You can sort by revenue, visitors or biggest change, and switch the period. On top you get the total across your sites: one figure per currency, never added together, with each site counted in its main currency.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-your-sites-now-tells-you-which-one-to-open-first</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Hear about it when a new customer pays</title>
      <description>Switch on New sales in Notifications and a customer’s first payment reaches you by email, webhook or both, with the site and the amount. On Pro and in the beta it also says which source and campaign brought the sale. A refund sends nothing, and neither does a renewal or repeat purchase from a customer id Vero already has a sale for. Email stops at 10 per site a day, and the webhook keeps going.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-hear-about-it-when-a-new-customer-pays</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Fewer anomaly emails, with all your sites in one</title>
      <description>Drops on all your sites now arrive in a single email a day per workspace, and spikes in another if you turned them on in Notifications. A slow day on a low-traffic site no longer emails you. A drop that holds steady is not emailed again every morning. A small site that takes off can now send you a spike.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-11-08-fewer-anomaly-emails-with-all-your-sites-in-one</guid>
      <pubDate>Sun, 08 Nov 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A new sale or refund shows up on the next load</title>
      <description>After a sale or a refund came in, Revenue and the Overview could keep showing the previous figure for a while. Now the new amount is there the next time you load the screen.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-23-a-new-sale-or-refund-shows-up-on-the-next-load</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your first visit opens the screens right away</title>
      <description>After you installed the tracker, the screens could keep saying No events yet for a little while after your first visit arrived. Now they open with that visit. Goals also say 1 visit instead of 1 visits.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-23-your-first-visit-opens-the-screens-right-away</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your dashboard now shows what the demo showed</title>
      <description>What the redesigned dashboard only filled in on the public demo now comes from your own data: each site card shows its change against the week before with a sparkline of the week, Sessions compares each card with the period before and names the campaign behind each visit, and every Web Vitals metric splits its readings into good, needs improvement and poor. Revenue, your latest sales, Alerts and invitations fill in the rest, from the sales that arrived without a visit to the name of whoever invited you.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-22-your-dashboard-now-shows-what-the-demo-showed</guid>
      <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One source per platform in Sources and Revenue</title>
      <description>Visits from Facebook (facebook.com, l.facebook.com, m.facebook.com, the Android app), X (x.com, twitter.com, t.co), Instagram, LinkedIn, YouTube, Reddit, TikTok and Pinterest now add up in one row per platform in Sources and Revenue, instead of spreading across several. The Referrers list still shows the exact host. This also applies to the data you already have.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-18-one-source-per-platform-in-sources-and-revenue</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The conversion card gets its sparkline</title>
      <description>On the Overview, the Goal conversion card now has a sparkline, like the other cards: your conversion rate to the main goal across the period, so you see whether it climbs or drops before you read the figure.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-18-the-conversion-card-gets-its-sparkline</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>UTM tags named direct, none or other keep their own row</title>
      <description>A UTM tag called direct, none or other no longer mixes with the Direct, No campaign and Others rows that Vero adds itself. Your tagged visits stay in their own row.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-18-utm-tags-named-direct-none-or-other-keep-their-own-row</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Two-step sign-in with an authenticator app</title>
      <description>In Account, you can turn on two-step sign-in: after your password, Vero asks for the 6-digit code from your authenticator app. When you turn it on, you get backup codes for the day you lose your phone, and each one works once. It is optional and on every plan. If you sign in with Google or GitHub, Vero does not ask for a code, because your provider handles that step.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-18-two-step-sign-in-with-an-authenticator-app</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One Hobby workspace per person</title>
      <description>Each person can now own one Hobby workspace. To create another, upgrade the one you have to Pro first. Workspaces on Pro or in the beta do not count, and any extra Hobby workspace you already own keeps working as before.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-18-one-hobby-workspace-per-person</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A calmer, denser dashboard on every screen</title>
      <description>Every screen was redesigned, from the Overview and Revenue to Funnels, A/B tests, Settings, Billing, sign-in and onboarding, with lighter cards and more on each view. Each change shows as a colored pill, no change included, bar charts on short ranges put the value over each day, and Today at a glance on the Overview names what is driving the day.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-18-a-calmer-denser-dashboard-on-every-screen</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Leave or create a workspace, sign out other devices, and edit goals and watches</title>
      <description>You can leave a workspace from Team, and create another one, which starts on Hobby. Account has a Sessions section with the devices where you are signed in, and Sign out everywhere else. When you choose a member&apos;s site access, All sites also covers the sites you add later. A goal can be renamed, or pointed at another event or page. On Pro, a watch can be paused, resumed or given a new threshold, revenue can be grouped by payment provider with a refunds column, and an A/B test warns you when another one already runs on its page, since only one runs per page.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-leave-or-create-a-workspace-sign-out-other-devices-and-edit-goals-and-watches</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Exact usage near the cap, Back undoes a filter, and money tables that say more</title>
      <description>Near the monthly cap, usage shows the exact figure, and the limit shows as reached only once it is. Members see who can change billing, and plan notices also appear on the sites list, Team and Account. On a phone, Search is under More, and a greyed-out period says why it is locked. Hobby&apos;s 30-day limit applies everywhere you pick dates: presets, calendar and command palette. Back undoes a filter or period change. CSV exports open correctly in Excel. A site from another workspace offers to switch to it. The conversion card shows its change. From new data on, /pricing/ and /pricing count as one page. Pages search finds a pasted address and says how many pages match, and a page with no visits points you to its other spelling. Each page shows its revenue as entry page next to the revenue from visits that saw it. On Hobby, money tables show visits under the upgrade prompt. The revenue chart cuts one huge day so the rest stays readable. Cohorts are net of refunds and go monthly on long ranges. Time to pay names a typical wait once there are 5 sales. Money tables have a change column and sort both ways. In Sessions, entry and exit pages are links, times are exact, the steps include email links, phone links and A/B variants, and a filter that matches no visits offers Clear filters. Web Vitals separates Core Web Vitals from diagnostics and links failing pages to Pages. Funnels lead with Entered, Converted and Overall conversion, and count only visits with a page view, as goals do. Settings keep unsaved edits when you switch tabs, and excluded paths say which line is wrong. The site check works for sites served over http only. Billing opens on your billing period, explains why a plan is unavailable, and warns before you move to a plan below this month&apos;s usage. API keys that stopped working are marked, with who created them. The email channel says who receives alerts. Invitations arrive in the recipient&apos;s language, and an expired reset or invitation link tells you what to do next. When your session ends, signing in brings you back to the same screen. Sales appear at the hour they were paid, and anomaly alerts quote the same figures as the Overview.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-exact-usage-near-the-cap-back-undoes-a-filter-and-money-tables-that-say-more</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Right numbers across clock changes, filters and refunds</title>
      <description>The heatmap no longer shifts by an hour across a clock change, and tabs left open no longer skew time per page. Unknown and Tor countries show a name. The top campaign is the same on the Overview and on Revenue. Partial refunds that arrive together are no longer counted twice, profit no longer shows wrong figures under a country, page or campaign filter, and a cost can no longer be negative. A site that only sends sales from its server now sees its revenue. Visits with no screen width show as Desktop. On Hobby, links to Pro-only screens no longer empty the list. A double tap no longer deletes two deploys, Save segment no longer saves twice, and adding a goal that already exists no longer renames it without telling you. Sharing an achievement uses your current public link. Escape in a dialog no longer takes you out of onboarding, and revoking a key no longer hides one you just created. Removing a webhook secret asks first. Ask Vero answers no longer show stray asterisks. The offline notice no longer covers the mobile bar, and the iPhone status bar is readable in Lumen. For the API: /api/revenue and /api/refund now refuse an amount that is not a whole number above 0.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-right-numbers-across-clock-changes-filters-and-refunds</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Big sites and long date ranges open much faster</title>
      <description>On a site with a lot of traffic, Sources, Pages, Sessions, goals and Web Vitals open much faster, and so do long date ranges. Vero now keeps each visit and each day ready instead of counting them again on every screen. Load more in Sessions no longer slows down the further you go. Your numbers stay the same, with one detail on Pages: a visit whose first action in the period was not a page view now counts as an entry on the page it opened on, the same as in Sources.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-big-sites-and-long-date-ranges-open-much-faster</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>End an A/B test and keep its final results</title>
      <description>End test stops showing the variant and freezes the results as they are that day, so you can read them later without them moving. A test created without a goal can now get one, and its conversions count from the day the test started. Site settings also shows how to send deploy annotations from CI, so each release lines up on your charts with the jump or drop it caused.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-end-an-a-b-test-and-keep-its-final-results</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Payment conversion counts first payments, and A/B results say when data is thin</title>
      <description>Payment conversion now counts only first payments from visits in the period, so it can no longer pass 100%. Renewals and repeat sales are shown under Sales. On the Overview, Conversion is now called Goal conversion. With a campaign or referrer filter on, revenue shows what those sales really brought. Profit by source keeps each cost in its own currency, shows &lt;−999% instead of a huge figure, and warns when a cost looks out of proportion. A/B certainty is two-sided, says when there are too few conversions to compare, and no longer projects a finish date far into the future. A variant nobody has seen yet, and a test with three variants, read more clearly. Admins can invite, remove and rename on Team, and each role says what it can do. The Web Vitals matrix shows the pages with the most samples, plus every page that misses a target. A paused site on Hobby says why, and Pages remembers what you chose for its table to show. Exclude visits from this network now covers your whole IPv6 network, and any member can use it. Your public page&apos;s top sources match Sources, members see who manages billing, tall dialogs scroll on phones, and the Node and Bun/Deno edge snippets forward every UTM tag.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-payment-conversion-counts-first-payments-and-a-b-results-say-when-data-is-thin</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Revenue that adds up, and destructive actions that ask first</title>
      <description>Try again on an error screen reloads the page, and the site switcher and site list update as soon as you add, rename or delete a site. If a signing secret is wrong, the connection shows Failing, and Revenue and the Overview say sales are not arriving. Lemon Squeezy and Paddle no longer subtract refunds of orders Vero never saw, and a Stripe refund that arrives before its sale is applied once the sale lands. Beacons sent late are counted, so bounce rate is no longer slightly high. A repeated funnel step no longer shows 100%, opening a visit always shows the one you clicked, and the Goals property explorer reads keys with accents and says when the list is cut. An export that hits the row limit says so. Deleting a site or your account lists what is lost and asks you to type the domain or your email, and deleting an account asks you to sign in again. Removing the revenue webhook and declining an invitation ask first. Variant HTML that is too long is refused instead of cut, and setting a goal no longer resumes a paused test. Signing up again with an email that already has an account sends an email that says so. On Billing, a plan change that needs 3-D Secure gives you a link to confirm with your bank, a cancelled plan is resumed before you switch, a trial or beta checkout says your card is saved and when the first charge is, and a past-due subscription gets Pay now. Adding a domain that is already in the workspace opens its install snippet.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-revenue-that-adds-up-and-destructive-actions-that-ask-first</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Faster screens on big sites, and time to pay counts every sale</title>
      <description>On a site with a lot of traffic, screens open sooner. The Overview loads each card as you scroll to it, and Pages, goals, funnels and A/B tests read less data to fill them. Your sites loads every card in one go, so a workspace with many sites no longer shows empty cards. Opening a visit in Sessions is quick. How long customers take to pay now counts every sale, not a sample.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-faster-screens-on-big-sites-and-time-to-pay-counts-every-sale</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Long lists show everything, and every picker has a search</title>
      <description>A long list no longer stops without telling you: the rest goes into an Others row, the card says how many rows it shows of the total, and View all opens every row with a search field. Picking a page, a country, a funnel step, a goal or a test is now a search, and you can paste a full URL: /pricing and /pricing/ count as the same page. On a phone, long names and paths stay readable and a tap shows the full text. Paths with accents or spaces read the way you wrote them, and international domains keep their own letters.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-long-lists-show-everything-and-every-picker-has-a-search</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A failed load says so, and money adds up in the edge cases</title>
      <description>When a card can&apos;t load, it says so and lets you try again, instead of looking like there is no data. A link to a site you lost access to explains why, and a signed-out session takes you to sign-in. Comparisons stay right across clock changes, and long ranges are drawn as weekly bars with the year on the axis. Each screen shows one currency, with a note for sales made in others. Refunds are drawn below zero, tiny amounts read like &lt;€0.01 instead of rounding to nothing, and long durations are shown in hours. On Billing you can load older invoices, and the sessions list keeps scrolling however many visits you have.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-17-a-failed-load-says-so-and-money-adds-up-in-the-edge-cases</guid>
      <pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The price you pay and changes measured on equal spans</title>
      <description>Founding subscribers now see the price they actually pay, founding discount applied, on the plan card, the renewal line and the plan-change preview. On the Overview, a partial today is compared with the same stretch of time before it, the date picker no longer offers future days, and a card says so when the previous period is older than your plan keeps instead of showing a made-up change. On Hobby, a filtered revenue card says revenue is a Pro feature instead of staying blank. Web Vitals says how many pages fail, an A/B variant that is behind is called behind, the privacy snippet in Settings is accurate, an unverified email gets a new link at login and can resend it, and someone removed from a workspace sees a clear screen instead of an error.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-the-price-you-pay-and-changes-measured-on-equal-spans</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Fairer numbers on how long customers take to pay and where sales came from</title>
      <description>How long they take to pay now counts only each customer&apos;s first paid sale, so renewals no longer stretch the typical wait. On Hobby, Connect your sales no longer says every sale came with its visit, and recent sales are no longer all shown as Direct. A test sale now completes setup, still left out of revenue, and the traffic and revenue table keeps a paying source&apos;s visits and says how many rows it shows of the total.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-fairer-numbers-on-how-long-customers-take-to-pay-and-where-sales-came-from</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See which campaign made the most money</title>
      <description>A Top campaign card on the Overview and on Revenue names the tagged campaign that billed most in the period, with its sales, its visits and the two sources that billed most for it. On Revenue, one click filters the whole screen to that campaign; on the Overview, the card takes you to Revenue.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-see-which-campaign-made-the-most-money</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Pro now starts at €9 a month</title>
      <description>Pro 50K costs €9 a month + VAT, or €7.20 a month billed yearly at €86.40, for 50K pageviews and custom events a month. It has every Pro feature, revenue attribution included, so a small site sees which sources bring its sales without paying for volume it does not have. Prices are public during the beta, and nothing can be bought yet.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-pro-now-starts-at-9-a-month</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Traffic and revenue in one table</title>
      <description>Sources and Revenue now share one table that puts what brought visits next to what brought sales. Group it by source, channel, campaign, referrer or entry page, and each row shows its visits, revenue, revenue per visit, change, sales, average order and conversion. Sort by any column, and click a row to filter the whole dashboard to it. The Overview shows its top rows. On Hobby, each row shows its visits.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-traffic-and-revenue-in-one-table</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See which sources pay, and open each one on its own</title>
      <description>Sources has a new chart, Who pays?: each source sits by the visits it sends and what one of those visits is worth, and the bigger the circle, the more it bills. Click a source to open its sheet, with its visitors and revenue by day, the pages its visits land on and a link to the whole dashboard filtered to that source.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-see-which-sources-pay-and-open-each-one-on-its-own</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Overview charts revenue and shows what moved</title>
      <description>The Overview chart can show revenue, with the previous period as a dashed line. What moved a figure now reads as before and after, with a bar for each factor&apos;s share of the change. The heatmap names its busiest hour and can show revenue by hour instead of visits. The live sheet has a Sales tab with the last 24 hours of sales and, on Pro, the source of the visit behind each one.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-the-overview-charts-revenue-and-shows-what-moved</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Revenue shows what a visitor is worth</title>
      <description>The Revenue screen adds revenue per visitor and the share of visitors who buy, each with its change. Refunds are already subtracted from revenue, and the card shows the total before them. The revenue chart switches between revenue and number of sales, with the previous period as a dashed line.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-revenue-shows-what-a-visitor-is-worth</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See how long people take to pay</title>
      <description>A new card on Revenue times each sale from the first page of the visit that paid, or of the trial its checkout points to. It groups sales by how long they took and gives the typical wait for each source, and it follows your filters. Vero sets no cookies, so someone who comes back another day starts from zero: the card measures within the visit or the trial.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-see-how-long-people-take-to-pay</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The UTM builder checks your tags, and connecting sales takes three steps</title>
      <description>The UTM builder fills in source and medium from where you will share the link, and says which channel its visits count as. It saves tags in lowercase and warns you when a source is a new spelling of one you already use, so its revenue does not split in two. Your campaigns lists the visits and, on Pro, the revenue each tagged link brought. Connect your sales now takes you through three numbered steps per provider, links to its webhooks page, and shows the attribution meter and the last sales with their source.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-the-utm-builder-checks-your-tags-and-connecting-sales-takes-three-steps</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Read your pages by lens and each visit as a story</title>
      <description>Pages switches between Traffic, Engagement and Money, with a bar in each cell so rows compare at a glance; Money shows revenue by entry page on Pro. A page&apos;s detail shows the pages just before and just after it inside the same visit, and its chart reads views or visitors against the previous period. On Sessions, each visit reads as sentences, from where it arrived to the sale it ended in. What visits look like spreads them by pages seen and time spent, each visit shows its entry and exit page, and you can list all visits, the ones that paid or the one-page ones.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-read-your-pages-by-lens-and-each-visit-as-a-story</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Web Vitals, goals and funnels lead with the answer</title>
      <description>Web Vitals opens with one sentence on whether you pass, lays every page against every metric, and charts each core metric day by day against its good line, with your deploys marked. Goals puts your primary goal on top with its change, adds a table view and shows where the goal converts best, by source and by entry page. Funnels name the biggest leak first, switch between steps, bars and a table, and show the typical wait between one step and the next.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-web-vitals-goals-and-funnels-lead-with-the-answer</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A/B tests say how sure they are, and watches say when they fired</title>
      <description>Each A/B test shows how sure it is that the variant wins and, at your current traffic, about how many more days it needs to call it. Alerts draws the last 30 days with every alert and deploy marked, and each watch says whether it has fired and when it last did. AI insights open with the period in four figures, and each finding links to the screen with its numbers.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-16-a-b-tests-say-how-sure-they-are-and-watches-say-when-they-fired</guid>
      <pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The dashboard shows each figure once</title>
      <description>The Overview is shorter. UTM sources now live only on Sources, and devices, browsers and operating systems sit together under Audience. The weekday-by-hour heatmap moved into a Patterns group that stays closed until you open it, and it remembers your choice. Revenue no longer repeats custom events, which stay on the Overview and Goals, and Sources no longer repeats languages, which stay on the Overview.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-the-dashboard-shows-each-figure-once</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Make a page your goal, and see its conversion on the Overview</title>
      <description>A goal can now be a page a visit reaches, like /thanks, as well as a custom event. Create it from the Goals screen, with no code to add. Mark one goal as primary and the Overview shows a Conversion card for it: the visits that reached the goal out of all visits in the period.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-make-a-page-your-goal-and-see-its-conversion-on-the-overview</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Overview opens on your money</title>
      <description>The Overview&apos;s top row is now Visitors, Revenue, Revenue per visitor and Bounce rate, so what your traffic earns sits next to how much of it came. Until you connect your sales, revenue is a single card that takes you there. Pageviews stay in the chart&apos;s toggle, and active time and pages per visit now live on the Pages screen.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-the-overview-opens-on-your-money</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See how much of your revenue arrived with its visit</title>
      <description>The Revenue screen has a new card, Revenue with its visit: the share of the period&apos;s revenue that arrived with the visit that brought it, with a bar to read it at a glance. When a sale arrives without its visit, the card says why and how to fix it: a checkout on your own domain, an embedded Stripe buy button or a Checkout Session your server creates without the visit id, or a sale from before the tracker or past your plan&apos;s retention. It links to the docs on revenue attribution.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-see-how-much-of-your-revenue-arrived-with-its-visit</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A free trial from a Stripe Payment Link keeps its visit</title>
      <description>A free trial started from a Stripe Payment Link charges nothing at checkout, so Vero stored no sale and the first paid invoice arrived with no source. Vero now remembers the customer and the visit from that free checkout, and the customer&apos;s first paid invoice takes that visit. Renewals already took the source of the customer&apos;s first attributed payment. This works with Stripe for now.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-a-free-trial-from-a-stripe-payment-link-keeps-its-visit</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Compare your pages in one sortable table</title>
      <description>Pages is now one table with pageviews, visitors, entries, exit rate, time on page and scroll depth for every page. Click a column to sort by it, click a row to open the page. Time and scroll show when the tracker modules that measure them are on. A page&apos;s detail adds its scroll depth and trend lines, and links to Sources, Overview, Web Vitals and Goals already filtered to that page. Browsers and operating systems moved to the Overview, next to devices.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-compare-your-pages-in-one-sortable-table</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Every metric says what it counts</title>
      <description>Every metric card on the Overview, the Pages screen and a page&apos;s detail has an info mark beside its name. Hover or tap it to read what the number counts: bounce rate, for example, is the share of visits that saw one page and left. You no longer have to guess what a number means.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-every-metric-says-what-it-counts</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>An empty day no longer draws a bar</title>
      <description>On the visitors and pageviews chart, when the period started partway through a day with no visits, that first day drew a thin line at zero as if it had data. Now a day with no visits draws nothing.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-15-an-empty-day-no-longer-draws-a-bar</guid>
      <pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Choose which site keeps recording on Hobby</title>
      <description>Hobby includes 1 site. When an account with several sites moves to Hobby, at the end of the beta or when it leaves Pro, you choose on the Billing page which site keeps recording. The others are paused: they record no new visits, keep their data 30 days and record again if you choose Pro. If you choose none, the site with the most events in the last 30 days stays.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-choose-which-site-keeps-recording-on-hobby</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Switching sites keeps you on the same screen</title>
      <description>Choosing another site in the menu at the top of the sidebar used to open its Overview. Now it opens the same screen of that site: from Revenue you land on its Revenue, from Settings on the same tab. The period you were reading, custom range included, Compare and Paid only come with you. Filters by page, source, UTM, country or device and funnel steps stay behind, because they describe the first site&apos;s traffic, so the other site opens unfiltered. From Team or Account, choosing a site still opens its Overview.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-switching-sites-keeps-you-on-the-same-screen</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Clearer team invitations, a fully Spanish dashboard, and longer funnels</title>
      <description>A team invitation now names who sent it and the workspace you are joining, instead of repeating the first part of an email address. In Spanish, the workspace heading on the Team page and the API keys tab in Account are translated. In Funnels, Add step keeps the editor open, so you can add a third step and more while the result updates.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-clearer-team-invitations-a-fully-spanish-dashboard-and-longer-funnels</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Page details no longer ask for a module you already run</title>
      <description>Time on page, on a page&apos;s detail, and the Web Vitals screen told you to turn on a tracker module even when your site already loads it. Now, when the module is on and there is simply no data yet, they say so, and the message to add the module, with its link to the Install tab in Settings, shows only when the module is really off.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-page-details-no-longer-ask-for-a-module-you-already-run</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The revenue CSV now says which visit brought each sale</title>
      <description>Export revenue (CSV) now adds six columns after the existing ones: the source, channel, campaign, referrer, landing page and time of the visit that brought each sale. The existing columns keep their order, so a spreadsheet or script that reads the file keeps working. The columns are filled on Pro and stay empty on Hobby, where the source of a sale is not included.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-the-revenue-csv-now-says-which-visit-brought-each-sale</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Click a source to see what it brings you</title>
      <description>Click a row in the Overview Sources card or in Visits by source and every screen narrows to the visits from that source, revenue included: the sales whose visit came from there. Click the row again to remove the filter.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-click-a-source-to-see-what-it-brings-you</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A shorter sidebar that fits your laptop screen</title>
      <description>Team and Account now open from the menu under your name at the bottom of the sidebar, and the tracker builder is the Install tab in Settings, where old Tracker links now lead. The sidebar fades at the edge when there is more to scroll, and the setup checklist takes one line until you open it.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-a-shorter-sidebar-that-fits-your-laptop-screen</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Emails now arrive in the language your dashboard shows</title>
      <description>If you never picked a language on the Account page, the weekly digest, anomaly and watch alerts, and billing and account emails reached you in English even when your dashboard was in Spanish. Now the dashboard saves its language to your account the first time you open it, until then emails use the language you joined the waitlist in, and a language you picked yourself is never overwritten.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-emails-now-arrive-in-the-language-your-dashboard-shows</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Overview Sources card matches the Sources screen</title>
      <description>The Sources card on the Overview listed only referring sites, so a visit tagged utm_source=newsletter with no referrer was missing there while Visits by source showed it. The card now counts each visit once by its UTM source, or else the site that referred it, or else Direct (no referrer), just like the Sources screen.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-the-overview-sources-card-matches-the-sources-screen</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The usage meter says it counts every site</title>
      <description>The pageviews and events meter in the sidebar counts your whole workspace, every site together, against your plan&apos;s monthly cap. It now says so, and when you have several sites it also shows the current site&apos;s own month.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-the-usage-meter-says-it-counts-every-site</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Install snippet comments now match your language</title>
      <description>On the dashboard install screen and the Spanish install pages, the comments inside the WordPress, Webflow and Shopify snippets now show in Spanish when you use Vero in Spanish. Before, they were always in English.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-14-install-snippet-comments-now-match-your-language</guid>
      <pubDate>Wed, 14 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Check my site tells you why the snippet is not sending</title>
      <description>Check my site, on the install screen, opens your home page and looks for the snippet, checks that its token belongs to this site, that your Content Security Policy lets Vero load and send, and that the page is served from your domain. Each check says what it found and what to fix. Testing on localhost or a preview? Start a test, open the page with the snippet and Vero confirms it works without counting the visit.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-check-my-site-tells-you-why-the-snippet-is-not-sending</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>See where a change in visitors or revenue came from</title>
      <description>The Today strip, and a click on the visitors or revenue change, show the sources, entry pages, countries or devices that moved the figure most, each with its numbers next to what it is compared with. It is arithmetic on your own data, no AI involved. New alerts and the anomaly email name them too. Visitors work on every plan; revenue by source is Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-see-where-a-change-in-visitors-or-revenue-came-from</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One definition of source, on every screen</title>
      <description>A visit&apos;s source is now its UTM source, or else the site that referred it, or else Direct, everywhere Vero shows one. So producthunt and producthunt.com no longer split into two rows, and your own site&apos;s pages never count as a source. Sources lists visits by source, with the raw UTM tags kept as detail. Untagged visits with no referrer read Direct (no referrer).</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-one-definition-of-source-on-every-screen</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A sale keeps its source whatever dates you pick</title>
      <description>Vero now stores the source, campaign and channel of the visit that paid the moment the sale arrives. A sale keeps that source whatever date range you read it in.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-a-sale-keeps-its-source-whatever-dates-you-pick</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The weekly digest says more in its subject and its body</title>
      <description>The subject now names your site with its visitors, how they changed and, when you sold, the week&apos;s revenue. Inside, the digest adds the source that lost the most money, the biggest change behind the week&apos;s figures and any new site that sent you visitors this week. On Hobby it tells you what attribution on Pro would show for your sales and that Hobby keeps 30 days of data.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-the-weekly-digest-says-more-in-its-subject-and-its-body</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Pageviews next to countries, devices and browsers count only pageviews</title>
      <description>On the lists ranked by visitors, such as countries, devices, browsers and languages, the pageviews figure counted every event Vero recorded, page exits, speed measurements and clicks included. It read far higher than your site&apos;s real pageviews. It now counts only pageviews.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-pageviews-next-to-countries-devices-and-browsers-count-only-pageviews</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your account export includes everything Vero keeps about you</title>
      <description>Export account data, on the Account screen, now downloads as JSON everything Vero holds about you: how you sign in (Google, GitHub or password), your sessions, your API keys by name and date, your activity log, the feedback you sent and the replies to it, the team invitations you sent and received, your onboarding progress, the record of your weekly emails and your waitlist entry. Passwords, tokens and keys are never included.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-your-account-export-includes-everything-vero-keeps-about-you</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A switched-off public profile is a missing page for search engines too</title>
      <description>When a public profile was turned off, its page looked like a missing page but still answered as a normal one, so search engines and link previews could treat it as live. It now answers as a page that does not exist, for people and machines alike.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-a-switched-off-public-profile-is-a-missing-page-for-search-engines-too</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Links to Sharing settings open that tab</title>
      <description>A link to a site&apos;s Sharing settings now opens the Sharing tab directly, so you no longer have to look for it.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-13-links-to-sharing-settings-open-that-tab</guid>
      <pubDate>Tue, 13 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Visitors per page count each person once on longer periods</title>
      <description>On periods long enough to be read from hourly summaries, the visitors figure next to each top page counted a person twice when they came back to the same page hours later. It now counts each person once, like the rest of the screen.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-12-visitors-per-page-count-each-person-once-on-longer-periods</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Tracker modules are read-only for members who cannot change them</title>
      <description>A team member without owner or admin rights could flip the module switches on the Tracker screen and watch the size change, although nothing could be saved. The switches are now read-only for them, matching the note that only an owner or admin can change the tracker.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-12-tracker-modules-are-read-only-for-members-who-cannot-change-them</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Invoices say so when they cannot load</title>
      <description>If your invoice list failed to load, the Invoices section on the billing screen kept showing a loading placeholder forever. It now tells you it could not load your invoices.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-12-invoices-say-so-when-they-cannot-load</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Screens no longer jump when their data arrives</title>
      <description>While a dashboard screen loads, it now shows its real title, description and the same card layout it ends up with, so on a phone the content stays where it is instead of shifting down. This applies to every dashboard screen and to the public demo.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-12-screens-no-longer-jump-when-their-data-arrives</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What&apos;s new, inside the dashboard</title>
      <description>The sidebar has a What&apos;s new entry. A dot appears when something changed for you, and opening it lists those changes with a link to the screen they live on. The dot goes out on every device once you have opened it.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-05-what-s-new-inside-the-dashboard</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Sign in with Google or GitHub</title>
      <description>The login and sign-up screens now offer Continue with Google and Continue with GitHub, above the email form. Vero asks only for your name, verified email and profile picture, and never keeps the tokens Google or GitHub hand over. If you already have an account with the same verified email, the new sign-in is linked to it instead of creating a second one. During the beta, only an address with an invitation can create an account this way.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-05-sign-in-with-google-or-github</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Keep your own visits and chosen pages out of your stats</title>
      <description>Site settings has a new Exclusions card. Turn on Exclude visits from this network and Vero stops recording visits from the network you are on, such as your home or office. It stores a keyed hash of that address, never the address itself, and a site can exclude up to 20 networks. You can also list paths to ignore, one per line, with * as a wildcard, for example /admin*. Excluded visits are dropped before they are stored, so they never count toward your plan. A mobile connection or an address that changes on its own escapes the network rule.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-05-keep-your-own-visits-and-chosen-pages-out-of-your-stats</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Tagged links keep their channel, in traffic and in revenue</title>
      <description>Vero now reads a visit&apos;s UTM tags first and its referrer second. A link tagged utm_medium=email or newsletter, social or cpc that arrived with no referrer used to count as Direct. It now lands in Email, Social or Paid search, on the Sources screen and in revenue by channel. Display and Affiliates join them, and each new channel appears once a visit lands in it. A new site shows bounce rate, active time and scroll within minutes, not after the next hourly update. From your own checkout, provider is now optional and a sale without one is stored as your own. A refund must carry its own id: one sent under its sale&apos;s id is refused with a 400 instead of acknowledged and dropped. Saving notifications with a webhook URL Vero cannot call now says why and keeps your edits on screen. A teammate who signs up from an invitation gets a screen for joining the team, and Stripe checkout shows a 14-day trial as 14 days, not 13.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-04-tagged-links-keep-their-channel-in-traffic-and-in-revenue</guid>
      <pubDate>Sun, 04 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The plan limit counts only pageviews and custom events</title>
      <description>Your monthly limit now counts only pageviews and custom events: every page load, every vero.track() call or goal, and the custom events you send through the events API. What the tracker modules send on their own (time on page and scroll depth, Web Vitals, outbound clicks, downloads and A/B exposures) is still stored and shown, but no longer counts. Turning a module on no longer uses up your plan, so the tracker builder now sizes your plan from pageviews alone. Tier names stay the same: Pro 250K is 250K pageviews and custom events a month. Hobby still stops recording at its limit, and Pro keeps recording past it.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-04-the-plan-limit-counts-only-pageviews-and-custom-events</guid>
      <pubDate>Sun, 04 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Revenue in the weekly email, and emails for every plan change</title>
      <description>The weekly email now opens each site with its revenue without tax, the change against the week before and the source that brought the most money. A site with no payments connected gets a link to connect them instead of zeros. Vero now emails the owner when a plan starts, changes, is set to end or ends, when a trial runs out, the day before stats would lock and when they do, and before data older than Hobby&apos;s 30 days is deleted. CSV export reaches all the data still stored, so you can take it before that date. Password changes, account deletion and team changes send a notice too. A trial that ends with no sale yet gets 7 more days of Pro, once.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-04-revenue-in-the-weekly-email-and-emails-for-every-plan-change</guid>
      <pubDate>Sun, 04 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Filter by campaign</title>
      <description>Click a campaign in UTM campaigns on the Sources screen, or in Revenue by campaign on the Revenue or Sources screens, and a Campaign = &lt;name&gt; chip filters the screen. Visitors, pages, sources, revenue and its breakdowns, the sessions list and CSV exports all narrow to the visits that arrived on that campaign, read from the first page of the visit, the same rule as the source chip. The chip lives in the URL, so a shared link keeps it, and a saved segment can store it. No campaign and Other campaigns are not a single campaign, so they cannot be filtered. Revenue under a filter is part of revenue attribution, on Pro and in the beta. Hobby sees revenue unfiltered.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-03-filter-by-campaign</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Revenue by campaign, on Pro and in the beta</title>
      <description>The Revenue screen now ranks your UTM campaigns by the money they brought, next to revenue by channel. Each sale goes to the campaign of the visit that started it, the same rule as revenue by source, and refunds are subtracted. Sales from a visit with no campaign are listed as No campaign. The Sources screen shows the same list, and the read API and the MCP server return it too.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-03-revenue-by-campaign-on-pro-and-in-the-beta</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Docs and guides you can find your way around</title>
      <description>The docs have a grouped index, install steps and a copy button on every code sample. Each integration page shows how a sale travels from your checkout to Vero. Guides, the glossary, use cases and this changelog now have an index you can jump around in.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-03-docs-and-guides-you-can-find-your-way-around</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>AI insights and Ask Vero, on Pro and in the beta</title>
      <description>The AI features are on. The insights panel reads your week and says what drove revenue. Ask Vero answers a question about your data from your own figures. You can write a watch as a sentence, anomaly emails name a likely cause, and the weekly digest adds a short commentary. A meter shows how much of the month&apos;s AI allowance you have used. The models run on Google&apos;s Gemini API, which receives aggregated figures, never a single visit or an IP. Owners and admins can turn AI off for the whole workspace on the Team page, and then no model is called. Hobby has no AI.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-02-ai-insights-and-ask-vero-on-pro-and-in-the-beta</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Know that your install and your sales work</title>
      <description>In the beta, the dashboard tells you whether your tracker is reporting and whether sales are arriving from your provider. Anomaly alerts skip changes too small to mean anything: an alert needs a change of 20% or more, and of at least 10 visitors or pageviews. On a phone, each screen has one header with its title, the period and a menu for the rest. If an A/B test is slow to load its settings, your page shows its original version instead of waiting.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-02-know-that-your-install-and-your-sales-work</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Every feature, every price and who runs Vero</title>
      <description>The features page walks through the product screen by screen and lists every capability with the plan it belongs to. Prices are public during the beta, each one shown plus VAT, although nothing can be bought yet. The legal notice names the person who runs Vero, and the data processing agreement is published.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-10-02-every-feature-every-price-and-who-runs-vero</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>One home for each site: the Overview</title>
      <description>A site now opens on its Overview. Today is one of its periods instead of a screen of its own, and it compares the last 24 hours with a typical day for your site: the same 24 hours over the previous 4 weeks. Anomaly alerts use that same typical day.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-27-one-home-for-each-site-the-overview</guid>
      <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How the beta ends, in writing</title>
      <description>The beta terms now say what happens when the beta ends. There is no end date yet. When there is, you get at least 30 days of notice, by email 30, 7 and 1 days before and in the dashboard. Nothing is charged automatically, because no card is on file. If you choose no paid plan, the account moves to Hobby with one site and 30 days of data, and you can export your data as CSV at any time before that.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-27-how-the-beta-ends-in-writing</guid>
      <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Every link keeps your language</title>
      <description>Links from the site to the app, from the app back to the site and in our emails now open in the language you were reading. Emails arrive in the language you signed up in.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-27-every-link-keeps-your-language</guid>
      <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Stripe revenue without code</title>
      <description>Connect Stripe from your site settings: paste the URL Vero gives you into Stripe, then paste its signing secret back into Vero. No code. A new checkout module in the tracker adds the visit to your Stripe Payment Links and Lemon Squeezy checkout links, so each sale is tied to the source that brought it. Revenue is what was charged, without tax, less refunds.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-26-stripe-revenue-without-code</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Set up in two steps</title>
      <description>Getting started now asks for two things: your domain, then the snippet to paste, with your framework preselected when Vero detects it. The workspace takes its name from your site, and the screen tells you when the first visit arrives.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-26-set-up-in-two-steps</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Going past your plan never costs extra</title>
      <description>There is no overage billing. On Pro, a month over your plan brings a notice and an email, nothing else. If the next month is over too, an email names the plan that fits and gives you 7 days, after which the stats lock until the plan fits or the month ends. Recording continues the whole time, and in the beta the stats never lock. Only a flood past 5 times the cap is dropped. Hobby stops recording at its cap. Prices are shown without VAT.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-25-going-past-your-plan-never-costs-extra</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Visitor hashes change every day</title>
      <description>The hash that counts a visitor is now salted with a value that changes every day, so one day&apos;s hash cannot be matched to the next. The IP is still used only in memory and never stored. Your own sign-in sessions no longer keep your IP address or your browser either.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-25-visitor-hashes-change-every-day</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A demo with every screen</title>
      <description>The product demo shows every control a customer gets, with simulated data for a fictional site&apos;s launch week. It includes profit by source, with the two sources that lost money, and marks both launches on the chart. Anything that needs an account says so when you click it.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-09-22-a-demo-with-every-screen</guid>
      <pubDate>Tue, 22 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A hand-picked beta</title>
      <description>Anyone can join the waitlist. We pick the beta accounts from it by hand, never by signup order. A picked account gets Pro capabilities for free and keeps 40% off for life on the plan it chooses later. The beta page tells you what we ask in return. At the time, the AI features were off.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-08-03-a-hand-picked-beta</guid>
      <pubDate>Mon, 03 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A dashboard that answers up or down</title>
      <description>Every KPI shows its change against the previous period. The chart can draw the previous period behind it, you can drag across it to zoom in, and you can read any point by pointing at it or with the keyboard. Deploys appear on the chart. A heatmap shows your traffic by weekday and hour, each page opens on a page of its own, and entry and exit pages show where visits start and end.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-31-a-dashboard-that-answers-up-or-down</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Goals, funnels, saved segments and AI assistants as a channel</title>
      <description>Turn custom events into goals with conversions and their rate. Build a funnel from pages or events and see how many people each step loses (Pro). Save a set of filters as a segment and open it again in one click. Visits from AI assistants get a channel of their own, and browsers and operating systems get their own breakdown.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-07-goals-funnels-saved-segments-and-ai-assistants-as-a-channel</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Track without a script</title>
      <description>Send pageviews from edge middleware or your server instead of the browser: Vercel and Next, Cloudflare, Netlify, or Node, Bun and Deno. Ad blockers cannot stop it and it works with JavaScript turned off. The visitor&apos;s IP is hashed and discarded, as it is with the script.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-07-track-without-a-script</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A/B tests at the edge, with results</title>
      <description>In the AB Designer you pick an element by CSS selector, write its variant and set a goal. Vero gives you a snippet for a Cloudflare Worker, Cloudflare Pages or Netlify that changes the page before it paints, with no client JavaScript and no cookie. Results show exposures, conversions, lift and significance. A/B testing is on Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-07-a-b-tests-at-the-edge-with-results</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Take your data with you</title>
      <description>Export your raw events and revenue as CSV, up to 50,000 rows per export, on every plan. You can also export the whole account as JSON, or delete a site or the account with all its data.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-07-take-your-data-with-you</guid>
      <pubDate>Tue, 07 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Your analytics in Claude, Cursor and your own code</title>
      <description>The MCP server lets AI agents such as Claude or Cursor read your stats, revenue, attribution, goals, cohorts, realtime visitors and anomalies. The read API gives your own code the same data, with read-only or read-and-write keys per site. Both are on Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-05-your-analytics-in-claude-cursor-and-your-own-code</guid>
      <pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Our own numbers, in public</title>
      <description>getvero.dev/live shows Vero&apos;s own real traffic, measured with Vero. You can opt in to a public stats page for your own site too.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-05-our-own-numbers-in-public</guid>
      <pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Lemon Squeezy and Paddle sales, and profit by source</title>
      <description>Lemon Squeezy and Paddle send sales, renewals and refunds straight to Vero by signed webhook. A refund comes off the source of the sale it reverses. Enter what you spend on each source and read its profit and margin, not just its revenue. Revenue attribution and profit by source are on Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-04-lemon-squeezy-and-paddle-sales-and-profit-by-source</guid>
      <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Alerts when a number moves</title>
      <description>Vero checks your visitors, pageviews and revenue every day and emails owners and admins when one falls out of its usual range. Deploy annotations from your CI mark each release on the chart, so a drop lines up with the deploy that caused it. Deploy annotations are on Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-07-04-alerts-when-a-number-moves</guid>
      <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Vero in Spanish</title>
      <description>The dashboard now reads in Spanish too, like the site, with prices in euros.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-05-10-vero-in-spanish</guid>
      <pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Invite your team</title>
      <description>Each account now has a workspace. Invite teammates by email and switch between the workspaces you belong to.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-05-09-invite-your-team</guid>
      <pubDate>Sat, 09 May 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A weekly email with your numbers</title>
      <description>Each site gets a weekly email with the week&apos;s numbers. Vero also emails you when your account reaches 80% and 100% of its monthly events.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-04-19-a-weekly-email-with-your-numbers</guid>
      <pubDate>Sun, 19 Apr 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Sales tied to the visit that brought them</title>
      <description>Send each sale to Vero with the visit id that vero.session() gives you, and read revenue by the source that earned it. A live feed lists visits as they happen, and each session opens as a timeline of its pages and events. Revenue by source is on Pro.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-04-18-sales-tied-to-the-visit-that-brought-them</guid>
      <pubDate>Sat, 18 Apr 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The first version of Vero</title>
      <description>Analytics without cookies. The tracker is a small core with optional modules you switch on one by one, and a builder lets you pick only the modules your site needs.</description>
      <link>https://getvero.dev/changelog/</link>
      <guid isPermaLink="false">vero-changelog-2026-04-07-the-first-version-of-vero</guid>
      <pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>