Nuon Monitor
Nuon MarketingSub-account health, review capture and NFC activity across the estate
Loading...
Demo preview · fixed 30-day sample
Remembered on this device for 30 days. Never put the key in a URL. Disconnect forgets it here.
Executive brief
30-Day Activity & Conversion Velocity
Not in the clean set
An open finding, a failing source, or nothing collected yet.
No open findings
States configuration and collection only, and implies nothing about results.
What has just happened across the estate
The most recent webhook deliveries, newest first. Every row is one event a sub-account's own workflow reported; this is raw arrival, not a metric, so nothing here is a 30-day total. No contact is identified: the feed carries the account, the kind and the time only.
Every signal across all sub-accounts
Counts, not rates. A source that was never attempted is its own hatched band, never counted as a failure.
Sub-accounts by state
Command Center
Use each area to inspect the service, account, workflow, and measurement signals collected for the agency.
All sub-accounts
A dash means a signal was never attempted. "Unavailable" means it was attempted and failed -- neither is ever a zero. Select View details for the full picture.
| # | Client | Status | What needs attention | Last checked | Details |
|---|
Card-link visits over time
A visit means someone opened the card's link. It does not confirm a physical NFC tap or a completed review. Every day in the selected window is shown, including days with zero visits -- a day is never silently skipped. The chart and visit total use all tracked cards, including their history while paused. Card status counts describe the current setup.
Same data, as a table
| Day | Visits |
|---|
Cards needing a look
Deterministic checks against this account's own active cards, not a performance judgement.
Your cards
Select View details for a card's public link, destination, and full activity. Add or edit cards through the Worker-backed registry.
Add NFC card
Changes are account-scoped and saved through the authenticated Worker. A saved destination is configured; activation is confirmed only by a successful test visit.
| Card | Placement | Status | Visits in selected period | Last activity | Details |
|---|
Recorded review events, this account
Observed via workflow instrumentation. Lifetime totals and lifetime average rating are not available from this data source -- shown as "Unavailable", never as zero. A platform not listed below has not produced a review-received event for this account in the last 30 days; that does not confirm it is disconnected, only that nothing was observed. Counts may include a duplicate if the review-received workflow fires more than once for the same real review (for example, a retried delivery). Exact review counts require verified review identity. A delivery ID can suppress retries of one delivery, but cannot merge multiple workflow runs about the same review. Each count is scoped to one platform for one sub-account; it is never combined across accounts or across platforms.
This window is fixed at 30 days regardless of the period selector in the top bar -- reviews are not yet collected with a configurable window. This control is deliberately locked rather than left to silently do nothing.
| Platform | Event deliveries (30d) | Lifetime | Avg rating (30d) |
|---|
Workflow inventory by account
Published and total workflow counts come from the existing health summary. Execution and message outcome data require collector fields.
| Account | Total | Published | Runs (30d) | Errors |
|---|
Configuration signals
These values identify setup intent. They do not prove that a workflow executed or a card activated.
Message health
Delivery, DND, and error counts are shown only when message IDs and outcomes are collected.
Webhook coverage
Native GHL events and workflow webhooks use different authentication and identity contracts.
Coming Soon
The dashboard navigation is ready. Website status, indexability, schema, canonical URLs, GBP connection state, and profile freshness will be added after their read-only collectors and evidence definitions are approved.
Website health
Uptime, domain, SSL, forms, and published version.
Coming SoonSEO signals
Indexability, schema, canonical, robots, and sitemap checks.
Coming SoonGBP health
Connection, profile completeness, and review destination checks.
Coming SoonWhat needs a decision
Each item includes its account and evidence. This view does not send messages or change GHL settings.
What is instrumented, by sub-account
A dash means never attempted for this account; a mark means observed at least once. Neither implies performance.
| Sub-account | Workflows | Forms | Chat widget | NFC | Reviews |
|---|
What each column measures
- Workflows. Existence and published state only; no execution log exists, so a published workflow is never claimed to have run.
- Forms. Submissions and distinct contacts in the last 30 days.
- Chat widget. Whether one is configured, not whether anyone used it.
- NFC. At least one card registered for this account. Visits and taps are separate: see the NFC section.
- Reviews. At least one review event observed via workflow instrumentation. Never a lifetime total or a verified published-review count.
When each source last succeeded
Collection timestamps recorded by the collector itself. Stale labels require an explicit freshness deadline or stale flag from the collector; age alone does not imply failure.
healthyAll required sources have confirmed collection and no finding is open.needs_attentionA source failed to collect, or a non-critical finding is open.criticalA directly observed failure, such as a confirmed message send error.not_collectedNo source has been attempted for this sub-account yet. Never reported as healthy and never as failing.
What can be attributed
- NFC. Link visits can be attributed to a registered card key and sub-account when the redirect recorded it. A visit does not prove a physical tap, person, or review.
- Reviews. Workflow event deliveries can be scoped to a sub-account and platform. A distinct Google review or its source card remains unverified without a stable review identity.
- SMS and email. Delivery and error attribution requires message IDs from the server collector; the current summary does not expose them.
What the dashboard cannot prove
- A saved GHL custom value or custom field proves configuration only. It does not prove an NFC card was programmed or physically activated.
- A workflow definition proves setup or publication, not that every run or message succeeded.
- A dashboard refresh reloads stored summaries. It does not itself collect fresh GHL data.