-
Introduction
- Understanding Matomo
-
Matomo Core development
- Contributing to Matomo Core
- Contributing to Matomo Plugins
- Coding Standards
- Using GitHub Issues
- Pull Requests and Reviews
- The Core Team Workflow
- Maintaining Plugins
- Maintaining Translations
- Matomo APIs
- Debugging Core
- Profiling Code
- Reproducing Issues
- FAQs
- Core Components
- Composer dependencies
- Release Management
- Using GitHub Actions
- Matomo's Roadmap
- Matomo Plugin development
- Web Interface
- Utils
- Reporting API
- Data Model
- Tests
- Tools
-
Plugin Development
Log data
This documentation is for an outdated Matomo version.
Click here if you want to read this article for the latest version.
Click here if you want to read this article for the latest version.
Log data
The HTTP tracking API (i.e. the Piwik\Tracker component) receives raw analytics data, which we call log data.
There are five types of log data:
- visits
- action types
- plugin specific actions
- conversions
- ecommerce items
Log data is aggregated by the Archiving process into archive data.
Log data is never used directly for Matomo (formerly Piwik) reports, archive data is used instead. The only exception is the Live plugin which uses log data to generate real-time reports.
Persistence
Log data is represented in PHP as Piwik\Tracker\Visit objects, and is stored into the following tables:
log_visitcontains one entry per visit (returning visitor)log_actioncontains all the type of actions possible on the website (e.g. unique URLs, page titles, download URLsâ¦)log_link_visit_actioncontains one entry per action of a visitor (page view, â¦)log_conversioncontains conversions (actions that match goals) that happen during a visitlog_conversion_itemcontains e-commerce conversion items
The content of those tables (and their related PHP entities) is explained in more details in the Database schema guide.