Aiola desktop version 2.0.8, released October 20, 2026, brings five fixes and improvements to Analytics. Revenue bars stay visible, renewals get rows, extension pings become custom events, bots get names, and hover cards stay readable.
Revenue bars stay put across tabs
The purple revenue bar no longer disappears when you scroll a list or switch tabs. It now appears on every tab, including Referrer, Screen, Language, Region and City. Those tabs are explicitly named in the shipped release note.
This matters when you move between different ways of looking at the same revenue. You can scroll through a long list without losing its purple revenue bars. Switching from Referrer to Region also keeps that visual information available. Revenue remains visible as you move from acquisition details to location details.
For example, you might start with referrers, then look at the cities associated with revenue. Previously, a disappearing bar interrupted that comparison. In 2.0.8, the bar stays put as you change tabs or scroll. The change removes a display problem from that review.
See Aiola Analytics for the broader feature. This release makes its revenue presentation more consistent during everyday browsing.
Renewals appear even without a visit
A customer who renewed without visiting now appears as a revenue-only row. That row appears in Locations, Tech, Pages and Sources. Previously, the customer was left out of those lists.
A renewal and a site visit are different activities. An existing customer can renew without returning to browse a page. You still need to see that revenue when reviewing the lists named above. The new row makes that renewal visible without requiring a fresh visit.
For a subscription business, this helps explain revenue associated with existing customers. A quiet day for visits can still include renewals. Revenue-only rows give those renewals a place in the relevant views.
The release addresses visibility for this specific case. It does not require you to treat the renewal as a new browsing session. When reviewing Sources or Pages, look for the revenue-only row alongside rows containing visitor activity.
Extension pings become custom events
Extension pings that were counted as page views are now recorded as custom events. Lists also stop showing rows labelled "(unattributed)". These are the two parts of the extension fix described in the release note.
The distinction matters because a ping from an extension is not the same activity as viewing a page. Recording that ping as a custom event gives it the appropriate event type. It also removes the "(unattributed)" rows from the lists you review.
If those rows previously made a list harder to interpret, this change directly addresses that clutter. You no longer need to work around that label while reading the list. The release describes a correction to how these extension pings are recorded and presented.
For your next review, keep page views and custom events conceptually separate. That distinction is the reason this change matters. The ping remains an event, with its classification corrected.
Bot traffic shows the client name
Clients that are not browsers now appear in Bot traffic under their real name. The shipped example is "Google Play link checker". Previously, those clients appeared as "Unknown client".
A name gives you something concrete to recognize while reviewing automated traffic. "Unknown client" tells you little about which client made the request. "Google Play link checker" identifies the client described by the release note. That makes the row easier to understand without guessing what the generic label represents.
This change matters when you need to distinguish automated clients from browser activity. Open Bot traffic and read the client name attached to the row. The improvement is the named presentation of these clients within that view.
For background on crawler names, browse the crawler directory. The release claim here is specifically about replacing "Unknown client" with the client's real name. It does not announce a new crawler count.
Hover cards keep row details together
Hovering any row in Sources, Pages, Locations or Tech now shows visitors, views and revenue together. Those values appear in one card that is never cut off. The release calls this "Clearer row details".
This matters when a row needs more context than its visible bar provides. You can inspect the visitor count, view count and revenue in the same place. A card that remains readable helps you finish that inspection without losing part of the detail.
For example, hover a row in Sources while reviewing how visitor activity relates to revenue. Then inspect a row in Locations with the same three measures available. The card brings those measures together for the row you are examining.
The benefit is a clearer view of individual rows. Combined with persistent revenue bars, it makes both scanning and closer inspection easier. Read the [October 20 release entry][release-208] for the published list of changes.
Who gets it with Pro or the trial
Hosted Analytics requires Pro or the 7-day trial. The trial is available to first-time Pro Monthly customers, with a card required. GUI Lifetime alone does not include hosted Analytics access.
Pro costs $24 per month or $240 per year and includes 100k events. GUI Lifetime options cost $49, $89 or $129 as a one-time payment. Check pricing when choosing between desktop access and hosted Analytics.
For current revenue setup, Stripe connects separately for each analytics site. Checkout Sessions need aiola_visitor_id and aiola_session_id metadata to attribute payments. That setup is supporting context for using revenue today, rather than an additional 2.0.8 change.
Try it in Aiola: download the desktop app for macOS 12+ or Windows 10+. The download is free. Open Analytics with Pro or the trial, then inspect revenue bars, renewal rows, Bot traffic and row details.
