Daily Revenue, Spend & ROAS (Financial Flow)
Interactive CanvasChronological revenue vs Meta ad spend and efficiency curve
Chronological Invoice & Unit Economics Table
Strict sum-first calculations · No ratio averaging| Date | Meta Spend (₹) | Leads | Cost / Demo (₹) | Rev / Demo (₹) | Booked | Sched | Attended | Att % of scheduled | ARPC (₹) | New Inv | New Conv | Conv % of attendees | Renewal Inv | Renewals | New Rev (₹) | Renewal Rev (₹) | Blank Inv | Blank Rev (₹) | ROAS | New ROAS |
|---|
Reactive Controls & Dimension Slicing
Select dimensions to slice, toggle cohort maturity window, and filter ad hierarchy.
Executive Cohort Outcomes Summary
Aggregated for selected window (Till date)Cohort ROAS Maturity Curve Over Time
Blended ROAS (new + renewal revenue ÷ spend) for the selected date range at each maturity window; click a node to switch the table to that window.
Cohort Performance Table
Granular breakdown of Meta Inflow campaigns vs Verified Metabase revenue
|
No campaigns match your search query
|
Cohort ROAS progression
Revenue return by lead-capture date and selected outcome window. Color intensity reflects performance maturity.
Campaign Meta diagnosis
Combined performance of the campaigns matching your filters with automated root-cause driver decomposition.
Where booking cost changed
Net Efficiency GainRed increases booking cost • Green reduces booking cost
| Funnel Metric | Performance Window | Comparison Window | Delta | Cost Impact |
|---|
Performance-Period Trend
Daily TrajectoryCorrelation analysis between Ad cost (CPM) and demo booking velocity
Meta Ads Manager data
Direct ad delivery metrics from the Graph API, sliceable by placement and device OS
Spend by Delivery Date
Meta reported spend per day in the selected range
Top Campaigns by Spend
Share of spend and cost per result
Spend by Delivery Country
Where Meta served the impressions — Meta's own country breakdown, not the campaign's target market
Device OS Delivery Comparison
Link CTR, landing-page rate and cost per result by device — from the Meta delivery feed
Acquisition detail
Grouped by Delivery date, Campaign ID
Device is where the ad impression was served. Meta-attributed demo counts can vary slightly by breakdown.
Campaign tagging
Every campaign's target market, course and channel lives here. What you save is what the whole dashboard reports — there is no spreadsheet behind it.
Needs tagging
Campaigns with spend but no market or course. These read as Unmapped everywhere until they are tagged — heaviest spender first.
| Campaign | Campaign ID | Spend | Last seen | Missing | Action |
|---|
Tagged campaigns
Click any cell to edit. Changes save as you leave the cell and apply to the dashboard immediately.
| Campaign | Campaign ID | Display name | Target market | Course | Channel | Aliases | Last change |
|---|
Try it
Type what a lead would arrive with and see exactly how the dashboard will label it, using the registry as it stands right now.
How a campaign gets its tags
The order the dashboard applies. Every field is decided on its own.
-
1
Source comes from the UTM first.
utm_source, else the Meta placement the ad ran on, elseutm_medium. Never guessed from the campaign name. -
2
The campaign is looked up here — by Campaign ID, then by name, then by any alias you have listed. Matching ignores case, spaces, hyphens and underscores.
-
3
Meta traffic (Facebook, Instagram, Audience Network, Messenger) takes its campaign name, market and course from this table.
-
4
Non-Meta traffic (Google, organic, referral, email…) keeps the campaign name exactly as the UTM carried it, and takes market and course only if you have mapped them here on purpose.
-
5
Anything missing reads as “Unmapped”. Never “Others”, never “NA”, never a guess. Unmapped rows still count in every total, so the numbers always add up to real spend.
A blank market and a market typed as “Others” are stored the same way — as not tagged.
Team access
Who can sign in, and what each person may do. Admin manages people and tags · editor edits tags · marketing views only.
| Username | Name | Role | Last sign-in | Actions |
|---|
Recent changes
Every edit, who made it and when.
| When | Who | Campaign | Field | From | To |
|---|
Operational Accounting Logic & Conversion Definitions:
• Booked = booking creation date; scheduled and attended = class date. Confirmed demo bookings only; cancelled, workshop, mock-demo and teacher-training classes excluded.
• Attendance Rate (Att. %) = attended ÷ scheduled. • New conversions = distinct New/Token paying families per day (draft and Token invoices count; invoices with no booking type are their own category — Blank — inside total inflow and ROAS but not New; void counts for nothing). Non-INR uses the stored INR amount, else amount × 78 ÷ conversion factor. • Conversion Rate (Conv. %) = distinct new conversions ÷ attended demos.
• Cost per demo booked = Meta ad spend ÷ internal demos booked. • Revenue per demo booked = New revenue ÷ internal demos booked. • ROAS = New revenue ÷ Meta spend.