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.
Integrations/Google Local Services
Review Google Local Services setup, expected fields, and validation gates before its records are treated as reporting evidence.
Data brought into SIRJ
Review the signals SIRJ is scoped to map, which records can support reporting, and what setup has to prove before the source contributes to proof.
Dashboard proof path
Each integration page shows what comes in, what dashboard view it can unlock, and what has to be checked before the output becomes client-ready proof.
Connect
Sync: Every 6 hours. During setup, permissions and client-resource scope have to be confirmed first.
Graph
SIRJ previews lead outcomes from fields such as Lead source, Call leads, Message leads.
Review
Google Local Services record to Spend and campaign performance to Scoped client workspace to Paid LSA lead outcomes before the result is used in dashboards, Ask Data, or reports.
Cost per booked job + Spend without revenue
Booked jobs: 19. $23.2k collected
Connection and sync stay visible before client reporting.
Revenue proof lens
Google Local Services matters in SIRJ when its source records can be matched to downstream revenue evidence; otherwise the page shows the missing proof path instead of presenting the connector as attribution-ready.
| Proof question | How SIRJ handles it |
|---|---|
| Source record SIRJ reads | Google Local Services is scoped to use Lead source, Call leads, Message leads, Lead cost from records such as lead source, call leads, message leads before SIRJ lets the source influence reporting. |
| Revenue match target | The important question is whether those records can be matched to lead, job, invoice, or payment records from the rest of the client stack inside the same client workspace. |
| Dashboard result | The visible output is paid lsa lead outcomes as lead outcomes, with sample evidence such as Booked jobs: 19; Contacted, not booked: 7. |
| User decision | The user should verify during setup which LSA leads became scheduled jobs without jumping into the raw provider account. |
| Safe fallback | If Google Local Services is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting campaign roas as proven. |
Unlocked surfaces
A connector should not disappear into a shared data pool. These are the visible places where the source can affect decisions, reports, answers, and review work.
Google Local Services appears as lead outcomes with rows such as Booked jobs: 19, plus source-field context before the card is trusted.
Google Local Services record to Spend and campaign performance to Scoped client workspace to Paid LSA lead outcomes before the card can be treated as reportable evidence.A user can ask which lsa leads became scheduled jobs and get a cited answer only when Google Local Services records are scoped, current, and matched to downstream evidence.
If Google Local Services is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting campaign roas as proven. The assistant should return the missing proof path instead of guessing when the source cannot support the answer.The weekly report can summarize cost per booked job from Google Local Services alongside the rest of the client stack, with source rows kept close to the recommendation.
Report output should stay held for review when required records are stale, missing, or unable to prove the visible revenue claim.Google Local Services can create a visible setup, stale-source, or missing-proof state so operators know whether to connect, retry, review, or explain the source before the client sees it.
The connector state has to remain visible in the client workspace, alert inbox, and review path before reports or AI-generated copy rely on it.Reporting readiness
This keeps connector pages honest: a source can be connected without being safe for client-facing revenue proof.
Paid LSA lead outcomes can appear in dashboard cards, cited Ask Data answers, and report sections after setup, permissions, and first synced records are reviewed.
Google Local Services record to Spend and campaign performance to Scoped client workspace to Paid LSA lead outcomes before client-facing output can use Google Local Services.
Google Local Services stays visible as a setup, stale-source, missing-field, or review-required state when a record path is incomplete.
Operators should confirm source scope, latest sync, selected resources, and required fields before approving the output.
If Google Local Services is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting campaign roas as proven.
Dashboards, Ask Data answers, weekly reports, and exports should name the missing proof path instead of smoothing over the gap.
How users see it
Google Local Services is on the launch track, so this page shows the setup path, expected records, and proof gates before its data becomes dashboard evidence.
| Imported signal | Visible surface | Buyer question answered |
|---|---|---|
| Lead source | Campaign ROAS | Which LSA leads became scheduled jobs? |
| Call leads | Cost per booked job | Where did paid leads go uncontacted? |
| Message leads | Spend without revenue | Which service categories are worth keeping active? |
| Lead cost | Campaign ROAS | Which LSA leads became scheduled jobs? |
The page shows owners whether expensive Local Services leads became scheduled jobs or follow-up gaps.
Which LSA leads became scheduled jobs?
Where did paid leads go uncontacted?
Which service categories are worth keeping active?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
Google Local Services must complete setup, be scoped to the right client workspace, and sync on its expected cadence before its records can affect a dashboard.
Spend and campaign performance, Leads and source attribution become typed revenue-path events, which keeps source-specific payloads from turning into loose reporting copy.
Records have to stay inside the active account and client workspace before they can influence attribution, reports, exports, or Ask Data answers.
Paid LSA lead outcomes appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If Google Local Services is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting campaign roas as proven.
Lineage route
Related connectors
Bring campaigns, costs, clicks, conversions, and search intent into the revenue graph so agencies can defend budget moves with invoice-backed proof.
Ad sourcesBring campaigns, ad groups, spend, clicks, conversions, utm source into client dashboards, weekly reports, and Ask Data answers with source lineage intact.
Ad sourcesReview TikTok Ads setup, expected fields, and validation gates before its records are treated as reporting evidence.
Integration FAQ
Answers stay tied to imported fields, visible dashboard output, and what SIRJ refuses to claim when source evidence is missing.
SIRJ is scoped to map lead source, call leads, message leads, lead cost, account, service category from Google Local Services. The page also names the fields used for visible proof, including Lead source, Call leads, Message leads, Lead cost, so buyers can see which source records support the dashboard output.
Google Local Services is expected to support this by giving SIRJ a source-specific part of the revenue path, then matching it to the rest of the connected client stack before the result appears as paid lsa lead outcomes.
The sample revenue view models Google Local Services as lead outcomes. Example rows include Booked LSA calls: 19; Uncontacted paid leads: 4, with the exact output depending on the client's connected sources and synced records.
If Google Local Services is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting campaign roas as proven.
Ready when the numbers need to hold up
Use the workspace intent to begin setup, then confirm permissions, synced records, and validation gates before revenue claims depend on it.