PowerAdvice/Internal operating dashboard

Stateful reporting / internal use

What changed. What proves it. What happens next.Operating dashboard

Each control reads the current immutable snapshot. A new validated snapshot can replace the manifest pointer; this page then refreshes without changing its presentation code.

Loading state…

Sponsor export view

Scope. This print view is generated from the same locked snapshot as the internal dashboard. It does not create a sponsor portal or claim unavailable delivery outcomes.

01 / Operating decision

Start with the period, evidence, and next action — not a data catalog.

Loading period state…

Current comparison

Loading snapshot…

No decision can be drawn until source state loads.

Needs attention

Three evidence-bound follow-ups.

Ranked by selected-period change; no materiality threshold is invented.

02 / Audience model

The 26 May meeting split the job into three distinct views.

Distribution Reach, Reader Engagement, and Preservation Equity remain separate. The dashboard never converts pageviews into readers or attention events into commercial outcomes.

Attention rule.Loading source definition…

02A / Audience trend

Make growth legible across the on-site reporting window.

Source: GA4 on-site activity, not people or revenue. The selected Day, Week, or Month rollup will appear here with its metric meaning and date range.

Audience metric

Loading selected rollup…

Loading audience trend…
Interpretation. GA4 on-site activity is descriptive. It is not people or revenue, and observed movement does not imply causation.

03 / Campaign reporting lanes

Every source gets its own lane, state, and limit.

Internal sponsor operations can inspect available source receipts. Sponsors receive a dated PDF derived from this same snapshot — never live dashboard access.

Rendered-placement boundary. GA4 ad_viewable and ad_click are rendered-placement telemetry. They are not impressions, delivery, billing, revenue, fulfilment, or certified viewability.

03A / Partnership telemetry trend

Read returned event rows by lane and period.

Source: campaign_telemetry, separate GA4 rendered-placement event telemetry. This source is stale through 2026-08-27; observed rows start 2026-08-04.

Telemetry lane
Returned event

Loading returned telemetry…

Loading campaign telemetry trend…
Partner / campaign source state; returned event total is for the selected event
GroupReturned event totalObserved date rangeDelivery-mode stateFixed non-proof
Returned-row boundary. This surface shows returned ad_viewable, ad_click, and session_start event counts only. Missing dates have no returned row and must not be synthesized as zero. These counts do not prove impressions, delivery, commercial performance, billing, revenue, fulfilment, viewability, or sponsor outcome.

05 / Sources and refresh

The dashboard shows the source that created each number.

“Reload state” re-reads the current manifest. New information becomes visible only after a validated immutable snapshot is published and the manifest pointer advances.

Update function. scripts/publish_snapshot.py turns refreshed source exports into an immutable snapshot, validates required data, then atomically advances reporting-data/manifest.json. A failed source remains unavailable or stale; it is never replaced with zero.

Meeting-based visibility

One state, different internal use cases.

Each section is available only for its stated internal purpose. The sponsor PDF is a limited dated render, not another data system.

SectionWho sees itUse case

Historical reference

Context stays visible without becoming current performance.

Legacy Advisorpedia and the Calamos publication cohort are isolated reference lanes. They are not added to today’s PowerAdvice results.

Advisorpedia legacy GA4 reference

Property 355871891 is historical methodology context only. It does not populate current PowerAdvice totals or comparisons.

Calamos archive

Loading historical archive state…