--- title: "Changelog — SealMetrics" description: "Product updates and new features from SealMetrics. See what we have shipped recently." canonical_url: "https://sealmetrics.com/changelog/" lang: "en" content_type: "product" owner: "web" llm_priority: "useful" last_verified: "2026-08-10" source: https://sealmetrics.com/changelog/ publisher: SealMetrics --- Changelog # What we have shipped. Product updates, new features, and improvements. We ship continuously and document everything. ## July 2026 New ### Seal AI Private — EU-hosted AI with token packs Seal AI Private is generally available: the managed AI provider behind LENS, processed entirely in the EU (Paris) with no prompt retention and no API key to manage. A paid add-on on Growth, included on Scale and Enterprise, with 5M tokens per calendar month for the whole organisation and email alerts at 80% and 100%. Extra 5M-token packs cost €358.80 each, never expire, and are consumed only after the monthly quota. When the quota runs out, any user can fall back to their own Anthropic, OpenAI, Gemini or DeepSeek key. Improved ### Sources report — referral traffic grouped by domain, GA4-style The Sources tab now shows referral traffic as source domains (reddit.com / referrer), unifying historical data under the same convention. The Referrers tab keeps its URL-level detail, one row per referring URL. In the API, referral rows now appear in /stats/sources as domains and are excluded from /stats/terms. New ### Custom Channel Grouping — from the dashboard, CSV or MCP Define your own marketing channels on top of (or overriding) the GA4-style defaults, with a drafts → test → publish workflow. Rule form with a “Test a visit” tester that runs the same engine as the pixel, an Override button on default channels, CSV/JSON import and export, and MCP tools for AI-assisted rule authoring. Every write tool is draft-only by design — publishing is always a human action. New rules take effect in about 5 minutes and never rewrite historical data. Improved ### Channel classification — more accurate Direct and Referral Default classification rules for Direct (no referrer, no campaign parameters) and Referral (external sites without UTM tagging) were refined to match the GA4-style conventions the tracker already used internally. From July 20, 2026 a portion of traffic previously reported as Unassigned appears as Direct or Referral. New traffic only — historical rows keep their classification, and custom channel rules keep priority. ## June 2026 Improved ### Bot-blocking algorithm update — fewer false positives Deployed June 2, 2026 at 20:00 CET. The bot-blocking algorithm no longer filters out legitimate human traffic that was previously misidentified as automated. Accounts affected by the old behaviour see a recovery in reported human traffic from that timestamp onward. ## May 2026 Improved ### Attribution: internal hits with UTMs no longer open a new session From May 25, 2026, when a hit carries UTM parameters and the referrer is your own domain, the referrer wins: the hit is counted as a pageview inside the existing session and the UTMs are ignored. Session counts stop being inflated by UTM-tagged internal links, and campaign sources reflect genuine external entries only. Historical data is unchanged. Fixed ### API: /exports/* and /batch returning 403 with API keys — fixed A permission check on /exports/* and /batch required a scope API keys don't carry, returning 403 insufficient_scope for valid keys. Fixed in production, no action required — existing API keys now work on these routes unchanged. ## February 2026 Launch ### SealMetrics V2 is here The most significant update since we started, rebuilt from the ground up: a faster, cleaner dashboard; smarter attribution; compliance ready for GDPR, CNIL, UK PECR and the upcoming EU Digital Omnibus; a new, better-documented API; and a lighter tracking script with better SPA support. V2 is the default for all accounts — data, settings and tracking code keep working. ## November 2025 Improved ### Robot user-agent database expanded Added 158 new robot-related user agents on Nov 21, improving detection of automated traffic and precision when separating real users from bots. New ### Legal approval for IP-based bot filtering After legal review, incoming hits are checked against our bot IP database: a match is excluded from your analytics, a non-match is registered as human traffic without the IP being stored. No human IP is ever retained, tracked or exposed. Precision without crossing the privacy line. Fixed ### Facebook traffic classification fix Visits carrying only fbclid and no UTM parameters were being categorised as facebook-ads. From Nov 17 at 19:00 UTC they are classified as Facebook Organic, and only traffic with proper UTM campaign parameters counts as Facebook Ads. Expect a slight increase in organic Facebook traffic from that timestamp; historical data is unchanged. Improved ### Facebook Ads attribution — fbclid no longer used Breaking change from Nov 13 at 19:00 UTC: the fbclid parameter is no longer used to identify Facebook Ads traffic, because it is neither reliable nor consistent. Facebook Ads attribution now requires properly configured UTM tags (utm_source=facebook, utm_medium=paid or equivalent). Audit your active campaigns and add UTMs to keep full visibility. Improved ### 2.5× faster data processing Increased core capacity in the processing infrastructure on Nov 10 at 22:00 UTC. Data now processes 2.5 times faster: quicker dashboard loading, live data updates and instant report generation. Want to see these features in action? [Start 14-day trial](https://my.sealmetrics.com/register) Or explore the [full product](https://sealmetrics.com/product/) and [pricing](https://sealmetrics.com/pricing/).