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.
Preview a SIRJ client report with snapshot metrics, source breakdown, campaign rows, attention items, recommendations, and source-backed report lineage.
Snapshot header
Google Ads and call tracking show the clearest path from spend to booked revenue. Revenue proof is strongest where campaign, call, job, invoice, and payment evidence all exist.
Metric preview
These sample cards show the type of metrics a report can surface when the connected stack supports the claim.
Revenue counted from matched job, invoice, and payment evidence inside the report period.
Spend -> call lead -> booked job -> invoice -> payment
Review metric proofSpend imported from ad platforms and scoped to the active client workspace and report window.
Google Ads and Meta Ads campaign spend rows
Review metric proofAttributed revenue divided by ad spend when both revenue and spend evidence are available.
Attributed revenue from matched payment evidence divided by scoped ad spend rows
Review metric proofJobs matched from operations or CRM records after lead source and contact evidence are validated.
Call or form lead -> job or opportunity record
Review metric proofSource breakdown
A useful report explains whether a source supplied spend, calls, booked work, invoices, payments, or follow-up context.
| Source | Spend | Activity | Revenue | Report role |
|---|---|---|---|---|
| Google Ads | $9,840 | 118 | $61,300 | Primary paid search source. Campaign rows can show which queries and groups produced the most invoice-backed revenue. |
| CallRail | Source context | 96 calls | $49,700 | Phone-lead bridge. Call source, answered status, tracking number, and duration help explain why spend became booked work. |
| Jobber | Operations source | 42 jobs | $72,880 | Booked-work proof. Jobs, quotes, invoices, and service details turn lead reporting into operational revenue evidence. |
| Stripe | Payment source | 36 payments | $58,940 | Collected-revenue proof. Payment status and refund context keep collected revenue separate from projected deal value. |
Campaign performance
Budget guidance should explain the reason, the support level, and the next setup step when revenue evidence is missing.
| Campaign | Spend | Leads | Revenue | ROAS | Recommendation |
|---|---|---|---|---|---|
| Emergency AC repair | $3,420 | 41 | $28,700 | 8.39x | Increase budget only if CallRail and Jobber continue to show answered calls becoming completed jobs. |
| Furnace tune-up | $2,160 | 33 | $9,840 | 4.56x | Keep spend stable, then review booking follow-up and invoice completion before making a larger budget change from this campaign. |
| Duct cleaning | $1,290 | 18 | $0 | Unsupported | Do not judge ROAS until booking, invoice, or payment evidence is connected for this campaign. |
Attention items
Missing or delayed evidence should become a next step, not a hidden flaw in the revenue story.
Duct cleaning has spend and leads but no connected booked-work or payment evidence in this sample period.
Verify job source mapping and revenue-source sync before making a budget decision from this row or presenting it as underperforming.
Inspect the causeSeveral booked jobs have invoices but no collected payment event yet, so collected revenue is lower than booked revenue.
Use payment-source sync status before treating the gap as client performance decline.
Inspect the causeUncontacted call leads can turn campaign performance into an operations problem rather than an ad problem.
Use Ask Data or messaging integration evidence before reallocating campaign budget.
Inspect the causeProof sections
This is the report anatomy a buyer can evaluate before trusting a client-ready export.
| Section | User sees | Source path |
|---|---|---|
| Snapshot header | Client name, report date range, generated timestamp, summary, and report context. | Report snapshot records tenant scope, client scope, date range, generated timestamp, branding, metrics, insights, and recommendations. |
| Metric cards | Attributed revenue, spend, ROAS, booked jobs, leads, and source-supported performance changes. | Dashboard cards and extracted report metrics share the same source-backed calculation layer. |
| Source breakdown | Rows for ad, call, job, invoice, and payment systems with the role each source plays in the revenue claim. | Integration records, normalized events, and report rows stay scoped to the active account and client workspace. |
| Campaign performance | Campaign spend, leads, attributed revenue, ROAS, recommendation text, and unsupported-state labels. | Recommendations are generated from top campaign performance, attention items, and missing source conditions. |
| Attention items | Setup gaps, stale source warnings, spend-without-revenue rows, and follow-up items that need action. | Connector health, report recommendations, Ask Data unsupported states, and dashboard readiness feed the attention layer. |
Workflow
The sample mirrors the same snapshot, source row, recommendation, and unsupported-state behavior used by the actual report workflow.
| Step | What happens | User-visible proof |
|---|---|---|
| Freeze the snapshot | The report starts from a scoped snapshot so the exported artifact keeps the same metrics, date range, insights, and recommendations after future syncs run. | The client can review the same report state later instead of watching the evidence shift underneath a previously exported claim. |
| Show the source mix | Source rows explain what ad, call, job, invoice, and payment systems contributed to the report before the reader reaches recommendations. | The client sees why a revenue claim is supported and which source still needs setup before another claim can be made. |
| Tie recommendations to rows | Budget and follow-up recommendations cite campaign rows, attention items, missing revenue evidence, or source-health state. | The agency can explain a recommendation without opening a separate spreadsheet or making a vague performance claim. |
| Expose unsupported states | When spend, leads, revenue, or payment evidence is missing, the report labels the gap instead of inventing a complete ROAS story. | Unsupported rows become setup or investigation steps, which protects client trust during review. |
Proof standards
The preview is valuable only if it teaches the buyer what evidence a real report needs before claims become client-facing.
The page labels the artifact as a sample structure and routes result-dependent claims to disclosures, metric definitions, and source setup requirements.
The sample report explains that real exports are generated from scoped snapshots with account, client, date range, metrics, insights, and recommendations frozen together.
Unsupported and missing-evidence rows are labeled as setup or investigation paths before the report recommends budget changes.
Each recommendation in the sample is attached to a row-level reason and a proof route that explains the source or metric rule.
FAQ
The preview should reduce uncertainty while staying clear about what depends on real connected data.
No. It is a public sample structure that shows how SIRJ reports organize snapshot metrics, source rows, campaign performance, attention items, and recommendations.
Yes. Real report sections depend on connected sources, dashboard readiness, date range, client branding, available campaign rows, recommendations, and export format.
Unsupported rows show buyers that SIRJ does not invent ROAS or revenue proof when source coverage is incomplete. The report should name the missing evidence.
The sample mirrors the report snapshot, report HTML, dashboard, integrations, Ask Data, and connector health paths that real exports use.
Ready when the numbers need to hold up
Use the live demo to see dashboard cards, source health, Ask Data, and exports before connecting a real client stack.