Skip to main content

Web Analytics

Open Journal -> Web Analytics to review cabinet visits, audience characteristics, page speed, forms and errors. Web analytics permission is required.

Filters​

FieldPurpose
ProjectAll available projects or one project.
ServerAll servers or one server belonging to the selected project.
PeriodA preset, calendar year or custom dates. Defaults to the last 30 days.
From / ThroughFirst and last included days. Report dates and hours use UTC.
GroupingAutomatic, daily, weekly, monthly or yearly. Changes chart intervals, not the selected period.
Page pathAn exact path such as /en/, without the domain, query parameters or fragment after #. Leave empty for all pages.

Apply changes with the filter button. The address and section navigation preserve the selection. Reset restores the initial filters. Long periods may use larger intervals to keep charts readable.

Overview​

MeasureMeaning
Page viewsRecorded page openings. Revisiting a page adds another view.
VisitorsDistinct visitors identified by browser data, not registered player count.
SessionsSeparate visits to the site. One visitor can have multiple sessions.
Single-page sessionsShare of sessions with one page view in the selection. This is not a quality score.
Average time on pageAverage recorded page-visit duration.
Average active timeAverage activity time on a visible page.
Average scroll depthHow far visitors scrolled on pages with activity measurements.
Pages with activity measurementsPage visits for which activity measurements were received.

Below the cards are visit and single-page-session charts, 50 popular pages, and views by hour and weekday. Distinct visitors and sessions for the whole period are not the sum of daily unique counts.

Cards, charts and tables share the selected period.

Audience​

Compare referring pages, campaign sources, mediums and names. Separate tables show devices, browsers, operating systems, countries, languages, appearance themes and touchscreens. An unspecified value means that observation did not contain the corresponding information.

Each audience characteristic has its own page-view and visitor counts.

Speed​

MetricMeaning
LCPTime until the largest visible element appears, in milliseconds.
CLSLayout shifts during loading. A score, not a duration or percentage.
INPResponse time to an interaction, in milliseconds. It may be unavailable without a qualifying interaction.
TTFBTime to the first response byte, in milliseconds.

Cards show the 75th percentile: 75% of recorded values are at or below it. Tables also show the median and sample count; charts compare intervals. Individual pages have separate results for each metric.

Not measured does not mean zero delay. A recorded zero, such as CLS without shifts, remains zero. Not every browser or visit provides all metrics. Use Web Vitals to compare player LCP with subsequent payments.

LCP, CLS, INP and TTFB have independent values, sample counts and charts.

Interactions​

The table lists clicks on page elements and repeated-click sequences. Frequent repeats can help identify an unresponsive or confusing element, but do not prove an error. Outbound navigation has a separate table.

Compare elements by page, clicks and repeated clicks.

To see click distribution, select an exact page path and apply the filter. The diagram shows relative click positions, not a page screenshot. If the page has changed, compare the selected period with its relevant layout.

The selected /en/ path excludes clicks on other pages.

Forms​

Each form shows starts, submissions, abandonments and average time to submission. Submission does not confirm that the operation succeeded: validation may still fail. The field table compares completed fields and time spent on them. Entered values are not displayed in the report.

Forms and individual fields have separate activity and duration measures.

Diagnostics​

Script errors are grouped by kind, source, line and column, with occurrence and affected-page counts. Slow resources are grouped by kind and address, with sample count and 75th-percentile duration. These are website errors and loads, not game-server errors.

Separate tables help locate a problem and determine how often it occurs.

Actions​

This section lists named actions connected in the site's design: action name, page, occurrences and visitors. Entries appear as visitors use those elements.

Actions are measured separately from page views and form submissions.

One server​

Select a project and server, then apply. The server remains selected when moving from Overview to Speed, for example. Choose all servers or reset filters to return to the overall picture.

The overview is limited to the selected project and server.

Empty results and errors​

An empty table means there are no observations for the selection. Check dates, server and page path. Missing speed measurements are shown separately from numeric zero.

There are no measurements in the selected historical period; missing values are not replaced with zeros.

If loading fails, retry with the filter button. Shorten a very large period or choose one project. Data can arrive with a delay; browser blocking also affects report completeness.