The operational problem
Agency reporting was fragmented across platform dashboards and point-in-time exports, making trend comparison, connection health, evidence review, and repeatable client reporting harder to operate.
Que Media's internal analytics and reporting system for durable client, account, post, audience, and reporting history.
Why this system exists
Durable history makes changes inspectable across clients and platforms. A single operating surface lets the team see portfolio health, investigate the evidence behind a movement, repair collection gaps, and prepare consistent reports.
QUE Signal organizes the agency, clients, authorized owned accounts, daily and post snapshots, content, actions, and frozen reports. Collectors normalize only metrics each platform actually supplies and preserve explicit gaps or unavailable values.
How the work moves
- Connect an authorized account
- Collect account and post history
- Store source-qualified snapshots
- Compare clients and periods
- Surface gaps and repair work
- Generate a deterministic report
- Review before delivery
What shaped the solution
Official platform data requires owner-authorized OAuth credentials and platform verification.
The local portfolio runtime uses synthetic data and stubbed collector checks, not private client analytics.
A shared operator password exists, but individual user accounts and production deployment were not verified.
What I owned
Designed
Agency, client, owned-account, campaign, post, reporting-period, and provenance model
Developed
Agency dashboard, client workspaces, growth and content views, account health, report library, PDF output, and responsive shell
Integrated
Meta, YouTube, and TikTok OAuth and collectors with retry, token, rate-limit, backfill, and gap-handling paths
Tested
Collector fixtures, token failures, historical backfills, data gaps, report determinism, frozen output, content ranking, and sentiment
Operated
Migration, worker, repair queue, sync health, and data-quality workflows
Decisions that carried the work
Preserve history with provenance
Snapshots retain account, platform, date, source, raw payload, and availability so comparisons do not turn missing data into zero.
Freeze delivered reports
Generated reports store deterministic computed output so a later data sync cannot silently rewrite what a client received.
Make repair work visible
Connection failures, reporting risk, and data gaps become an ordered decision queue instead of disappearing inside background jobs.
Verified outcome
Built agency and client workspaces for portfolio health, historical growth, content performance, account state, and reporting.
Implemented fixture-tested Meta, YouTube, and TikTok collectors plus deterministic frozen reports and data-quality checks.
Verified the complete local system against an isolated PostgreSQL database with synthetic clients and 90 days of history.
What I will not overclaim
The repository and local runtime are verified. Portfolio captures contain synthetic data only; no OAuth tokens, private client metrics, recipients, reports, or raw payloads are published. Production hosting, live cross-platform credentials, predictive analytics, autonomous strategy, and universal metric availability are not claimed.
Verified from Ayub's QUE Signal repository, authored commit history, local PostgreSQL runtime, synthetic capture state, and passing self-check suite on September 3, 2026.