Review Revenue Hub
Review confirmed purchases, sales trends, campaign usage, and complete CSV reports.
Distinct workspaces
Financial summary cards belong to Overview only. Analysis shows trends and purchase drivers; Campaigns shows code usage and attribution; Customers shows purchaser portfolios; Orders & Data shows the verified order ledger and source checks. These tabs open directly into useful details, without decorative introductory panels or repeated Overview cards.
All tabs share one verified report for the selected time frame. Changing tabs does not restart syncing. Refresh, a changed time frame, source-change notifications, returning to the page, and the visible-page 60-second backup can verify fresh data. Independent reads run together where safe; warnings that are not needed for final outcomes are not loaded. Refresh rotates clockwise until Up to date. Errors stop motion and show Sync error. The completion time records the successful saved-source check, not live broker freshness.
Net Revenue is verified sales after discounts, before payouts and other costs—not Gross Profit. Total customers displays new / existing (total), with each identified purchaser counted once. New means their first retained confirmed purchase falls in the selected period. Monetary figures show USD with $; unverified totals remain N/ A, never invented zero payments.
Confirmed sales is the paid sales amount after recorded discounts, before payouts and operating costs. Recorded discounts shows the amount given on the selected period's confirmed orders. Below it, Sales before discounts = Confirmed sales + Recorded discounts adds those discounts back. This is a recorded gross-sales comparison, not profit or a forecast that customers would have purchased without discounts. If any confirmed order lacks a discount amount, the discount card and sales-before-discounts total display N/ A rather than a partial total. Known discount subtotals remain traceable in source details and CSV; Word shows the same complete-total limitation.
All Hub source changes are subscribed to; sources without published real-time notifications remain covered by the complete 60-second visible-page backup and checks on return or connection restoration. The source-read badge does not guarantee broker freshness or complete history. Missing metric values display N/ A rather than invented zeros.
The canonical page is /admin/revenue-hub. Older revenue-intelligence bookmarks redirect here. Guide and export names use the Hub name.
Before you start
Sign in as an administrator. Open Analytics Hub, between Overview and Landing Page, then choose Revenue Hub. The shared admin header remains visible when you scroll. This page only reads records; it does not approve payments.
Confirmed payments only
A checkout receipt or order-received email is not proof that money arrived. All sales figures, order counts, purchasing-customer counts, discounts, charts, calendar counts, and rankings include only orders recorded as Approved, Paid, or Created, with a valid positive USD amount. Approved means an administrator confirmed payment, Paid means a verified provider confirmed payment, and Created means the paid purchase reached account delivery. Pending, Rejected, unknown states, and invalid or zero amounts do not contribute.
The date filter uses the order-placement date, not the date money arrived. Historical orders do not have a reliable payment-received timestamp. This is a confirmed-purchase sales report, not a cash-flow, refund, profit, or bank-reconciliation report.
Beside Recorded discounts, Total payouts sums finalized funded-account and affiliate payments in the selected Day, Week, Month, or Year using their recorded paid dates in Myanmar time. Funded payments use actual paid USD, including recorded fee refunds; affiliate payments use the recorded paid withdrawal amount. Pending requests are excluded. Net remaining revenue below it is confirmed sales minus total payouts, and can be negative. This is not profit: operating costs, fees, taxes, and other refunds are not deducted. Missing paid amounts or undated finalized payments make the totals unavailable instead of estimating them. The Word report includes these totals and their calculation basis.
Steps
The section tabs appear above the date selector.
The heading follows your selected tab, such as Revenue Hub / Analysis. New customers made their first recorded confirmed purchase in the selected period; Existing customers first purchased before it. Total customers is New + Existing, counting each identified person once even if they buy repeatedly. Latest confirmed purchase opens the latest confirmed purchase date in retained history. Day, Week, Month, and Year keep that chosen date rather than jumping back to today. Empty periods remain empty; the shortcut does not create transactions. The rounded sync badge uses green for a current verified read, yellow for pending/offline, and red for an error. On phones, Refresh and Download appear side by side.
Analysis now includes buying cadence: observed intervals ending at confirmed purchases in the selected period, including the preceding confirmed purchase in retained history. Each buyer has equal weight in the summary averages. Expand anonymous buyer details for model and size repetition and retry counts. Missing prior purchases do not become zero-day intervals, and imported or deleted history cannot prove lifetime buying frequency. Business review opportunities propose tests based on observed counts; they do not prove intent, campaign causality or future sales. The Word report includes cadence, sample counts and the same review proposals.
The calendar places Week1, Week2, and subsequent row totals after Sunday. Each total includes only the displayed month's dates in that Monday–Sunday row; boundary rows and unfinished weeks are marked Partial. Weekly order and revenue totals add up to the calendar month. Weekly customers are unique within each row, not added from daily customer counts. Hover or focus a day for an animated preview of confirmed orders and revenue. It includes component purchases and money, customer types, order types, models, sizes, and saved add-on names. Expand Models, sizes and add-ons for details. Clicking a date opens that day's report and displays its details for touch users. Daily and monthly trend tables show Challenge, Addon, and Retry purchase counts and revenue between confirmed orders and total sales. Unallocated amounts remain explicit, not guessed.
Choose Day, Week, Month, or Year using the same date controls as Payout Hub. Weeks run Monday–Sunday; all dates use Myanmar time (Asia/Yangon). Year shows the twelve monthly order and revenue totals for that selected year. Month shows the selected month's calendar. Day and Week show the surrounding full month as context; its totals can differ from the selected-period summary. Switch the calendar between Orders and Revenue, or click a day to open its report. There is no separate calendar-month selector.
Use Campaigns to compare saved campaign names, discount codes, and referral codes. Names come from purchase-time records, so future purchased campaigns appear automatically. Missing historical names are marked unavailable. A campaign with no recorded purchases does not appear in the purchase ranking. These lists measure purchases, not views, clicks, conversion, or commission eligibility.
Use Analysis for models, account sizes, and platforms. The All, Challenges, Addon, and Retry switch separates paid components. The add-on view uses the saved purchase-time add-on prices; challenge or retry revenue is the paid total minus those prices. Invalid or missing component metadata remains Unallocated, never estimated. Challenge, retry, add-on, and unallocated amounts equal All revenue. An order containing add-ons appears in more than one category, so category order counts are not additive. Other campaign, code, and model rankings describe full-order revenue and may overlap.
Customers separates first confirmed purchases from repeat purchases using all available confirmed order history, not registrations. A customer's later purchase is an existing-customer order, even within the same period. A new purchaser who buys again remains one unique new purchaser. Missing identifiers are Unknown, not guessed. In Orders & Data, search the confirmed-order list and use its page buttons. Search affects that list only, not the period's summary figures or exports. Open each ranking's complete-value table for every entry.
Campaigns reviews saved campaigns and scheduled promotion codes: selected-period sales, exact-window orders and revenue, planned duration, elapsed duration, and average daily revenue. A completed three-day window with $3,000 recorded revenue has $1,000 average daily revenue. Running-window averages use elapsed fractional 24-hour days, capped at the scheduled end; selected-window averages use the overlap with the report period. Revenue is not profit: verified costs and refunds are unavailable. Schedules are current admin settings, not archived run versions or proof of actual active days. Changed schedules, pauses, and missing dates cannot establish historical campaign duration; unavailable values remain explicit.
Check accuracy and export
Open Orders & Data for excluded-status counts and missing amounts, customer identifiers, add-on data, and legacy pricing metadata. Older confirmed orders remain included when modern pricing metadata is absent. Recorded discounts sum known discount amounts only; missing values are not estimated.
Order and trading-account change notifications trigger a complete report check after a short debounce. A backup check runs 60 seconds after each completed check while the page is visible; other sources, such as campaign settings, use this backup. Returning to the page or reconnecting triggers another check. Refresh immediately reloads every section for the current dates. Last updated is the last successful source read, not guaranteed bank-arrival time. Complete order history and campaign/code settings are read twice and compared. Incomplete, duplicate, or changing sources stop the report instead of showing partial totals. This is not a locked database snapshot.
Both downloads fetch a fresh, verified report using the selected dates; later payments may make it newer than the screen. Filenames use Revenue Hub, the period, and the included start and end dates. Download → Download CSV includes every returned field, total, daily value, ranking, confirmed order across every page, coverage warning, and definition. Paths such as report.totals.salesCents use integer USD cents; divide cents by 100 for dollars. Average-order cents are sales divided by paid-order count; an empty cohort has no average. Missing values remain null. Review accuracy and disclosure permission before sharing order information.
What success looks like
Download → Download Report creates a professional Word document from the fresh selected-period report without choosing dates again. It includes summary, selected-period trends, customer cohorts, product components, campaign performance, rankings, every confirmed order, calendar context and data-quality limitations. The calendar's All tab shows order counts and revenue together; Orders and Revenue remain separate views. Keep reports internal: order details require appropriate disclosure permission.
Selected-period daily order and revenue sums equal the summary. Yearly monthly sums equal the selected year. Component money and customer-cohort money equal confirmed sales. A surrounding calendar month for Day or Week is context, not the selected-period total. Pending receipts never increase these totals.
Common mistakes
Do not treat an uploaded receipt as a confirmed payment, add overlapping rankings, or interpret order dates as payment-received dates. A missing source value is not zero.
What happens next
Review Orders & Data before using the CSV. Investigate payment evidence in Payment Verifications; this dashboard cannot confirm a bank transfer independently.
Related guides
The page has five tabs: Overview, Analysis, Campaigns, Customers, and Orders & Data. Analysis combines product views with model-and-size purchase patterns, offer order counts, unique identified buyers, retries, add-on orders, and buyer frequency. Customers includes expandable anonymous buyer records showing each model and size purchased repeatedly. Labels such as Buyer 001 apply only within that report and are not persistent user IDs. Equivalent numeric sizes are normalized; missing metadata is not a known preference. Purchase patterns describe observed purchases, not intent or conversion.
Recorded registrations are counted separately from purchasers using creation dates of retained member profiles with role user. Deleted profiles and historical role changes are unavailable; imported dates may not be original registration dates. This count does not change confirmed revenue. The source is read twice; failures or changing profiles stop the report instead of displaying zero registrations.
Year shows a twelve-month calendar grid with orders and revenue in each tile. Future months are unavailable. Hover or focus a tile for the component and customer breakdown; clicking an available month opens its daily calendar. Expand Exact monthly values for the table.
Use the single Download menu for CSV or Word. Word includes analytical findings, revenue-leading recorded campaigns and promotion codes, frequency, anonymous buyer and model-size detail, registrations, and all existing source sections. Rankings can overlap; unknown metadata stays explicit. Next to the Hub title, green Up to date means the latest verified read is within 60 seconds with no known pending changes, yellow means a check is pending, running, stale or offline, and red means a read or export failed. This does not independently prove a bank transfer or guarantee instant notification delivery.