Update2 September 2026, 09:03

ICanUp Analytics Expanded with Countries, Traffic Sources, Devices, Bots, and Activity Time

ICanUp analytics expanded with countries, devices, browsers, operating systems, traffic sources, human and bot classification, referral domains, and hourly activity without storing raw IP addresses.

The first version of ICanUp analytics already answered the basic questions: what content is being read, how many views it receives, which locale is used, and how activity changes by day.

The next step was understanding the context behind those views: where readers come from, which devices they use, which external sources send traffic, how much activity belongs to bots, and when that activity happens.

By the end of August and the beginning of September 2026, ICanUp analytics gained this deeper level of detail.

What became visible

Countries

Views can be analyzed by country when the country can be reliably resolved through a trusted infrastructure source.

Devices

Analytics distinguishes desktop, mobile, tablet, and other device types.

Browsers and Operating Systems

Normalized browser and operating-system families are stored without keeping the full User-Agent string.

Traffic Sources

Traffic is classified into direct, organic search, social, internal, referral, and other bounded channels.

Humans and Bots

Regular browser traffic can be analyzed separately from automated requests.

Referral Domains

External referrals can expose a normalized source domain without storing the complete referring URL.

Country is resolved at the infrastructure boundary

ICanUp does not send an IP address to an external GeoIP service on every page view and does not store raw IP addresses in analytics history.

Country resolution happens at a trusted infrastructure boundary. Laravel receives only a normalized two-letter country code.

A browser cannot simply provide its own trusted country value because the infrastructure creates or overwrites that internal header.

Analytics stores stable values such as UA, US, or DE, while localized country names are resolved at presentation time.

Traffic sources became more useful

Direct

This includes views without a reliably detected external source, such as direct visits, bookmarks, or applications that do not provide referrer information.

Search and Social

Known search engines and social platforms are normalized into stable sources instead of arbitrary raw values.

External Referrals

External websites are identified separately, while only a privacy-safe normalized domain is stored.

UTM Context

When controlled campaign parameters are present, analytics can use them to understand the traffic source and medium.

Bots no longer have to be mixed with the real audience

A significant part of public web traffic can come from search crawlers, link-preview services, automated scanners, AI crawlers, and other technical clients rather than people.

ICanUp began separating human and bot-classified traffic so large totals would not create a misleading picture of the actual reading audience.

Bot traffic also gained a bounded crawler-family dimension for supported search crawlers, preview bots, known AI crawler families, and safe fallback categories.

The full raw User-Agent does not need to be stored as an analytics value.

Analytics gained an hourly time dimension

Hourly Activity

New analytics data includes bounded hourly aggregates so activity can be examined by hour as well as by day.

Visitor Local Time

When a privacy-safe client UTC offset is available, views can be grouped by the visitor local hour.

ICanUp Reporting Time

The same activity can also be viewed in the canonical ICanUp reporting timezone.

Honest Data Coverage

When a dimension was introduced later or is unavailable for part of the history, the interface exposes that coverage instead of hiding it.

Country is intentionally not treated as a timezone. This matters especially for countries such as the United States, where one country spans multiple time zones.

Visitor local hour is calculated only when a privacy-safe time signal is available for that view, while reporting hour is tracked separately in the canonical ICanUp reporting timezone.

This makes it possible to answer two different questions: when readers are active in their own local time, and when that activity happens relative to ICanUp reporting time.

By September 2, 2026, ICanUp analytics had grown from basic view measurement into a much deeper audience, traffic, bot, referral, and time-analysis system without abandoning the principle of data minimization.