Skip to main content

Glossary

General

TermDescription
PropertyA property is an entity the tracking engine is tracking. It is a website, app, or other digital property.
HitA hit is a single request to the tracking server. Hits are raw and yield no analytical value, after they're processed into events by the tracking pipeline, they can be used for analytics.
EventAn event is a single action that occurs on the property. Its relation to hit is 1-1. It is used to track the user's activity on the property.
UserA user is a person who visits the property. It is used to track the user's activity on the property.

Tracking pipeline

TermDescription
Proto-sessionA set of loosely connected Hits, that may in the future form one or more sessions. The hits are glued together by the identifiers (Client ID, SS).

Identifiers

Identifier typeGA4-compatible (measurement protocol)Matomo-compatible (matomo.php)
Client ID - the ID assigned by the tracking engine to each device/browser combination, persisted in a cookieclient_id, user_pseudo_id_id
User ID - the ID used in an internal user system, for example email, available after the login. The customer must manually set it as a tracking parameter, it's not automatically determined by the trackeruser_iduid
Session stamp (SS) - hash calculated on the backend, from the incoming request elements - IP, User Agent, etcnone, calculated on the backendnone, calculated on the backend
Client-assigned session ID (CASI) - the session id as explicitly set by the client in the tracking requestsession_idnone