Analytics Extension Points

This page covers analytics at the integration level only. Internal table names, column definitions, AJAX/REST endpoints, hook names and aggregation queries are implementation details and are not published here.

What analytics does

The plugin records aggregated, anonymous usage signals for the vehicle catalogue (such as listing views, basic interaction counters) to support dealership-side reporting from the plugin's own admin dashboard.

Integration guidance

Reporting is exposed through the plugin's admin UI. Storage layout, collection endpoints, rate limits and the exact set of signals captured are internal implementation details that may change between releases. External code should not read from the plugin's analytics storage or call the plugin's analytics endpoints directly.

If you need to feed plugin analytics into an external BI tool, request a supported export channel rather than querying internal storage.

Supported public integration surfaces

When integrating with the plugin, prefer these stable surfaces:

• The plugin admin settings UI.
• The documented shortcodes.
• Theme-level template overrides as described in Template System And Overrides.
• The general Developer Overview for orientation.

Internal class names, option keys, database tables, REST and AJAX endpoints, cron hook names, capability and nonce identifiers, and release / update infrastructure are treated as implementation details. They may change between releases without notice and are not part of the public integration contract.

Stability and change policy

Anything not listed as a supported public surface above is considered an internal implementation detail. Internal APIs, storage layout and security implementation may change between releases. Do not depend on them from third-party code, themes or external systems. Direct database writes are not supported.

Public documentation notice. This page provides a high-level integration overview only. Internal implementation details, private APIs, storage internals and security-sensitive release infrastructure are maintained separately and are not part of the public documentation. Supported integration surfaces are the documented shortcodes, template overrides, settings UI and any extension points explicitly published in this section.