BeeScope
Revenue Observability Dashboard
Every rupee, every source, every page. Nothing hidden.
Most publishers find out what they earned once a month, as a single number from a partner who will not show the working. BeeScope is one ledger for every BeeOS module and your existing ad accounts — with gross, fee and net on the same screen, and an alert when something moves before you find out at month end.
Revenue ledger · last 30 days
hindinews.example · 5 sources, one table
| Source | Gross | Fee | Net |
|---|---|---|---|
| BeeBid · display | ₹3,12,400 | −₹18,744 | ₹2,93,656 |
| BeeFresh · refresh | ₹84,100 | −₹5,046 | ₹79,054 |
| BeePlay · video | ₹46,800 | −₹2,808 | ₹43,992 |
| BeeLink · affiliate | ₹22,600 | −₹1,130 | ₹21,470 |
| BeeWall · readers | ₹13,040 | −₹652 | ₹12,388 |
| Total | ₹4,78,940 | −₹28,380 | ₹4,50,560 |
Gross, fee and net on every row. Most partners show you the last column only.
BeeScope
now
BeeBid RPM −18% on mobile
Since 2pm. Likely cause: SSP timeout rate up 4×.
significance-tested
before it ever sends
The problem
What this is costing you right now
Five reporting tabs that never agree
AdSense, Ad Manager, the native widget, push, affiliate — five dashboards, five timezones, five definitions of a day.
"Revenue dropped 30%" — and no way to find out why
The number moved.
A statement with one number on it
Managed-inventory partners report net and call it revenue.
How it works
What BeeScope actually does
No black box. Here is the whole mechanism, step by step.
BeeScope — how it works
-
1
Every module streams into one pipeline
BeeBid bids, BeeFresh depths, BeeLink commissions, BeeWall payments, BeeMail issues — all of it lands in the same event pipeline instead of five separate reporting systems.
-
2
One ledger normalises the mess
Currencies, timezones and each source's idea of when a day starts are reconciled into a single ledger, then checked daily against the partner reports with discrepancies flagged rather than smoothed over.
-
3
Drill down until the number explains itself
Site, then revenue source, then page, then ad unit, then device and geo. The point is to reach the row that moved, not to admire a total.
-
4
Anomalies find you, not the other way round
Every metric carries a rolling baseline. A deviation that passes a significance check raises an alert on WhatsApp with a plain-language probable cause — "BeeBid RPM down 18% on mobile since 2pm, SSP timeout rate up" — inside hours, not at month end.
-
5
A statement you could hand to your accountant
A monthly PDF per site showing gross, fees and net, with the payment date and enough detail to raise an invoice against. Full history kept, exportable any time.
- Gross, fee and net all three, always
- Page-level drill-down to the row that moved
- Alerts in hours WhatsApp-first
- Export any time your data, no lock-in
In context
Where BeeScope sits on your page
Every ad slot on the page reports into the same ledger — plus your affiliate links, reader payments and newsletter issues.
BeeScope does not change anything on the page. It is the layer that tells you what each of these actually earned, and which one moved when the total did.
Specifications
Full technical specification
Publishers compare specifications, not adjectives. Everything is here, including what depends on partners we do not control.
The ledger
| Sources unified | Every BeeOS module, plus AdSense and Google Ad Manager imported by API where you connect them. Modular by design — the ledger works with whichever modules you actually run, and shows the gaps rather than hiding them. |
|---|---|
| Gross-first accounting |
Gross → fee → net, all three visible on every screen and every statement. This is a structural commitment, not a display preference. Reporting net and calling it revenue is the standard trick in this industry and it is exactly why publishers do not trust their partners.
|
| Formatting |
INR-first with lakh and crore formatting, because ₹4.82L is how Indian publishers actually talk about a month. Multi-currency sources are converted at the rate on the day, with the raw figure retained.
|
| Reconciliation | Daily comparison against each partner's own reporting, with discrepancy flags when they disagree beyond a threshold. A silent gap between your dashboard and your payment is the worst kind of surprise. |
Drill-down & export
| Drill-down | Site → revenue source → page or article → ad unit → device and geo, with period-over-period comparison at every level. |
|---|---|
| Export |
CSV export of any view, any time, including full history. You own your data is one of the five company principles and this is where it becomes concrete.
|
Alerts & statements
| Anomaly detection |
Rolling 7 and 28 day baselines per metric, with significance testing before anything alerts. Alert fatigue kills alerting — a channel that cries wolf gets muted and then misses the real one.
|
|---|---|
| Alerts | WhatsApp-first, email fallback, with a plain-language probable-cause note rather than a raw metric dump. Quiet hours per timezone. |
| Statements | Monthly PDF per site: gross, fees, net, payment date, invoice-ready. Full history retained and downloadable. |
Some capabilities depend on third-party approvals and platform policies that are not ours to promise. Where that is the case, the spec above says so explicitly.
Expected impact
What the industry reports
Every number below is an industry benchmark published by a third party. BeeOS has not shipped, so none of these are results we have produced.
Revenue lines visible on every screen — including what we take
This is the commitment the rest of the product rests on. A partner who will not show you gross has already told you something.
Without BeeOS
- Reporting tabs to reconcile
- 5
- Gross revenue visible
- No
- Fee visible
- No
- Time to notice a 30% drop
- Weeks
- Can you export and leave
- Ask your account manager
With BeeOS
- Reporting tabs to reconcile
- 1
- Gross revenue visible
- Always
- Fee visible
- Always
- Time to notice a 30% drop
- Hours
- Can you export and leave
- One click
Expected difference
5 tabs → 1 ledger
No percentage on this one on purpose. Observability does not raise revenue; it tells you the truth about it early enough to act, and lets you check whether the arrangement is fair.
3 of 3
Gross, fee and net shown on every screen
A structural commitment. Most partners show you one of the three.
Hours
Time to notice a revenue anomaly, instead of weeks
Baseline deviation with a probable cause, on WhatsApp.
Any time
Full CSV export, including history
If you leave, you take everything. No notice period.
Being straight with you: This product has no uplift percentage and we are not going to invent one. A dashboard does not raise your RPM — BeeBid and BeeFloor do that. What BeeScope changes is how quickly you find out something is wrong and whether you can tell how you are actually being treated. Both of those compound, and neither reduces to a number we could footnote honestly.
Works with
Fits into the stack you already run
Platforms BeeOS integrates with — not customers, partners or endorsements.
- Google AdSense
- Google Ad Manager
- AdX (via partner)
- Prebid.js
- Amazon APS
- PubMatic
- Magnite
- Index Exchange
- Sharethrough
- Sovrn
Glyphs are generic shapes, not brand logos — these are platforms we integrate with, not endorsers.
Questions
BeeScope — frequently asked
Module 4 · Data & Intelligence
The rest of the module
Modules 1 to 3 make money. Module 4 makes it visible, defensible and worth more — one honest ledger, first-party audience data, content-level intelligence, traffic-quality protection, and the curated demand that all of it unlocks.
BeeData
First-Party Audience Kit
Know your reader. Earn like you know them.
BeeIntel
Content Revenue Intelligence
Know which article paid the rent.
BeeGuard
Traffic Quality Shield
One bad traffic spike can end your account. We watch so it does not.
BeeCurate
Curated Deals Engine
Alone you are small. Curated, you are premium.
Be first in line for BeeScope
BeeScope is under active development. Early-access publishers get priority onboarding, founder-level support on WhatsApp, and locked-in launch pricing.
No spam — we write only when something real ships.