ICanUp Introduced Its Own Privacy-First Analytics

As ICanUp grew, it became important to understand more than how many times a single post had been opened. The project needed a broader view of how the public site was being used.

Instead of simply adding another external counter, ICanUp gained its own analytics system built as a product subsystem.

It covered Home, Categories, Posts, and Pages while storing historical data independently from the application cache.

The analytics subsystem was designed to avoid turning content measurement into personal visitor profiling.

View deduplication uses a privacy-safe contract that does not require permanent storage of raw IP addresses.

ICanUp therefore distinguishes total views from deduplicated views, without presenting the latter as a true count of unique people.

This provides useful measurements while avoiding unnecessary visitor profiles.

Historical analytics data is stored in the database and acts as the source of truth.

Cache is used only to improve read performance and summaries. Clearing it does not remove or alter historical metrics.

Writes are also designed to avoid losing increments when multiple views are recorded concurrently.

The collected data gained a dedicated presentation layer in Admin.

Analytics can be filtered by period, locale, page type, or specific content, with historical trends, top content, and breakdowns available from one section.

The main Admin Dashboard also gained a lightweight summary so important changes are visible without opening the full analytics area.

On August 21, 2026, first-party analytics became a full part of ICanUp.

From this point on, content development could be evaluated using historical data while preserving the principle of collecting only the visitor information that was actually needed.