What Jurnr measures.

A random ID created when Jurnr starts.Used to group events from the same visit; it is not a device or advertising identifier.

Milliseconds since the app started.Collected from the browser’s monotonic performance timer.

When the browser created the event and when Jurnr’s server stored it.Useful for ordering events and diagnosing delayed delivery.

Records that Jurnr finished loading.Includes article, source, saved, and reacted counts plus theme, sort mode, viewport class, and whether the app is running standalone.

Summarizes a completed visit.Includes duration, last page, deepest feed scroll, and totals for previews opened, reactions, saves, and full-article opens.

Records movement between Jurnr’s main screens.The page name is collected when the in-app navigation changes.

Records opening filters, sorting, account, or similar panels.The stable panel ID is stored; time spent in a panel is not inferred.

Records use of the floating up-arrow.Stores the current page and scroll position at the moment it is pressed.

Shows which articles were meaningfully visible.An impression is counted once per session after at least half of an article card enters the viewport. Events are sent in batches of up to 25 and include source, feed position, sort mode, and filter mode.

Records the selected reaction or source filters.Includes the resulting number of visible articles, making it possible to identify useful or empty filter states.

Records the selected sort order.Includes result count and the first article after sorting so the reorder can be validated.

Measures use of source-directory search.Recorded after a 500 ms pause. Jurnr stores query length and result count—not the search text.

Records opening or leaving the Saved screen.Includes whether the view became visible and the current saved-item count.

Records opening an in-app preview.Includes source, feed position, article age, page, sort and filters, plus whether it was already saved or reacted to.

Describes a preview session from open to close.Includes duration, maximum scroll depth, whether 90% was reached, and whether the user reacted, changed Saved state, or opened the source article.

Records closing the reading preview.Collected when the close control, browser history, or in-app navigation returns to the feed.

Records following the publisher link.Stores the article ID, source, and destination URL at click time.

A source-level rollup signal.Labels the interaction as opened, rated, saved, or full article opened so engagement can be compared by source.

Records adding, changing, or removing an article reaction.Stores article ID and emoji; custom reaction labels are included when present.

Identifies reaction changes made inside Reading view.Distinguishes additions, updates, and removals from feed-card gestures.

Records opening the reaction interface.Helps distinguish discovering the control from completing a reaction.

Records changes to Saved state.Stores article ID and source. The article snapshot itself remains in account settings for Saved view.

Records reaction-wheel edits.Includes resized wheel size or the slot and emoji changed.

Records the start of a refresh.The reason is identified as manualstartupscheduled or source_added.

Records refresh outcomes.Success includes duration, checked and loaded totals, and added or removed article counts. Failure includes duration and reason.

Describes the complete feed assembled for the app.Includes item and page counts, changes since the previous load, and whether loading happened at startup or during refresh.

Records changes to connected and enabled RSS sources.Includes source name and relevant item counts. Custom-feed setup may also include the submitted feed URL.

Records the selected light or dark appearance.

Records opening this reference page.Includes the analytics schema version shown by the app.

Records requesting the account’s JSON export.

Records requesting the Android package.Includes the advertised application version and build code.