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/LinkedIn Ads
Review the planned LinkedIn Ads data path, expected fields, and validation gates before it becomes a live connector.
Data brought into SIRJ
Review the signals SIRJ plans to map, which records would support reporting, and what has to be proven 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. Before rollout, connector scope and provider readiness have to be confirmed.
Graph
SIRJ previews campaign roas output from fields such as Campaign ID, Campaign name, Spend.
Review
LinkedIn Ads record to Spend and campaign performance to Scoped client workspace to Campaign ROAS before the result is used in dashboards, Ask Data, or reports.
Cost per booked job + Spend without revenue
Spend and campaign performance: Normalized. Available to dashboard and Ask Data
Connection and sync stay visible before client reporting.
Revenue proof lens
LinkedIn 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 | LinkedIn Ads would use Campaign ID, Campaign name, Spend, Clicks from records such as campaigns, ad groups, spend 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 campaign roas as campaign roas output, with sample evidence such as Spend and campaign performance: Normalized; Cost per booked job: Available. |
| User decision | The user should verify before planning how does campaigns affect booked revenue without jumping into the raw provider account. |
| Safe fallback | If LinkedIn 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.
LinkedIn Ads appears as campaign roas output with rows such as Spend and campaign performance: Normalized, plus source-field context before the card is trusted.
LinkedIn Ads record to Spend and campaign performance to Scoped client workspace to Campaign ROAS before the card can be treated as reportable evidence.A user can ask how does campaigns affect booked revenue and get a cited answer only when LinkedIn Ads records are scoped, current, and matched to downstream evidence.
If LinkedIn 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 LinkedIn 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.LinkedIn 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.
Campaign ROAS can appear in dashboard cards, cited Ask Data answers, and report sections after connector scope, provider access, and test records are approved.
LinkedIn Ads record to Spend and campaign performance to Scoped client workspace to Campaign ROAS before client-facing output can use LinkedIn Ads.
LinkedIn 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 LinkedIn 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
LinkedIn Ads is modeled as a roadmap source, so this page shows the planned data path, proof requirements, and rollout questions before it becomes a live connector.
| Imported signal | Visible surface | Buyer question answered |
|---|---|---|
| Campaigns | Campaign ROAS | How does campaigns affect booked revenue? |
| Ad groups | Cost per booked job | How does ad groups affect booked revenue? |
| Spend | Spend without revenue | How does spend affect booked revenue? |
| Clicks | Campaign ROAS | How does campaigns affect booked revenue? |
LinkedIn Ads records show up as campaign roas so buyers can see what the source changed downstream.
How does campaigns affect booked revenue?
How does ad groups affect booked revenue?
How does spend affect booked revenue?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
LinkedIn Ads must clear connector scoping, provider API review, client-resource selection, and sync expectations 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.
Campaign ROAS appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If LinkedIn 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, 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 plans to map campaigns, ad groups, spend, clicks, conversions, utm source from LinkedIn Ads. The page also names the fields used for visible proof, including Campaign ID, Campaign name, Spend, Clicks, so buyers can see which source records support the dashboard output.
LinkedIn Ads 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 campaign roas.
The sample revenue view models LinkedIn Ads as campaign roas output. Example rows include Spend and campaign performance: Normalized; Cost per booked job: Available, with the exact output depending on the client's connected sources and synced records.
If LinkedIn 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
Use the workspace intent to flag the source, then confirm readiness, validation gates, and the rest of the client stack before treating it as reportable evidence.