Back to News
OmniCon 2.0.325 — Analytics you can act on, views from real readers, and OmniCon for Japan

OmniCon 2.0.325 — Analytics you can act on, views from real readers, and OmniCon for Japan

November 4, 2026

Eleven versions on from 2.0.314. A new analytics dashboard shows top content, sources, geography and devices, with analytics for each article. Crawlers and your own previews no longer count as views on your channel pages, visitors are counted without cookies, and IP addresses are no longer stored. Plus Japanese legal pages and press releases, and mobile images without writing HTML.


OmniCon 2.0.325 — Analytics you can act on, views from real readers, and OmniCon for Japan

November 4, 2026

Eleven versions on from 2.0.314. This release replaces the single line on your analytics page with a full dashboard, changes what counts as a view on your channel pages, and stops storing readers’ IP addresses. It also finishes much of the work of making OmniCon ready for customers in Japan.


Three things stand out: a new analytics dashboard, counting real readers, and better privacy for your readers.

A new analytics dashboard

Analytics used to show a fixed 30-day line. It now answers what gets read and where readers come from.

  • Pick a range. Today, 7, 30 or 90 days, 12 months, or your own dates. Views, visitors and views per visitor each show the change from the previous period, and today is compared with yesterday up to the same hour.
  • Top content. Your 50 most-read articles and pages, with views, visitors and a trend line. Filter by title and sort by views or visitors.
  • Where readers come from. Search, social, AI assistants, email, campaigns and other sites, plus referring sites and your utm_source, utm_medium and utm_campaign tags.
  • Who reads. Countries, cities, devices, browsers, operating systems and languages.
  • What readers searched for. The most frequent searches on your channel.
  • Analytics for each article. Every article has its own page, with views and visitors over time, sources, countries and devices. The article page, the editor and the article list now show real views for the last 30 days, in place of a count that always said zero.

Visitors, sources and audience start with this release, so the first full day appears tomorrow. Earlier days show views only.

Counting real readers

  • Crawlers no longer count on your channel pages. Search engine crawlers, AI crawlers such as GPTBot and ClaudeBot, monitors and scripts are left out of your views. If much of your traffic was automated, your numbers will be lower from today. Your readership has not changed, and past days stay as they were.
  • Your own previews no longer count. Views by signed-in members of your organization are not recorded.
  • Visitors, without cookies. A visitor is counted once a day, using a value that changes every day and is then deleted, so nobody can follow a reader from one day to the next. A range adds up each day’s visitors, so someone who reads on three days counts three times.
  • Reads through the content API still count as views. If your site fetches articles through the API, your views carry on as before. The API can’t see who the reader is, so these reads have no visitors, sources or audience.

Better privacy for your readers

  • IP addresses are no longer stored. A reader’s IP address is used to work out their location and daily visitor count, then discarded. Referrers are kept without their query strings.
  • Locations are looked up on our own servers. Reader IP addresses used to be sent to an outside service. They no longer leave our servers.
  • OmniCon’s own analytics are off your channel pages. Our Google Tag Manager tag used to load on channel and community pages. It now runs only on omnicon.cloud. You can still add your own tags.
  • An updated privacy policy. The policy now describes all of this, including how long each kind of analytics data is kept.

OmniCon for Japan

  • Press releases in Japanese. A release now has a language, picked on the send form and accepted by the API and MCP. Its footer, opt-out link and unsubscribe page follow it.
  • Legal pages in Japanese. The privacy policy and terms are published in Japanese, and we added a notice under the Specified Commercial Transactions Act and a company page. Sign-up now states that creating an account means agreeing to the terms and privacy policy.
  • Public pages in Japanese. News, Help, unsubscribe, invitation and error pages are translated, and News and Help now have their own Japanese articles.

Also in this release

  • Mobile images without writing HTML. In the article and page editors, select an image and press the mobile image button to show a different image on phones. Ones you wrote by hand can be swapped or removed the same way.
  • Large images stay inside the editor. Images wider than the editing area are now shrunk to fit it while you edit. The saved HTML and your public page do not change.
  • Bug fix: views were badly undercounted. Finished hours were never added up, so the analytics chart showed far fewer views than were recorded. Every view now counts, and missed runs catch up on their own.
  • Bug fix: daily analytics stopped after October 29. The nightly job timed out, so the following days were missing. Those days have been rebuilt, and October’s monthly totals with them.

The biggest change here is the one you may notice first: on your channel pages, your views now mean readers. If the numbers look different from what you expected, or there is something you would like the dashboard to show, drop us a note.

release analytics privacy japanese editor bugfix