Product-defined business outcomes
Prepare a daily count of the event the client cares about, such as confirmed orders or completed bookings. Supabase does not supply a universal definition for those custom measures.
Supabase + Monthwrap
Databases & warehouses reporting
Supabase reporting for agencies.
Use a prepared query on a client’s Supabase database to turn confirmed orders, bookings or other dated results into clearly defined monthly report metrics.
AvailableSession pooler connection and saved query
Inside the monthly reportSample data
Daybreak Goods
Confirmed orders from the client’s system
Confirmed orders156Total across the four example days
Reporting days4A short format example
Highest daily count48October 4 in this example
Query resultsMonthly report
| Record | Reported numbers |
|---|---|
| 2026-10-01 | 30 |
| 2026-10-02 | 36 |
| 2026-10-03 | 42 |
| 2026-10-04 | 48 |
The four daily counts total 156 confirmed orders. “Confirmed” is an example business definition, not a built-in Supabase metric.
Supabase, at a glance.
- Connect with
- Session pooler connection and saved queryUses the IPv4 Session pooler and read-only database credentials, not a service_role API key. Connect the project, preview a dated numeric query and save it for the client.
- Updates
- Daily sync, with a manual refresh in Sources. Platform reporting delays still apply.
- Earlier months
- Run the saved reporting query for an earlier month, using the history retained in your database.
- In your report
- Custom numbers from the client’s Supabase Postgres data.
Built around your client’s questions
A custom product needs reporting that respects its definitions.
Agencies serving custom ecommerce and product-led businesses
The client’s application may record an order, booking or activation in Supabase before that result appears anywhere else. A prepared reporting query can turn those records into a daily measure the client recognises. Agree what counts and which date applies before bringing the figure into a marketing report.
Monthwrap’s Supabase route uses the project’s PostgreSQL connection to read that numeric output. Connect through the Session pooler, preview the prepared query and save it on the client’s source. After syncing and checking the results, use those custom metrics alongside the client’s marketing sources.
Choose the numbers that matter
What Supabase
brings to the report.
Custom numbers from the client’s Supabase Postgres data. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.
Agreed numeric values
Return an order-value or booking-value column when the client has defined its meaning. Label gross, net, booked or paid amounts accurately rather than treating every stored value as revenue.
Dates that match the business question
Choose the relevant date in the query, such as confirmation or completion. A result can change when the date basis changes, so document that choice in the report.
Metrics alongside the acquisition story
Use the prepared totals in their own section beside advertising or website activity. A query result can describe business performance without establishing which channel caused each order.
For your next client report
Report a custom commerce journey
Bring confirmed-order totals from the client’s own application into the monthly review. Explain the status definition and keep it separate from ad-platform conversion counts.
Arrange the report in your own layoutRead it from the client’s side
See the complete
ecommerce report.
A full fictional agency report, with the work delivered, the numbers behind it and the plan for next month. Use its structure to plan your own mix of sources and client results.
Open the sample reportMake the connection
From Supabase
to the right client.
Uses the IPv4 Session pooler and read-only database credentials, not a service_role API key. Connect the project, preview a dated numeric query and save it for the client.
Connection methodSession pooler connection and saved queryAvailabilityAvailableYour connected account’s API permissions and plan apply.
- 01
Get the Session pooler details
Ask the project administrator for the IPv4-compatible Session pooler connection string from Supabase’s Connect view and the database password. This route does not use a service_role or REST API key.
- 02
Prepare restricted reporting access
Have the administrator provide a dedicated read-only database role with access to the required reporting data. Keep the application’s broader administrative credentials out of the reporting setup.
- 03
Connect, preview and save
An owner or admin connects the project in the workspace. Preview one SELECT or WITH query returning a date and numeric columns, resolve any format problems and save it for the appropriate client source before syncing.
Know what each
number means.
A database connection, not every Supabase service
This route reads prepared PostgreSQL query results. It does not report automatically on Auth users, Storage files, Edge Functions or every application table, and it does not modify the client’s product.
The query must produce reportable numbers
Customer names, product lists and arbitrary text rows are outside the current contract. Prepare dated numeric aggregates, use start and end dates, and avoid counting the same business event twice.
Before you connect
A few useful
answers.
Can I connect with the Supabase service_role key?
No. This route uses the database through the Session pooler connection string and database credentials. Ask the project administrator for suitable read-only access rather than substituting an application REST credential.
What does the query preview check?
It runs the query for the selected dates and shows sample rows, metric names and format problems without saving or importing the results. Reconcile a known period, save the checked query on the client source and then sync the numbers you want to report.
Does the integration discover my business metrics automatically?
No. Your agency and the data owner prepare one read-only query with a date first and numeric columns after it. The output becomes custom metrics; the query’s definitions determine what each reported number means.
Start with your next client report
The data has a source.
The story has your name.
Bring your sources together, choose your layout and add the context your client needs.
Start free trial14-day free trial. No card needed.