Les segments sont-ils rétroactifs ?
Segment retroactivity in Matomo depends fundamentally on your installation type and processing configuration, with significant implications for historical data analysis and reporting accuracy. Understanding these mechanics is crucial for maintaining consistent analytics workflows and avoiding data interpretation errors.
In Matomo On-Premise installations, segments can operate in two distinct modes. Real-time segments calculate results dynamically each time you access a report, processing raw visit data against your segment criteria. These segments are inherently retroactive, meaning they automatically include all historical data that matches your conditions from the moment tracking began. However, real-time processing comes with performance trade-offs, particularly for complex segments or large datasets, as each report request triggers comprehensive database queries.
Pre-processed segments, conversely, calculate and store results during the archiving process, dramatically improving report loading speed but sacrificing automatic retroactivity. When you create or modify a pre-processed segment, it only begins capturing data from that point forward unless you explicitly trigger retroactive processing.
Matomo Cloud installations exclusively use pre-processed segments to maintain consistent performance across their shared infrastructure. This architectural decision means new segments won’t display historical data without manual intervention.
To apply pre-processed segments retroactively, you must invalidate existing archived reports for your desired date range and re-run the archiving process. Execute ./console core:invalidate-report-data followed by ./console core:archive with appropriate date parameters. For example, to retroactively apply a segment from January 2024: ./console core:invalidate-report-data --dates=2024-01-01,2024-12-31 --sites=1
Performance Warning: Retroactive segment processing can be extremely resource-intensive and time-consuming, particularly for high-traffic websites with extensive historical data. Plan these operations during low-traffic periods and ensure adequate server resources. Large-scale retroactive processing may require several hours or even days to complete, during which time affected reports may display inconsistent data.
Enterprise environments should establish segment governance policies that include testing new segments on limited date ranges before full deployment, documenting processing requirements, and scheduling retroactive updates during maintenance windows to minimize business impact.
Have some questions ? We have your solution