Features
Data quality and health score
Know when tracking breaks, see which part broke and jump straight to the fix — before a campaign runs on bad data.
Tracking health
Example data: Static example state — not live traffic, no real customer data.Score
86 / 100
Components
- Consent coverage91 · 20% weight
91% of events carry an explicit consent signal
- Critical events78 · 25% weight
7 of 9 planned critical events observed
- Schema quality74 · 15% weight
74% of events pass schema and PII checks
- Duplicates96 · 10% weight
1.0% duplicates
- Delivery88 · 20% weight
94% delivered, 1 integration with credential problems
- Freshness100 · 10% weight
Last browser event 4 min ago
Open issues
- purchase without currencyFix: update the event mapping
12 events in the last 24 h are missing the required parameter
- Consent signal missingFix: connect the CMP adapter
9% of events arrived without an explicit consent state
Weighted components; a lower score always points at its cause.
Example score with its six components and two open issues, each naming the tool that fixes it.
Six components, one explainable score
The worker computes a tracking health score from consent coverage, critical event coverage, schema quality, duplicate rate, delivery success and freshness. Each detected issue names the assistant tool that resolves it.
The score is computed from the events of the last period: how many carry an explicit consent signal, which planned critical events were seen, how many pass schema and PII checks, the duplicate rate, the delivery success per destination and when the last browser event arrived. The weights are shown next to the score, so a lower number always points at its cause.
How it is built
The technical decisions behind the capability — the proof after the benefit.
01
Issues with fingerprints
Recurring problems are grouped, counted and timestamped so you see trends instead of noise.
02
Schema guardrails
Standard events have required parameters; custom events follow naming rules; PII in properties is blocked before storage.
03
Benchmarks only with opt-in
Anonymised, aggregated benchmarks are available only for organizations that opt in.
Noticing problems versus being told
How a broken purchase event surfaces with and without the health score.
| Noticing problems versus being told | Without monitoring | With the health score |
|---|---|---|
| Detection | Someone notices a dip in the ads dashboard days later | The score drops and an issue is opened |
| Diagnosis | Which tag, which page, which browser? | The component that dropped and the events behind it |
| Fix | Ticket, tag change, re-publish, wait | The issue names the assistant tool; you approve the change |
| Trend | No history | Grouped, counted and timestamped issues |
What you can verify
Product facts you will find in the dashboard, the docs and the audit log.
- Score per site with its components
- Resolve or ignore issues with an audit trail
- Consent coverage and duplicate rate as first-class metrics
Questions
- Is the score comparable across sites?
- The components are identical for every site; weights are documented in the score card so teams can reason about differences.
More capabilities
Built on the same signed configuration and event schema.
- AI-guided setup
Describe your site, confirm each step, publish a signed configuration.
- Server-side event router
One event, every platform: browser and server delivery with shared deduplication.
- Event debugger and lineage
See every event with its consent snapshot, routing decision and vendor response.
- Consent-aware by construction
Strict opt-in defaults, Consent Mode v2, purpose-based destinations, no replay after consent.
- Click ids and attribution done right
Capture only the ids the destination needs, only with consent, only for the documented window.
Try it on your domain
Create a site, install one snippet and let the assistant configure the first destination in minutes.