Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
See how SIRJ turns connected dashboard data into weekly insights, white-label reports, PDF exports, recommendations, and cited client-ready proof.
Buyer answers
SIRJ reporting has to explain the proof path, delivery path, export path, and missing-data path in language an agency can use with clients.
A SIRJ report is built from a report snapshot: date range, dashboard cards, source breakdowns, campaign rows, insights, recommendations, and client branding captured together.
The client can ask where a number came from, and the agency has the source path instead of a polished but fragile screenshot.
Follow the report proofWeekly delivery builds the current dashboard, compares the previous period when available, generates insights, sends configured recipients, and records delivery notifications.
The reporting workflow becomes scheduled operational proof, not a Friday scramble through ad platforms, CRM rows, and invoice exports.
Follow the report proofReport output should keep unsupported rows empty, mark attention items, recommend source verification, or explain when no campaign, source, or revenue data is available.
The report earns trust by naming gaps. It does not pretend every connected stack can answer every revenue question on day one.
Follow the report proofReport rendering uses client branding metadata for display name, logo, accent color, and footer notes, while keeping source metrics and recommendations tied to the frozen snapshot.
Agencies can present client-ready reports without breaking the evidence chain underneath the brand layer.
Follow the report proofReporting surfaces
The dashboard, weekly email, PDF export, and Ask Data answer should all describe the same source-backed reality instead of creating four different versions of the truth.
What users see
This is the difference between a reporting feature and a proof system: the visible report surface stays tied to the data path that produced it.
| Surface | User sees | Source path |
|---|---|---|
| Live dashboard | Current metrics, recent activity, readiness gaps, source health, cards, and Ask Data prompts in the workspace. | Dashboard generation reads normalized events, connected source capability, tenant scope, and date bounds. |
| Weekly insight email | A scheduled email with the week label, summary, attention items, anomalies, and a route back to the dashboard. | Weekly delivery builds current and previous dashboard configs, generates insights, sends recipients, and saves notification records. |
| PDF export | A branded report with summary metrics, source breakdown, campaign performance, top performer, attention items, and recommendations. | Report export creates a scoped snapshot, renders report HTML, sends it to the PDF renderer, and stores the result or failure. |
| Ask Data answer | A cited answer or unsupported response that names the computed row, date range, source context, and chart rows when available. | Ask Data validates the query spec, executes against dashboard fields, cites metrics, and refuses unsupported questions. |
Report workflow
Reports are strongest when the context is frozen, source rows remain visible, recommendations cite evidence, and delivery/export status is auditable.
| Step | What happens | User-visible proof |
|---|---|---|
| Freeze the reporting context | A report snapshot captures tenant scope, client scope, date range, generated timestamp, dashboard cards, extracted metrics, insights, and recommendations. | The exported report can be traced back to the same snapshot instead of changing every time a source syncs. |
| Extract source and campaign rows | Report rendering groups source spend and leads, lists campaign revenue, spend, leads, and ROAS, and preserves the difference between no data and poor performance. | The client sees source breakdown and campaign performance tables rather than one blended top-line claim. |
| Generate recommendations from evidence | Recommendations come from top campaign performance, attention items, and missing revenue-source conditions, with the supporting metrics attached. | The report can say whether to increase budget, review spend, or connect a revenue source without hiding the reason. |
| Deliver or export with auditability | Weekly delivery stores sent and failed notifications, while PDF export stores completed or failed export results and an audit log entry. | The account can distinguish a sent report, a failed delivery, a completed PDF, and the user who requested the export. |
| Keep unsupported claims out | When campaign rows, source breakdowns, recommendations, or attention items are unavailable, the report says so instead of filling space with confident filler prose. | Empty states and missing-data recommendations protect the agency from overclaiming in a client review. |
Proof standards
The highest-converting reporting page is not the one that promises magic. It is the one that shows how the product refuses to overclaim.
Report snapshots assert the same tenant and client scope before metrics, insights, exports, or history can be used.
Report output includes source breakdowns, campaign rows, attention items, and recommendations tied to available dashboard metrics.
Weekly delivery records notifications and anomaly alerts with status, recipient, subject, provider message id, and error state.
PDF exports create request/result records and an audit log with snapshot id, format, status, output reference, byte length, and error message.
FAQ
The FAQ is written for search and answer engines, but its real job is to resolve reporting objections before they reach the client review.
A report includes summary metrics, source breakdown, campaign performance, top performer context, attention items, recommendations, client branding, date range, and generation timestamp when the connected data supports those sections.
Yes. The export flow creates a scoped report snapshot, renders report HTML, sends it through the PDF renderer, stores the output reference, and records failed export attempts instead of hiding them.
Yes. Weekly delivery checks the schedule, builds the dashboard for the active tenant and client, generates insights, sends configured recipients, and records sent or failed notifications.
The report should recommend connecting or verifying a revenue source before making budget decisions, because spend without attributed revenue is a setup gap or an operational signal.
Ready when the numbers need to hold up
Start in the live demo, then trace the report path through data lineage and integration detail pages.