Confirmed operational counts
Count the events that match the client’s definition, such as jobs with a completed status. Keep requested, booked, canceled and completed events distinct in the query and report labels.
Databases & warehouses reporting
Use a saved read-only query to bring dated numeric results from MySQL or MariaDB into Monthwrap, with definitions your agency and client agree on.
| Record | Reported numbers |
|---|---|
| 2026-10-01 | 12 jobs |
| 2026-10-02 | 15 jobs |
| 2026-10-03 | 11 jobs |
| 2026-10-04 | 18 jobs |
The example query counts completed jobs. It does not import individual job records or attribute those jobs to a marketing channel.
Built around your client’s questions
For agencies reporting on custom applications, booking systems and client databases.
A custom application may hold the client’s most useful results: completed jobs, attended consultations or approved orders. Those definitions often depend on internal status fields that an advertising platform cannot see. A saved database query lets your agency use the agreed business result without turning the report into a copy of the application.
Monthwrap’s MySQL route also supports MariaDB. Connect the database, preview a query returning a date and named numeric columns, then save it on the client’s source. After syncing, those columns become custom report measures. Check a known period before placing the results beside marketing activity and the work your agency delivered.
Choose the numbers that matter
Dated operational totals from MySQL or MariaDB. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.
Count the events that match the client’s definition, such as jobs with a completed status. Keep requested, booked, canceled and completed events distinct in the query and report labels.
Return an agreed amount for each day and configure the metric’s money settings. Explain whether it represents orders, invoices or collected payments instead of applying a generic revenue label.
A query can return multiple numeric columns after the date. Use readable column names so the resulting report measures communicate their meaning without exposing internal database terminology.
Use the supplied start and end dates to select the intended period. Return daily results at a suitable scale; repeated rows for the same day are added, so accidental joins can inflate totals.
For your next client report
Report completed jobs from the operational database beside calls and inquiries from other sources. The comparison helps explain follow-up without claiming that every completed job came from a recent campaign.
Arrange the report in your own layoutRead it from the client’s side
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
Connect with read-only database credentials, preview a query returning dates and numbers, then save it on the client’s reporting source.
Ask the database owner for a dedicated read-only account limited to the required tables or views. Use encrypted transport and a reporting endpoint that can be reached from Monthwrap; private-network hosts are not supported.
An owner or admin enters the host, port, database and reporting credentials in the workspace. The database administrator should restrict network access to the connection address shown there, rather than open the database broadly.
Return the day first and numeric columns after it. Test a known period, resolve reported problems and save the query on the correct client source before syncing its numbers.
This route supplies dated measures. It does not import contact records, arbitrary text columns or a complete operational database, and it does not currently provide a second query for a ranked text-and-number table.
The connection accepts one read query, with a 30-second limit and at most 5,000 returned rows. Aggregate close to the source and validate joins so the result is both manageable and correct.
Before you connect
Yes. The MySQL database route also supports MariaDB. Use the client’s approved reporting credentials and verify a representative query, rather than assuming every database-specific expression behaves identically.
Use a dedicated read-only database account. The connector accepts a single read query and uses a read-only transaction, but database permissions should still limit the account to the reporting data it needs.
The current route refuses private-network hosts. Ask the database owner whether an appropriately restricted, externally reachable reporting endpoint is available; do not expose the operational database broadly just to enable reporting.
Start with your next client report
Bring your sources together, choose your layout and add the context your client needs.
Start free trial14-day free trial. No card needed.