Yametrika3x

Package Description

The new Yametrika3x component integrates full Yandex Metrica analytics into the MODX 3 admin panel. No more switching between browser tabs — all key metrics are available right where you manage your site. Built on hywax/ya-metrika — a PHP client for working with the Yandex Metrica API. What the component does Yametrika3x loads data from Yandex Metrica on a schedule and stores it in its own database tables. This provides instant access to statistics without waiting for a response from the external API every time you open a page. The component provides eleven analytics sections: • Overview — summary KPI cards (today vs. yesterday) and an interactive traffic chart • Traffic — detailed daily table: visits, page views, unique visitors; weekends are color-highlighted • Pages — top site pages by views for the selected period with URL search • Search Engines — sources of organic traffic with the share of each search engine • Search Phrases — queries that bring visitors to the site • Geography — audience distribution by country and region • Browsers — browser statistics with percentage breakdown • Gender and Age — demographic profile of the audience • Synchronization — log of all data loads, manual triggering, loading for an arbitrary period • Settings — managing the token, counter, and data storage parameters • Documentation — built-in help directly within the component interface Data is filtered by period: today, 7 days, 30 days, quarter, year — or a custom range. Technical stack • hywax/ya-metrika — PHP client for working with the Yandex Metrica API • HTMX — partial page updates without reloading, lazy loading of tabs on click • UIKit 3 (scoped) — UI components are isolated from MODX styles, with no conflicts with ExtJS • SVG — bar charts are rendered natively, without Chart.js or similar libraries • xPDO ORM — all database queries go through the MODX object model, with no raw SQL • Cron — three synchronization modes: hourly (data for today/yesterday), daily (7 days), weekly (deep history) Data is stored on a "one row per day" basis — this allows for correct filtering by any period and accurate pagination.