Overview

Traffic, attribution, portfolio health, and operations — top to bottom by priority.

Status: operationalWindow: StoredCharts: ≤500 newest
01

Executive Summary

Headline KPIs, platform health verdicts, and automated narrative.

Events last hour
Partial
0
In last hour (newest-500 sample)
Captured events
Healthy
2,972
Total events in visibility store
Active pixels
Partial
0
No active pixels in sample
Attribution rate
Critical
—
Click and UTM signals not yet present in sample
Top source
Partial
—
No source data yet
Top country
Partial
—
No geo data yet

Operations

Delivery, recovery, and platform health — secondary to traffic analytics above.

Platform health
Partial
Partial
Partial visibility or incomplete coverage
Export acknowledgement
Warning
Not configured
Production worker: export_lineage storage is intentionally disabled (Phase 965). Full export acknowledgement validation runs on the staging worker. Tail logs and export summary remain authoritative for production transmission checks.
Recovery health
Warning
Backlog
100 events awaiting recovery
Platform insights
Automated summaries of traffic, tracking, and delivery health.
caution

Events are being accepted but the current activity window is empty.

caution

Some events require delivery recovery — platform remains operational.

caution

Destination delivery tracking is not enabled.

02

Traffic & Attribution

Volume, trend, attribution, campaigns, geo, devices, and coverage.

Traffic

Idle—
Recent 30m: 0 (0.0/min)Prior 30m: 0 (0.0/min)Δ +0
Source movement
utm_source / channel label change between 30-minute halves

No source labels in the last hour.

Campaign movement
utm_campaign volume change between halves

No campaign tags in the last hour.

Region movement
Region or country volume change between halves

No geo region signals in the last hour.

Quality vs traffic
Idle
No events to compare signal quality across halves.

Geo prior half

—

Geo recent half

—

Campaign prior half

—

Campaign recent half

—

Traffic timeline
Events per minute — last 60 minutes. No traffic recorded in the last 60 minutes.

Live refresh enabled

No events in the last hour. Traffic will appear here as tracking activity arrives.

Attribution

Traffic sources
Commercial and organic channel mix from enriched events — paid, email, affiliate, referral, and direct traffic.

No enriched attribution data yet. Sources appear as geo, campaign, and click signals arrive from live traffic.

Channel rankings
Last hour
Direct, paid, organic, email, and referral channels from stored signals

No channel classification in the last hour.

UTM signal frequency
Most common campaign attribution fields in the hour window

No UTM signals in the last hour.

Click signal frequency
Platform click-id presence via clickAttributionLabel

No click attribution labels in the last hour.

Missing attribution signals
Inventoried signals with zero population last hour
utm_source—0
utm_medium—0
utm_campaign—0
utm_content—0
utm_term—0
utm_source_first—0
utm_campaign_first—0
referrer_domain—0
First vs last touch transitions
Last hour
Channel shifts among events with persisted first-touch source or campaign signals

Comparable events

0

Channel mismatch

—

First-touch retention

—

Commercial last-touch

—

No first-touch source or campaign tags in the last hour — transition matrix requires utm_source_first or utm_campaign_first on stored events.

Campaign attribution dominance
utm_campaign volume with click-id co-occurrence

No utm_campaign tags in the last hour.

Attribution quality trend
idle
No events to compare attribution quality across halves.

Attributable prior half

—

Attributable recent half

—

Click prior half

—

Click recent half

—

Campaigns

Top campaigns
Campaign leaderboard by event volume — utm_campaign from enriched traffic only.

No campaign tags in the current window. Campaign names appear when UTM parameters are captured on incoming events.

UTM medium
Events by utm_medium

No utm_medium values in the current window.

UTM content
Events by utm_content

No utm_content values in the current window.

UTM term
Events by utm_term

No utm_term values in the current window.

First-touch source
Events by utm_source_first (session landing)

No first-touch source values persisted yet.

First-touch campaign
Events by utm_campaign_first

No first-touch campaign values persisted yet.

Geo

Geography
Country distribution from enriched events with geo signals.

No country data in the current window. Geo appears when worker-enriched events are recorded.

Region
Events by Cloudflare region

No region signals in the current window.

City
Events by Cloudflare city

No city signals in the current window.

Timezone
Events by IANA timezone from request.cf

No timezone signals in the current window.

Devices

Device traffic rankings
Marketing device labels ranked by event volume

No device labels in stored visibility rows.

Device attribution rankings
Devices ranked by attributable event count

No attributable events with device enrichment.

Device family rankings
Strongest and weakest family buckets by traffic share

No device family signals in stored rows.

Attribution quality by device
Not enough device groups to compare attribution quality.

Need at least two device groups with enrichment to compare attribution quality.

Mobile / desktop mix
Share of traffic by device class.

No device classification data in the current window.

Device model distribution
Marketing device names from enriched traffic.

Device model labels appear when worker-enriched events arrive.

Browser distribution
Browser family and version from User-Agent classification.

Browser signals not yet present in stored events.

Operating system distribution
OS family and version from User-Agent classification.

OS signals not yet present in stored events.

Campaign by device
utm_campaign paired with marketing device model.

Requires campaign tags and device enrichment on the same events.

Campaign by browser
utm_campaign paired with browser version.

Requires campaign tags and browser enrichment on the same events.

Campaign by OS
utm_campaign paired with operating system version.

Requires campaign tags and OS enrichment on the same events.

Source by device
Traffic source label paired with device model — e.g. Google Ads → iPhone 16.

Requires source or click attribution plus device enrichment.

Coverage & reconciliation

Geo coverage
Poor
—
0 events with country · All stored events
Region coverage
Poor
—
0 events with region · All stored events
City coverage
Poor
—
0 events with city · All stored events
Timezone coverage
Poor
—
0 events with timezone · All stored events
Source coverage
Poor
—
0 events with utm_source · All stored events
Medium coverage
Poor
—
0 events with utm_medium · All stored events
Campaign coverage
Poor
—
0 events with utm_campaign · All stored events
Content coverage
Poor
—
0 events with utm_content · All stored events
Term coverage
Poor
—
0 events with utm_term · All stored events
First-touch source
Poor
—
0 events with utm_source_first · All stored events
First-touch campaign
Poor
—
0 events with utm_campaign_first · All stored events
Click attribution
Poor
—
0 events with click IDs · All stored events
Device coverage
Poor
—
0 events with device type · All stored events
Device model coverage
Poor
—
0 events with marketing model · All stored events
Browser version coverage
Poor
—
0 events with browser version · All stored events
OS version coverage
Poor
—
0 events with OS version · All stored events
Signal quality by window
Country, region, city, timezone, device, campaign depth (source/medium/content/term), first-touch, and click attribution coverage.

Last hour

No events in last hour.

Last 24 hours

No events in last 24 hours.

Last 7 days

No events in last 7 days.

All stored events

No events in all stored events.

Accepted events
97
Lifetime ingest counter (non-duplicate)
Stored events
2,972
event_visibility.count · query sample ≤ 500
Delta (accepted − stored)
Unbounded store
-2,875
0 rows in API snapshot
Event lifecycle counter provenance
Scope durable · visibility d1 · metrics do
MetricValueKindSourceStorageWindowRetention
Accepted events97LifecycleGET /debug/state → metrics.ingest_acceptedMetricsDO durable counters (metrics_source: do | local fallback)Lifetime cumulative since MetricsDO / isolate initializationPersists in MetricsDO storage until reset or redeploy without binding
Stored events2,972StorageGET /debug/state → event_visibility.countD1 event_visibility table (or in-memory fallback when D1 unbound)Point-in-time row cardinalityUnbounded row growth in event_visibility (phase 871); dashboard queries use cursor pagination with per-request limits
Queued events0Queue depthGET /debug/state → queue + retryQueueIn-memory queue buffers (primary + retry)Current depth snapshot (not cumulative)Ephemeral — drained by processor; not a lifetime total
Replayed events0LifecycleGET /debug/state → metrics.dlq_replayedMetricsDO durable countersLifetime cumulative recoveriesPersists in MetricsDO until reset
Exported events0LifecycleExport outbox summary by_delivery_status.delivered (metrics.collector_delivered fallback)D1 export_outbox / lineage tables when enabledLifetime delivered count in export storeExport lineage retention per outbox policy; metrics fallback is lifetime
Failed events100LifecycleGET /debug/state → failed + dlq + metrics.collector_failedProcessor stats (failed) + DLQ depth (dlq) + export failuresProcessor failed/processed lifetime + current DLQ depth + export failed totalDLQ entries persist until replay or purge; processor counters lifetime
Supporting ingest counters
Additional lifecycle context not shown as primary KPIs

Ingest received

0

Duplicates rejected

0

Queue processed

0

Export pending

0

Attribution recovery context
Attribution coverage is ~0.2% because 92% of production stored events are demo/dashboard telemetry without campaign capture inputs — geo enrichment (11.7%) proves worker-side enrichment works independently of UTMs.

Stored window events

0

Demo / internal share

0%

Campaign in window

0%

Production D1 campaign

1 / 462

Recovery plan

PriorityActionRationale
highSeparate demo/internal telemetry from customer attribution KPIsProduction D1 is ~92% px_demo_* and dashboard routes without campaign query params — not a pipeline failure.
highAdd click-id parity to app/public/pixel.jsDashboard and demo traffic use pixel.js which captures UTMs but not fbp/fbc/gclid/fbclid — SDK-only today.
mediumAdd automatic UTM capture to customer SDK page eventsSDK captures click IDs but not URL UTMs unless customer passes properties — gaps vs pixel.js.
mediumRoute real marketing landings through tagged URLs before dashboard SPA navigationFirst-touch and session UTMs require an initial landing with query params; in-app routes never carry UTMs.
lowExpose utm_medium/content/term and first-touch in coverage KPIsPersisted in D1 but not in executive coverage audit — visibility gap only.
Signal capture completeness
27 high-value signals inventoried — 7 export-complete, 19 export-partial, 5 documented capture gaps, 6 captured-but-not-surfaced in dashboard.

Signals inventoried

27

Export complete

7

Visibility complete

16

Documented gaps

5

SignalCategoryCaptureVisibilityExportExplorer
Meta browser ID (fbp)Attributioncustomer_sdkPresence onlyCompletepartial
Meta click cookie (fbc)Attributioncustomer_sdkPresence onlyCompletepartial
Meta click ID (fbclid)Attributioncustomer_sdkPresence onlyCompletepartial
Google click ID (gclid)Attributioncustomer_sdkPresence onlyCompletepartial
Microsoft click ID (msclkid)Attributioncustomer_sdkPresence onlyPartialpartial
TikTok click ID (ttclid)Attributioncustomer_sdkPresence onlyCompletepartial
TikTok cookie (ttp)Attributioncustomer_sdkPresence onlyCompletepartial
Reddit click ID (rdt_cid)Attributioncustomer_sdkPresence onlyCompletepartial
UTM sourceCampaignpixel_js, customer_sdkCompletePartialcomplete
UTM mediumCampaignpixel_js, customer_sdkCompletePartialgap
UTM campaignCampaignpixel_js, customer_sdkCompletePartialcomplete
UTM contentCampaignpixel_js, customer_sdkCompletePartialgap
UTM termCampaignpixel_js, customer_sdkCompletePartialgap
Device typeDeviceworkerCompletePartialcomplete
Device familyDeviceworkerCompletePartialcomplete
Device modelDeviceworkerCompletePartialcomplete
Browser familyBrowserworkerCompletePartialcomplete
Browser versionBrowserworkerCompletePartialcomplete
OS familyOSworkerCompletePartialcomplete
OS versionOSworkerCompletePartialcomplete
CountryGeoworkerCompletePartialcomplete
RegionGeoworkerCompletePartialgap
CityGeoworkerCompletePartialgap
TimezoneGeoworkerCompletePartialgap
Client IPTransportworkerN/APartialnot_applicable
User-AgentTransportworkerN/APartialnot_applicable
Accept-LanguageTransportworkerN/AGapnot_applicable
03

Pixel Portfolio Health

Demo portfolio (DEMO_PIXEL_IDS) · activity and charts from ≤500 newest sample — not the full pixel universe.

Multi pixel portfolio
Demonstration pixels with real activity from the durable visibility window.
PixelRecent eventsHealthLast seen
Demo Landing

px_demo_landing

0Unknown—
Demo Storefront

px_demo_storefront

0Unknown—
Demo Checkout

px_demo_checkout

0Unknown—
Demo Support

px_demo_support

0Unknown—
Most active pixel
No evidence yet

Navigate dashboard routes to generate real multi-pixel activity.

Least active pixel
No evidence yet

Navigate dashboard routes to generate real multi-pixel activity.

Newest active pixel
No evidence yet

Navigate dashboard routes to generate real multi-pixel activity.

Activity by pixel
Recent event counts in the durable visibility window — real evidence only.

No demo pixel activity in the visibility window yet. Navigate dashboard routes to generate real telemetry.

Health by pixel
4 demo pixels · validation-derived health in current window
Pixel health distribution
0 repository pixels · validation on persisted registry only · excludes visibility-only pixels

No pixel health buckets yet — persist pixels and emit events to populate distribution.

Top active pixels
Ranked by event count in durable visibility window · canary: Dashboard Internal Pixel

No persisted pixels yet.

04

Operational Status

Event flow, delivery recovery, destination health, and worker signals.

Operations dashboard
Real-time traffic flow, recovery queue, and destination export health.
Last updated: —

System status

Warning

Events received

0

Events accepted

97

Active pixels

0

Recovery queue

1,000

Destinations

disabled

Live tracking · px_dashboard_internal

Dashboard monitor — Dashboard Internal Pixel

QuietUnknownlast seen —0 recent

Event flow

Received

0

Accepted

97

Accepted (pending)

0

Processed

0

Failed

0

Accepted (pending) counts visibility rows still in accepted status — ingest accepted but not yet processed. Processed counts visibility rows in delivered status.

Recovery summary

Open recovery

Awaiting retry

100

Recoveries

0

Candidates

100

Destination summary

Open destinations

Export ack'd

0

Export failed

0

Export pending

0

Mode: disabled

Production worker: export_lineage storage is intentionally disabled (Phase 965). Full export acknowledgement validation runs on the staging worker. Tail logs and export summary remain authoritative for production transmission checks.

Worker health
Operational signals from existing debug surfaces

Worker reachable

Yes

/debug/state responded with authorized token

Metrics available

Yes

MetricsDO or local metrics source present

Ring visibility

Yes

recent_events ring has entries on this isolate

Ingest active

Yes

ingest_accepted counter is greater than zero

Event type distribution
Counts from durable visibility window — real ingested events only

No event types in the visibility store yet. pixel.js emits page_view, button_click, link_click, form_submit, and dashboard_view via existing ingest.

05

Recent Activity

Live event stream from the current visibility window.

Recent activity
Property-first activity from durable events, replay, and export — source: durable. New events since refresh are highlighted.