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 Ads
Bring campaigns, costs, clicks, conversions, and search intent into the revenue graph so agencies can defend budget moves with invoice-backed proof.
Data brought into SIRJ
Review the exact signals SIRJ can pull, which records can support reporting, and where the source starts contributing 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. Once scoped to a client workspace, the source can feed the records listed above.
Graph
SIRJ previews revenue matched to campaign from fields such as Campaigns, Cost, Clicks.
Review
Google Ads record to Spend and campaign performance to Scoped client workspace to Booked revenue by campaign before the result is used in dashboards, Ask Data, or reports.
Cost per booked job + Spend without revenue
Emergency plumbing: $18.6k. 7.4x ROAS
Connection and sync stay visible before client reporting.
Revenue proof lens
Google Ads 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 Ads uses Campaigns, Cost, Clicks, Conversions from records such as campaigns, ad groups, search terms 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 booked revenue by campaign as revenue matched to campaign, with sample evidence such as Emergency plumbing: $18.6k; Water heater install: $12.3k. |
| User decision | The user can decide which campaigns produced booked jobs, not just leads without jumping into the raw provider account. |
| Safe fallback | If Google Ads 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 Ads appears as revenue matched to campaign with rows such as Emergency plumbing: $18.6k, plus source-field context before the card is trusted.
Google Ads record to Spend and campaign performance to Scoped client workspace to Booked revenue by campaign before the card can be treated as reportable evidence.A user can ask which campaigns produced booked jobs, not just leads and get a cited answer only when Google Ads records are scoped, current, and matched to downstream evidence.
If Google Ads 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 Ads 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 Ads 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.
Booked revenue by campaign can appear in dashboard cards, cited Ask Data answers, and report sections when the source is connected and current.
Google Ads record to Spend and campaign performance to Scoped client workspace to Booked revenue by campaign before client-facing output can use Google Ads.
Google Ads 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 Ads 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
SIRJ does not just show that Google Ads is connected. It turns the source into decision-ready cards, alerts, and Ask Data answers.
| Imported signal | Visible surface | Buyer question answered |
|---|---|---|
| Campaigns | Campaign ROAS | Which campaigns produced booked jobs, not just leads? |
| Ad groups | Cost per booked job | Where is spend rising without collected revenue? |
| Search terms | Spend without revenue | Which search themes deserve more budget? |
| Cost | Campaign ROAS | Which campaigns produced booked jobs, not just leads? |
The user sees which Google Ads campaigns produced booked work after calls and invoices are matched.
Which campaigns produced booked jobs, not just leads?
Where is spend rising without collected revenue?
Which search themes deserve more budget?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
Google Ads must be connected, scoped to the right client workspace, and synced on its expected cadence before its records can affect a dashboard.
Spend and campaign performance 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.
Booked revenue by campaign appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If Google Ads 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, 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.
Ad sourcesReview the planned LinkedIn Ads data path, expected fields, and validation gates before it becomes a live connector.
Integration FAQ
Answers stay tied to imported fields, visible dashboard output, and what SIRJ refuses to claim when source evidence is missing.
SIRJ imports campaigns, ad groups, search terms, cost, clicks, conversions, conversion value from Google Ads. The page also names the fields used for visible proof, including Campaigns, Cost, Clicks, Conversions, so buyers can see which source records support the dashboard output.
Google Ads supports 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 booked revenue by campaign.
Google Ads appears in the sample revenue view as revenue matched to campaign. Example rows include Emergency plumbing: $18.6k booked; Water heater install: $12.3k booked, with the exact output depending on the client's connected sources and synced records.
If Google Ads 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
The first source is only useful once it is tied to the rest of the client stack. That is the SIRJ job.