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 generates weekly ROI insights, detects spend and lead anomalies, sends client-ready emails, and records notification history.
Buyer questions
The weekly layer explains what gets emailed, which changes become attention items, how alert history is recorded, and how each item routes back to source-backed dashboard evidence.
Weekly insights are scheduled ROI summaries generated from the active client dashboard. They include spend, attributed revenue, ROAS, lead count, closed deals, top performer context, needs-attention items, and a dashboard link.
The agency can replace a recurring manual report check with a weekly proof loop that stays tied to the same dashboard evidence clients can inspect.
Follow the evidence pathSIRJ compares current and previous dashboard metrics, then flags material spend jumps, lead drops, and campaigns that spend above the threshold without attributed leads.
The alert layer separates reporting work from operational follow-up, so teams can address spend movement, lead loss, or campaign waste before the client asks.
Follow the evidence pathYes. Weekly delivery creates notification records for sent and failed emails, and anomaly alerts create active dashboard records with status, recipient, subject, provider message id, error, and metadata.
The account can distinguish a delivered report, failed delivery, and active alert instead of guessing whether automation quietly worked.
Follow the evidence pathWeekly alerts start from the same tenant-scoped dashboard config used by reports and Ask Data, then store the dashboard URL, week label, severity, anomaly payload, and client scope.
Alerts do not become a separate black box. They point back to the dashboard and source path that produced the weekly summary.
Follow the evidence pathWeekly surfaces
SIRJ does not treat weekly delivery as a separate reporting layer. The email, needs-attention list, notification center, and report recommendations all start from the scoped client dashboard.
What users see
Buyers should see exactly where weekly summaries, active alerts, due states, and report recommendations come from before they trust automation with client communication.
| Surface | User sees | Source path |
|---|---|---|
| Weekly ROI email | Week label, total ad spend, attributed revenue, ROAS, new leads, closed deals, top performer, needs-attention items, and a button back to the dashboard. | Weekly email rendering receives generated insights from tenant-scoped dashboard metrics and escapes all visible text before sending. |
| Needs-attention list | Spend jumps, lead drops, and campaigns with spend but no attributed leads listed as client-review items. | Anomaly detection compares current and previous dashboard metrics, then filters non-info items into the needs-attention list. |
| Notification center | Active, sent, and failed notification counts plus rows for status, recipient, subject, type, provider id, error, and time. | Notification center builds from tenant-scoped notification records and rejects records outside the active account and client. |
| Scheduled send due state | Whether the weekly send is due, already sent, or not due for the client timezone and schedule window. | Weekly delivery reads the latest sent notification, applies the Monday 7:00 schedule in the configured timezone, and skips duplicate sends inside the window. |
| Report recommendations | Recommendations in reports and sample reports that cite top campaign performance, missing revenue evidence, or needs-attention items. | Report recommendations are built from extracted dashboard metrics and generated insights before report snapshots are rendered or exported. |
Alert signals
The alert table names the current signals SIRJ can explain publicly: spend movement, lead movement, and campaigns spending without attributed leads.
| Signal | Trigger | User impact |
|---|---|---|
| Spend jump | Current total spend or source-level spend rises materially compared with the previous dashboard period. | The weekly email and notification history can show that budget movement needs review before it becomes a surprise in a client meeting. |
| Lead drop | Total lead count or source-level lead volume drops materially compared with the previous dashboard period. | The agency can review source quality, follow-up, and connector health before assuming the campaign itself failed. |
| Campaign spend with no leads | A campaign spends above the configured threshold in the current dashboard period while producing zero attributed leads. | SIRJ can turn the row into a concrete investigation path instead of letting wasted spend hide inside blended performance. |
Delivery states
Sent, failed, and active states keep weekly reporting honest: teams can see who received the report, what failed, and which alert still needs review.
| State | User sees | Source path |
|---|---|---|
| Sent | A delivery row with recipient, weekly insight subject, provider message id when available, week label metadata, and occurred-at timestamp. | Successful email sends create notification records with weekly_insights_email type and sent status. |
| Failed | A failed delivery row with recipient, subject, error message, week label metadata, and occurred-at timestamp. | Email client failures become failed notification records instead of disappearing from report history. |
| Active | An active anomaly alert assigned to the dashboard recipient with severity, anomaly payload, dashboard URL, week label, and timestamp. | Anomaly notification records are created from generated insights and scoped to the active account and client. |
Workflow
Weekly insights run automatically while the path underneath stays concrete: dashboard build, comparison, email render, notification history, and schedule protection.
| Step | What happens | Visible proof |
|---|---|---|
| Build the current dashboard | Weekly delivery starts by building the current dashboard for the active account, client, date range, registry, and event store before any email or alert is generated. | The weekly summary uses the same dashboard cards, source rows, tenant scope, and date bounds that the user can inspect in the workspace. |
| Compare previous performance | When previous dashboard evidence is available, SIRJ computes spend, revenue, ROAS, and lead changes before deciding which movement deserves attention. | The email can show week-over-week changes and needs-attention items instead of only restating current totals. |
| Render the client-ready email | Weekly email rendering turns the insight object into text and HTML with summary metrics, top performer, needs-attention rows, lead sources, closed deals, and dashboard CTA. | Recipients get a compact report they can read without opening every source system first, with the dashboard CTA available when they need row-level context. |
| Record delivery and alert history | After delivery, SIRJ stores sent or failed email notification records and active anomaly records so the account can review what happened later. | The notification center can show status counts and reviewable rows for each delivery or alert state, including recipient, subject, error, and time. |
| Skip duplicate scheduled sends | The due-send workflow reads recent sent notifications, checks the configured timezone schedule, and returns already-sent or not-due states before doing expensive dashboard work again. | Automated reporting stays predictable and avoids duplicate sends during the same schedule window. |
Proof standards
The weekly loop should increase trust by making records visible, keeping alerts attached to dashboard evidence, and avoiding duplicate sends.
Insight generation, notification center building, and weekly delivery assert active account and client scope before using dashboard or notification records.
Weekly delivery stores sent, failed, and active records with recipient, subject, provider id, error, metadata, and timestamp.
Anomalies are generated from extracted dashboard metrics and carry current or previous windows, source, campaign, severity, and value context.
Due-send logic checks the client timezone, weekly schedule, recent sent notification, and schedule window before sending.
FAQ
These answers keep the weekly promise precise: what the email includes, what alerts exist, how failures are recorded, and where plan limits apply.
It includes the week label, total ad spend, attributed revenue, ROAS, new leads, lead sources, closed deals, top performer, needs-attention items, and a link back to the dashboard.
The current alert layer covers material spend jumps, lead drops, and campaigns that spend above the threshold without attributed leads, with each alert tied back to dashboard metrics.
Yes. Failed email sends become notification records with recipient, subject, error, week label metadata, and timestamp so the account can review the issue.
Weekly insight delivery depends on plan features and workspace setup. Pricing and billing pages explain which plans include weekly emails and when reporting volume should move to a higher plan.
Make reporting hard to miss
Use the live workspace to inspect weekly delivery states, active alerts, source-backed reports, and the dashboard evidence behind each weekly summary.