Skip to main content
Warning This document has not been updated for a while now. It may be out of date.
Last updated: 18 Mar 2021

content-data-api: ADR 009: Track metrics by basepath instead of by Content Item



We started tracking performance and quality metrics by content_id, but after the first 3 months it was clear that the user needs to track metrics at the base_path level in Guides and Travel Advice.


If a subpath in a Content Item changes, then there is no simple way to track the performance before/after the change. The data will be stored, but the Data Warehouse has no way to join both series of metrics.

Content Items with no subpages won't be affected because we store the content_id next to the base_path for each Item, so in case we have a base_path change will be able to track all metrics through time via the content_id and locale.


Track metrics at the base_path level