Telemetry Engine

Stable

Applies to: SmartBlocks telemetry and reporting pipelines

Introduced: v1 telemetry core

Updated: Documentation v1

Telemetry Engine ingests machine-facing and optimization signals, normalizes them, and powers visibility dashboards, trend cards, and campaign evidence.

Summary

The engine is the shared data foundation for agent analytics, readiness comparisons, and recommendation confidence scoring.

Use cases

Track crawler and answer-engine activity
Measure signal changes after fixes
Support campaign compare and reporting

How it works

Collectors gather events, transformers normalize fields, and aggregators publish scoped metrics for admin pages and API surfaces.

Inputs

Request/crawler metadata
Content/readiness snapshots
Integration data (for example GSC-linked signals)

Outputs

Daily and rolling-window metrics
Agent and page-level trend datasets
Evidence fields consumed by recommendations

Admin UI location

SmartBlocks telemetry dashboards and compare views in WordPress admin.

Agent Intelligence features are built directly on Telemetry Engine outputs.

Significant telemetry-driven apply operations are correlated in Visibility Ledger.

Security

Use least-data logging and keep private fields redacted; access to telemetry controls is capability-restricted.