Changelog

Changes marked Action needed can stop a Google Tag Manager trigger, a GA4 dimension or a spreadsheet built on our exports from working until you update it. When we improve detection we may also re-judge recent stored reports, so past verdicts can change (see the FAQ). Questions: support@telltale.bot.

November 5, 2026

• Fewer people called bots: Windows users whose browser window is set a few pixels in from the screen's edges (often on a second monitor), people who click where the cursor already rests, people who move the mouse quickly while a page loads, and iPhone, iPad and Android users dictating or accepting a keyboard's suggestion. Earlier verdicts are unchanged.
• A shorter tag. The tag on Installation is 8 lines shorter and in a slightly smaller font, so all of it shows without scrolling, and its box grows when you add a member ID. Its settings (CONFIG) are unchanged, and it works as before. A tag you already installed keeps working as it is. If your Content Security Policy allows the tag by its hash, copying the new tag means a new hash. The separate JavaScript only copy under the tag is gone: for Tealium iQ or another tag manager that takes JavaScript only, paste what is between the tag's two script tags.

November 4, 2026

• Fewer people called bots: visitors whose antivirus, office web gateway or school filter inspects their HTTPS traffic, Chrome and Edge 109 on Windows 7 and 8.1, people who click as soon as a page opens without moving the mouse, and Mac and iPhone users dictating into a form. Earlier verdicts are unchanged.
• An email when a site's pageviews fall by 90% or more. The email for a site that stopped sending data only went out after 12 hours with nothing at all, and a tag taken off most pages seldom gets there. Now, when a site that usually has 500 or more pageviews in 12 hours gets less than a tenth of that, and pageviews from people fell the same way, the same logins get an email with the figures, the usual causes and a link to Installation. One email per drop, and at most one of either email a site in 3 days. The Account settings > Preferences switch covers both.

November 3, 2026

• Installation says when your options changed the tag. Turning on the member ID or changing the dataLayer push changes the tag on Installation. A notice above the tag now says so, until you copy it again, so the copy on your site doesn't stay behind.
• The GTM tag template takes a member ID from JavaScript as a GTM variable. Its From a GTM variable choice (was "From a variable") explains how to make one for an ID your site keeps in JavaScript. If the member ID on Installation is a GTM variable such as {{Member ID}}, the template downloaded there has it filled in; any other JavaScript selects From a GTM variable for you to choose one. Tags already made from the template are unchanged.

November 2, 2026

• Every page says when your free trial has ended. After a trial ends without a card, a notice at the top of every report page says so, with a link to Choose a plan. Before, only the Billing page said it. Logins that see a single site don't get the notice, since they never see your plan.
• Scheduled email reports follow your plan. After a trial ends without a card, scheduled reports go only to your logins, not to addresses without one, until you choose a plan. With no plan running, none go out. Each account also sends at most 500 scheduled report emails a day to addresses that have never signed in; your logins that have signed in aren't counted. A report's row under Site settings › Email reports says how many were held back.
• The free trial records up to 500,000 pageviews. It was 1 million. Past that, every visit is still judged and counted, as before. This applies to trials already running too.

November 1, 2026

• The free trial takes no card. Signing up no longer asks for a card. To keep going after the 14 days, add a card and choose your plan under Account settings › Billing; nothing is charged before then, and nothing at all if you don't add one. A trial that ends without a card stops getting verdicts (your pages keep working, but the tag pushes no verdict to your dataLayer), and your reports stay readable until you choose a plan. We email you three days before the trial ends, the day before if no card is on file, and when it has ended. Trials that already took a card are charged at their end as before.
• An email when a site stops sending data. When a site that usually has traffic sends us nothing for 12 hours, your logins that see every site get an email saying since when, with the usual causes and a link to Installation. If you haven't installed the tag 3 days after signing up, you get the install steps. You can turn off the first one under Account settings > Preferences.

October 31, 2026

• Action needed: Gemini and Claude Duet have new agentIds. Their cloud browsers name themselves in their user agents, and their IDs came from those names. They now follow our other cloud agents (chatgpt-cloud, grok-cloud): Gemini's Task mode is gemini-cloud (was google-agent) and named Gemini (was Google-Agent), and Claude Duet is claude-cloud (was claude-agent). Both are still agentic. A Google Tag Manager trigger or GA4 filter on an old ID needs the new one. Earlier pageviews keep the name they were given.
• Gemini's signature is verified. Gemini's cloud browser signs its requests with Web Bot Auth, in a form our check did not accept. It now does, so Gemini shows as Verified under How identified, and declared-verified in the exports' identification column (was Self-declared, declared-asserted). Its name and verdict are unchanged. Earlier pageviews keep what they were given.
• Meta Muse is named on Windows when it only reads a page. Meta Muse also browses from a Windows browser in Meta's cloud. Visits from it that only read a page were shown as Unnamed agent (WebMCP), unnamed-webmcp. They are now named Meta Muse (muse-cloud), still agentic. Earlier pageviews keep the name they were given.
• The agents ranking lists each visitor under its verdict. On All traffic, a visitor judged agentic or bot is no longer also listed under Human for pages that looked human before the agent acted, or for a tab of its own beside the agent's; those pages are left out of the ranking's pageviews. Human now lists exactly your human visitors, with all their pageviews, and links to them.
• Action needed if you send verdicts to GA4 with gtag.js and update the recipe: telltale_event has new values. The GA4 recipe for gtag.js (GA4 without Google Tag Manager) now sends the verdict at once, as the GTM recipe has since October 27. Before, the Google tag held it a few seconds for its next batch, and a visitor whose browser closed in that time, as many bots do, never sent it. This needs the tag's dataLayer push, which is on unless you turned it off. In the new recipe, telltale_event is telltale.verdict or telltale.verdict-update, the same as the GTM recipe's (it was verdict or verdict-update). Your current copy keeps working as it is, with the old values and batched. When you replace it with the new one, update any GA4 report or filter that reads the old values. The event's name and its other parameters are unchanged.

October 30, 2026

• Action needed: the CSV exports give confidence as a band. The All traffic and Paid clicks exports have a confidence column of high, medium or low, how sure Telltale Bot is of the verdict given, the same bands as the confidence field in the dataLayer. It takes the place of automation_confidence, a number to two decimals. A spreadsheet that reads that column needs the new name and values.
• Search by page. The search box on All traffic now finds pageviews by their page: type a path such as /products/ or paste a page's URL to see who requested it. The query string is not stored, so it is left out of the search. See Reading your reports.
• Perplexity Computer is named when it only reads a page. Visits from Perplexity Computer's cloud browser that only read a page were shown as Unnamed agent (WebMCP), unnamed-webmcp, agentic, and some as bot (automated-browser). They are now named Perplexity Computer (perplexity-cloud), agentic. Earlier pageviews keep the verdict and name they were given.
• Grok is named on more visits. Some visits from Grok's cloud browser were shown as Automated browser (automated-browser), bot. They are now named Grok (grok-cloud), agentic. Earlier pageviews keep the verdict and name they were given.
• Device details from Matomo 6.5.2. We read the browser, operating system and device from each visitor's user agent with Matomo's Device Detector, now its latest release, 6.5.2. Safari on a Mac shows its macOS version (26, for example) where it showed 10.15, many phones show their marketing name, and foldable phones are a phablet where they were a smartphone. You see this in the device line on All traffic, in the CSV exports' os_version, device_model and device_type columns, earlier pageviews included, and in the deviceType field of the dataLayer if you added it.

October 29, 2026

• Claude Duet is named, and agentic. Claude Duet, Anthropic's cloud browser, names itself Claude-Agent in its user agent and was shown as bot under that name. It is now agentic and named Claude Duet. Its agentId stays claude-agent; the agentName field changes from Claude-Agent to Claude Duet. When Duet only looks something up, it uses Anthropic's Claude-User fetcher, which runs no JavaScript, so those visits never report. Earlier pageviews keep the verdict they were given.

October 27, 2026

• Grok is named again. Since a change to Grok's browser around October 21, its visits were shown as bot (automated-browser) when it acted on a page, and often as a person when it only read one. Script version 2.21.0 names it again when it acts, and on some visits where it only reads a page: it is Grok (grok-cloud), agentic. Other visits where it only reads a page are still seen as a person. This is based on our own Grok runs so far, and some Grok visits may still go unnamed. Earlier pageviews keep the verdict they were given.
• Verdicts reach GA4 at once. GA4's Google tag holds most events for a few seconds and sends them together, so a visitor who left within those seconds, as many bots do, could leave before its verdict reached GA4. The GTM container on Installation and the GA4 recipe now send the verdict with a Custom HTML tag that hands it to your Google tag to send at once, in place of a GA4 Event tag. It needs your GA4 Google tag in the same container. The event's name and parameters are unchanged, and a GA4 Event tag you already set up keeps working; to send at once, replace it with the tag in the recipe.

October 26, 2026

• Perplexity Computer is named correctly again. After an update to the browser Perplexity Computer uses in Perplexity's cloud, a visit where it acted on a page was named Perplexity Comet (perplexity-comet), and shown as bot (automated-browser) until it acted. Script version 2.19.2 names it Perplexity Computer (perplexity-cloud) again once it acts, and Unnamed agent (WebMCP), unnamed-webmcp, agentic, before that. Earlier pageviews keep the verdict and name they were given.
• Instinct is named. Visits from Instinct's cloud browser were shown as Unnamed agent (WebMCP), agentId unnamed-webmcp. They are now named Instinct (instinct-cloud), still agentic. A few visits where it acted through another browser were shown as bot (automated-browser) and are now Instinct, agentic. Earlier pageviews keep the verdict and name they were given.
• The tag works in Tealium iQ and other tag managers that take JavaScript only. The tag is now a single script, with no HTML around it: its comment and its preconnect to our server are inside it. Installation also has it as JavaScript only, under the tag, and the install guide has a section on another tag manager. A tag you already installed works as before. If your Content Security Policy allows the tag by its hash, copying the new tag means a new hash.
• ChatGPT agent is named only on its own proof. Some automated browsers were shown as ChatGPT agent (chatgpt-cloud), agentic. They are now bot (automated-browser, or selenium when we can tell). ChatGPT agent's own visits, which carry OpenAI's verified signature, are still named and agentic. Earlier pageviews keep the verdict they were given.
• Fewer people using a screen reader called agents. In Chrome and Edge, a button or link activated with a screen reader or voice control (Narrator, for example) clicks the way an automation tool does, so those visitors could be shown as Copilot in Edge (copilot-edge) or Unnamed agent (local browser), unnamed-local-browser, agentic. Script version 2.19.1 tells these clicks apart, and they no longer count as automation. Earlier pageviews keep the verdict they were given.
• This month's estimate on Usage. For the current month, Account settings > Usage now adds two rows under your sites, each against your plan: October at this rate (the pageviews so far, plus the rest of the month at that rate) and Full month at this rate. The rate is your sites' pageviews a day over the last 7 days, or since a site's first pageview when that is more recent.

October 25, 2026

• A year of history on All traffic. Reports are still kept 30 days, but each day's counts (visitors and pageviews by verdict, host, agent and country) are now kept 13 months. Pick a range of up to a year on All traffic, or the new 90 days and 12 months presets. A range that reaches back past 30 days counts each visitor once for every day they were seen (visitor-days), and the new Visitors: Distinct / Per day switch shows a shorter range the same way, so this month and last quarter compare on equal terms. The visitor list, ISPs and the host, agent, country and search filters still cover the last 30 days. The history starts with the 30 days of reports each site has when this ships.
• Turn add-ons on yourself. Account settings › Add-ons turns Paid clicks and Member accounts on or off for every login of your account, without writing to us. New accounts start with both on. Both are free while we're in beta. Turning one off hides its tab and deletes nothing.
• Verdict shares on All traffic. The top of All traffic now looks like the top of Sites: a donut of visitors by verdict, and each verdict's share of visitors in large type, with its visitors and pageviews under it. Click a share or a slice to see only those visitors, and again to see every verdict.
• High automated shares stand out in Paid clicks. The Automated (Agentic + Bot) share of an ad platform, a source / medium or a campaign is orange from 25% and red from 50%, on rows of 10 or more visitors.
• Traffic overview by email. Every site now has a traffic overview under Site settings > Email reports: visitors and pageviews against the period before, visitors by verdict, the agents they were identified as and their countries, over the period you pick, daily or weekly, to logins or to any email address. It carries counts only, with no attachment.

October 24, 2026

• A faster first verdict. The tag now starts with a line that lets the browser open its connection to our server while the page loads, so the verdict reaches the page sooner on a visitor's first page. A tag you already installed works as before; to add the line, copy the tag again from Installation or put it above your tag (A faster first verdict). The GTM tag template can't carry it.
• Meta Muse is named again. Since a change to Meta Muse's browser around October 17, its visits were shown as Unnamed agent (WebMCP), agentId unnamed-webmcp. They are named Meta Muse again (muse-cloud), still agentic. Earlier pageviews keep the name they were given.
• Fewer visitors called agents or bots by mistake. Some visits shown as Unnamed agent (local browser), unnamed-local-browser, were people, for example filling a form with a password manager: they are now human. Others were automated browsers running on servers: they are now bot, automated-browser. Claude in Chrome (claude-extension) is named only on evidence from Claude in Chrome itself; other visits it named are now Unnamed agent (local browser), still agentic. Earlier pageviews keep the verdict they were given.
• Bots and agents as GA4 segments. Because the verdict is an event, filtering a GA4 report on it keeps only the verdict events. Send the verdict to your analytics now shows how to see everything those visitors did: a user segment for bots, a session segment for agentic visits, and an audience for standard reports.
• Fewer people called bots: in DuckDuckGo's browser on Android and Windows, in Opera Mini on Android, and in Safari 26 and later when AutoFill fills in a form for them (a saved login or a contact card), which Safari types in one key at a time. Earlier verdicts are unchanged.

October 21, 2026

• Invites last 7 days. An invite to choose a password now works for 7 days (it was 72 hours). An expired one says when it expired and offers to email a new link to the same address, so the person you invited no longer has to ask you to resend it.

October 20, 2026

• A Google Tag Manager container with GA4 included. Site settings > Installation now offers a GTM container to import (Admin > Import Container): our tag as a Custom HTML tag, filled in for the site with the options you chose there, plus a GA4 event for each verdict, with the trigger and variables it needs. Put your GA4 measurement ID in it and register the event's parameters in GA4. See the install guide. The tag and the dataLayer are unchanged.

October 18, 2026

• Account settings. Settings, under your name, is now Account settings, with a sidebar like Site settings: Preferences (theme, time zone), Security (password, two-factor sign-in, and now your sign-in email address, changed through a link to the new address), and, depending on your login, Billing, Usage, Team, Agreement and Close account. Old links keep working.
• Terms accepted with a checkbox. When you sign up, you accept our terms of service, with the Data Processing Addendum and Acceptable Use Policy, by ticking a box on the password page, so sign-up has one step fewer. An account still asked to accept the terms gets the same box. Nothing changes for accounts that have already accepted.
• Installation shows the first pageview arriving. Until a site's first report comes in, Site settings > Installation waits for it and turns green when it arrives.
• Fixed: script version 2.17.0 could change your page's own error reports. On pages using Angular (zone.js) or SES, an error's stack trace could come back as a list instead of text, which error trackers read wrong, and pages with very many global variables spent more time in our script. Script version 2.17.1 fixes both; nothing to change on your side. The tag and the dataLayer are unchanged.
• No more test message in the browser console. Script version 2.18.2 no longer shows "Telltale Bot Error Test - Ignore" in DevTools' console (it appeared with the Verbose level on). The tag and the dataLayer are unchanged.
• The script takes less of your page's time while it loads. Script version 2.18.1 moves part of its setup to when the browser is idle, so the work it does while your page is loading takes about half as long in Chrome and Edge, and much less in Firefox and Safari. The tag and the dataLayer are unchanged.
• Fewer people called bots on Samsung Galaxy phones and tablets with Exynos chips (such as the Galaxy S22, S24 and S25, A55 to A57 and Z Flip7). Earlier verdicts are unchanged.

October 17, 2026

• Clearer agent categories in the viewer. The agents ranking's categories are now a short list of our own: AI agents, Automation, Search engines, Advertising, AI crawlers, SEO & marketing tools, Social previews, Monitoring & security and Other bots. Google Ads and AdSense are under Advertising, Googlebot under Search engines, AhrefsBot and Semrush under SEO tools. Agents with the same name, like Google Ads' desktop and mobile crawlers, are now one row. The agentId in the dataLayer and the exports' bot_category column are unchanged.
• The script stays out of your page's way in more setups. Script version 2.14.0 never lets an error of its own reach your page or your error tracker, and no longer sends its test message through your console, so Sentry, Datadog and session recorders stop showing "Telltale Bot Error Test - Ignore". A second copy of the tag or script on a page now does nothing, and older jQuery keeps its fast selector engine even then. It also works next to Prototype.js, MooTools, Angular, WP Rocket's delayed scripts and pages that change built-in JavaScript objects; it does nothing in Partytown, and a page your visitor's browser prerenders but never shows is no longer counted as a pageview. Our servers now accept the tracing headers Sentry, Datadog, OpenTelemetry and New Relic add to requests, so those sites no longer lose reports with CORS errors, and pages with a strict Cross-Origin-Embedder-Policy no longer log an error on each report. Nothing to change on your side: the tag and the dataLayer are unchanged.
• Member ID expressions are checked. Under Site settings > Installation, a JavaScript expression for the member ID that would break the tag (a semicolon, a statement, an unmatched bracket or quote) is refused with the reason, and a trailing comment no longer breaks it.
• More crawlers by name. A crawler whose user agent names it after "compatible;" with no contact link is now named after it instead of Automated browser: GoogleOther (Google's crawler for products other than Search, most of these), Google's page renderer (google), Shap-User, pageburst and a few more. WebPageTest runs are named webpagetest. Their verdicts are unchanged (bot); their agentId in the dataLayer is now the name, no longer automated-browser. Pageviews of the last 7 days were re-judged.
• The page's HTTP status. Script version 2.13.0 reports the status the page itself was served with, so a "Page Not Found" page that carries the tag shows as 404. In All traffic, a pageview whose page answered with anything but success has its status next to the page; both CSV exports end with a new http_status column (empty when unknown). Chrome, Edge and Firefox report it; Safari does not. Pageviews from before have none. Earlier columns keep their places; the tag and the dataLayer are unchanged.

October 16, 2026

• Fixed: the script could stop older jQuery code on your page. On sites using jQuery before 3.7, loading our script ahead of jQuery made jQuery fall back to its own, slower selector engine, which fails on modern selectors such as :is() and can stop the page's own scripts (one site's homepage slider never started). Script version 2.12.1 fixes it; nothing to change on your side. The tag and the dataLayer are unchanged.
• A Google Tag Manager tag template. Site settings > Installation now offers our tag as a GTM tag template, already filled in for the site: import it under Templates, then add a Telltale Bot tag. It does the same as the Custom HTML tag, for containers that don't allow Custom HTML. See the install guide. The tag and the dataLayer are unchanged.
• Expand a ranking to see every row. On All traffic, Identified as, Countries and ISPs, and on Paid clicks, By source / medium, have a maximize button in their title bar when they run past one page. It opens every row in a window with a search box: type to narrow the list (a region or a campaign name finds its country or source / medium). Click a name to filter the report as before; press Esc or × to close.
• Sort a table by any column. Click a column heading to sort by it, largest numbers first or names from A to Z; click again to reverse. This works on tables that show every row: By host on All traffic, the tables on Paid clicks, each member's devices on Member accounts, Usage, Team, and the visitor lookup under Site settings > Delete, and in the expanded Identified as window. The page does not reload.
• Action needed: Member accounts has one export. The details CSV (one row per member, device and IP) is gone; Export accounts (CSV) stays, with every location, IP, ISP and proxy of each member listed in its row.

October 15, 2026

• Fewer people called bots: office workers behind a corporate web gateway or browser isolation service, visitors on government and school networks, phones on mobile networks, Tor Browser and Mullvad Browser, Safari before version 17, older Chromebooks and Android phones, Android apps' built-in browsers, Samsung Internet, the Huawei, Xiaomi, vivo and OPPO browsers, DuckDuckGo for Mac, and browsers in fullscreen.
• Beta terms. Our terms of service replace the alpha agreement, with a Data Processing Addendum and an Acceptable Use Policy as part of them, all linked from Docs and every page's footer. If your account accepted the alpha agreement, you don't need to accept again. The viewer calls it the Telltale Bot agreement.
• Final beta prices. The plans on the pricing page are final, and new accounts start with a 14-day free trial. See Trial and cancelling.
• The install guide and Reading your reports are public, under Docs.

October 14, 2026

• Perplexity Comet by name. When Comet's Computer mode acts in the person's own Comet (Control Browser), the visitor is now named perplexity-comet (Perplexity Comet). perplexity-cloud (Perplexity Computer) now names only Perplexity's cloud browser. See AI agents.
• A visitor judged human is no longer named after an agent. In All traffic and its CSV export (agent, agent_label), a human verdict now always reads Human. Before, a weak match could show beside it, such as Automated browser or Unnamed agent (local browser). The dataLayer already said human and is unchanged. Pageviews from before keep their old name until they are re-judged.
• Paid clicks by source / medium. Campaigns are grouped under their utm_source / utm_medium, with totals for each pair (a visitor counts once, whichever of its campaigns it came from). Open a row for its campaigns; click a source / medium to list its landings.
• Fewer missed pageviews (script 2.11.0). When a visitor leaves within a second or two of arriving, the script's first report is no longer canceled on the way, so that pageview is now recorded and judged. The page itself is gone by then, so it gets no verdict. Nothing changes in the tag or the dataLayer.

October 13, 2026

• Visitors over time by hour. On All traffic, a range of two to seven days can show its chart by hour as well as by day: use the By day / By hour switch above the chart.

October 12, 2026

• Plan limits in two steps. At one and a half times your monthly plan we stop recording your reports, but your pages keep getting verdicts. At twice your plan, reports are refused as before. We email you when each step starts. See the FAQ.
• Custom domain: a hostname for the script. Besides the reports hostname (a CNAME to in.ttbcdn.net), Custom domain now takes a script hostname, a CNAME to js.ttbcdn.net, so the script comes from our CDN under your name. With only a reports hostname, the tag now loads the script from js.ttbcdn.net. A tag already using your reports hostname for the script keeps working. If your Content Security Policy names your hostname, add the script hostname to script-src. See the install guide.
• Site settings > dataLayer is now Data layer fields: the fields you choose there reach the page events and Telltale.verdict too, not only the dataLayer. The preset is a drop-down above the fields, and the example of what the page receives sits on top, as a dataLayer push or as an event listener sees it, and follows your choices before you save. Installation's Push the verdict to the dataLayer switch and the dataLayer name are now saved for the site, and that page shows the matching view. So is Send the signed-in member's ID, with its cookie name or JavaScript expression.
• Action needed: the rdns column is gone from the All traffic, Paid clicks and Member accounts details CSV exports (it has been empty for new pageviews since October 9). The columns after it move one place left.
• The ISPs ranking on All traffic has a Type column: the ISP type of most of its visitors' IPs (isp, mobile, hosting, business, ...), as isp_type in the exports. A + means some had another type; hover the row for the counts.
• Site settings > Privacy is gone: Erase a visitor is now the first part of Site settings > Delete, and you type erase to confirm, instead of the site's name.

October 10, 2026

• Action needed: dataLayer events renamed (script 2.10.0). The verdict is pushed as telltale.verdict (was telltale.load), and a changed verdict later on the same page as telltale.verdict-update (was telltale.update). telltale.exit is gone: it described the previous page, whose own verdict already included it. GTM triggers on the old names stop firing. The install guide has a table of both events.
• Custom domain. Site settings > Custom domain serves the script and takes reports on a hostname of your own, through a DNS-only CNAME. See the install guide.
• Team. Logins that see every site can invite colleagues by email, give a login one site only (an agency's client), and remove logins, from Team under your name.
• Installation has switches above the tag for the dataLayer push and, with Member accounts, where the member ID comes from. The copied tag follows them.
• The install guide's Consent section is rewritten: run the tag before consent, as a security measure.
• Report pages: the verdict tiles that filter are underlined, a selected row is marked with a bar at its left, the agent filter reads "identified as", and Paid clicks shows campaigns 10 at a time.

October 9, 2026

• The verdict without Google Tag Manager (script 2.9.0). The page gets a telltale:verdict event on window, a telltale:verdict-update event when the verdict changes, and Telltale.verdict for code that runs later. The dataLayer push is on in the tag by default and can be turned off.
• A second verdict on the same page. A couple of seconds after a visitor first clicks or types, the script reports again and the page gets an updated verdict. Before, what a visitor did on a page only counted from the next page on.
• Plan limits. We email you at 80% and at 100% of your monthly plan. If a month reaches twice your plan, reports are refused until the month ends or your plan is raised. See the FAQ.
• If a site passes its daily report limit, its pages still get verdicts; only storing the reports stops.
• Two-factor sign-in (an authenticator app), optional, under Settings.
• Today, Yesterday, 7 days and 30 days load much faster on large sites: we build them ahead of time.
• New pageviews no longer have a reverse DNS name: the rdns CSV columns are empty for them.
• Site settings > Delete asks you to type clear or delete to confirm, instead of the site's name.
• The install guide covers Content Security Policies with 'strict-dynamic' and Trusted Types.
• A subprocessors page with an RSS feed, and 30 days' notice before a new one.

October 8, 2026

• Email reports (Site settings, with Member accounts): the flagged member accounts over the period you pick, daily or weekly at the day and hour you choose, with the CSV attached, to logins or to any email address.
• Action needed: Member accounts CSV columns. countries is now locations (the number of places; the list is location_list), a browsers column ends each row, and at_once_from, at_once_to, peak_hour_from and closest_at moved to the details CSV only.
• More agents named while they only read a page: the ChatGPT app, ChatGPT in Chrome, Meta Muse and Grok. Perplexity Computer is named when it acts.
• Fewer people called bots on Amazon Fire tablets and some Android phones.
• A new account with no data yet is pointed to the demo.
• The agreement is accepted with one OK button.

October 7, 2026

• The report tabs are All traffic, Paid clicks and Member accounts, and the viewer counts visitors (was users). URLs and CSV columns are unchanged.
• Email invites to choose a password, and Forgot your password? on the sign-in page.
• A public demo of the viewer with made-up traffic.
• Action needed: the agent chatgpt-extension is labeled "ChatGPT in Chrome" (was "ChatGPT for Chrome"), in agentName too. The ID is unchanged.
• CSV exports give automation_confidence to two decimals (was three).

October 6, 2026

• Member accounts (script 2.7.0): with the member ID in the tag, a tab of automation and account sharing per signed-in member, with a CSV and a details CSV for customer service.
• Countries and ISPs on All traffic, each a ranking you can filter by. Each IP shows its approximate city and region.
• Reports are sent compressed (script 2.6.0).
• Viewer pages load faster, and paging no longer jumps to the top of the list. Each visitor lists 20 pageviews, with a link to the rest.

October 5, 2026

• Action needed: agent IDs renamed to one scheme, product then surface. In agentId, the viewer and exports: claude-inapp → claude-app, claude-for-chrome → claude-extension, claude-computer-use → claude-cloud, codex → chatgpt-app, chatgpt-agent → chatgpt-cloud, gemini-in-chrome → gemini-chrome, edge-copilot → copilot-edge, meta-muse → muse-cloud, browser-agent → unnamed-local-browser, webmcp-agent → unnamed-webmcp. The agents page lists every ID.
• ChatGPT agent and ChatGPT in Chrome are named.
• Site settings > Privacy: find a visitor by IP address or member ID and erase everything stored about them. Site settings > Delete: clear a site's reports, or delete the site.
• Reading your reports, a guide to the viewer.
• Signing out signs you out on every browser.

October 4, 2026

• The install guide and the agents page are published.
• Gemini in Chrome is named when it acts, and Claude in Chrome while it reads a page too (script 2.4.0).

October 3, 2026

• Usage (under Settings): pageviews by month for a year, against your plan, by site, with a CSV.
• A visitor on a commercial VPN is no longer called a bot for the VPN alone.
• Opera Mobile is no longer named as the Claude app.

October 1, 2026

• Both CSV exports end with the visitor's country and network: country, isp_name, isp_domain, isp_type, proxy_type, proxy_name. All traffic shows an ISP column.
• ispType / isp_type is hosting only when the IP itself is a hosting address, so iCloud Private Relay and corporate gateways no longer read as hosting.
• Copilot in Edge, the ChatGPT app and Meta Muse are named. Fetchers a person asked for directly (ChatGPT-User, Claude-User and the like) are agentic, not bots.

This log starts on October 1, 2026.