LayarrSignal Control Plane
Local shellFixture data only
Secondary analytics surface

Trends explain signal health after the cockpit confirms operations.

These graphs are intentionally secondary: they help an operator understand fixture event volume, consent decisions, delivery reliability, duplicate suppression, and signal quality without pretending to show sales or audience-performance KPIs.

Local demo fixtures only — illustrative operator states, not customer KPI data.

Demo trend window5 local fixture points · no customer claims · no sales, order-value, audience-growth, or retention reporting.source=typed_fixture.analyticsTrends
Event volume
216Fixture events received across this demo window.
Consent blocked
20Events held by policy before destination fan-out.
Delivery attention
18Retries plus failed/held attempts requiring operator review.
Signal quality
93%16 duplicate attempts suppressed in fixture trends.
Event volume

Received signals over time

fixture counts

Volume is shown only as local signal pressure, supporting the control-plane narrative instead of claiming customer growth.

10:00
36
11:00
42
12:00
49
13:00
57
14:00
32
Consent allow/block

Allowed / partial / blocked

allowed partial blocked

Consent decisions stay visible before route fan-out so blocked marketing does not disappear into averages.

10:00
28/5/3
11:00
31/7/4
12:00
36/8/5
13:00
42/9/6
14:00
24/6/2
Displayed as allowed / partial / blocked fixture counts.
Destination delivery

Success / retry / failure

success retry failure

Destination delivery reliability is graphed as operational proof, with retry/failure states preserved for investigation.

10:00
30/1/1
11:00
34/2/2
12:00
39/2/2
13:00
47/3/3
14:00
27/1/1
Fixture delivery attempts only; not platform performance claims.
Duplicate detection

Suppressed duplicate attempts

operator signal

Duplicate detection shows tracking-stack hygiene: repeated browser/theme events are suppressed before they distort downstream tools.

10:00
2
11:00
3
12:00
4
13:00
5
14:00
2
Retry pressure

Retries stay actionable

not hidden

Retry counts explain where operators should inspect credentials, policy lanes, and destination receipts.

10:00
1
11:00
2
12:00
2
13:00
3
14:00
1
Signal quality

Quality score trend

proof-backed

The quality line is a fixture diagnostic score based on complete IDs, consent evidence, delivery receipts, duplicate suppression, and retry pressure.

10:00
91%
11:00
88%
12:00
90%
13:00
87%
14:00
93%