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/Ad sources integrations
Spend, campaign, click, and lead-source data that starts the revenue trail.
Data signals
Category pages make the library scannable by the job each connector performs, then point buyers to the exact connector pages for field-level proof.
Dashboard proof
This output only earns trust when the underlying connector records can be traced through normalized events, dashboard cards, and cited answers.
This output only earns trust when the underlying connector records can be traced through normalized events, dashboard cards, and cited answers.
This output only earns trust when the underlying connector records can be traced through normalized events, dashboard cards, and cited answers.
| Connector | Fields SIRJ uses | Dashboard output | Buyer question |
|---|---|---|---|
| Google Ads | Campaigns, Cost, Clicks | Booked revenue by campaign | Which campaigns produced booked jobs, not just leads? |
| Google Local Services | Lead source, Call leads, Message leads | Paid LSA lead outcomes | Which LSA leads became scheduled jobs? |
| LinkedIn Ads | Campaign ID, Campaign name, Spend | Campaign ROAS | How does campaigns affect booked revenue? |
| Meta Ads | Campaign ID, Campaign name, Spend | Paid social revenue trail | How does campaigns affect booked revenue? |
Connectors
Each connector page shows imported fields, dashboard examples, buyer questions, sample rows, and source-field lineage for that source.
MVP readyBooked revenue by campaign
MVP ready · Every 6 hours
Launch trackPaid LSA lead outcomes
Launch track · Every 6 hoursLinkedIn AdsRoadmapCampaign ROAS
Roadmap · Every 6 hoursMeta AdsMVP readyPaid social revenue trail
MVP ready · Every 6 hoursTikTok AdsLaunch trackCampaign ROAS
Launch track · Every 6 hoursValidation workflow
| Step | What has to be true |
|---|---|
| 1 | Import spend, campaign, and conversion records from ad platforms. |
| 2 | Normalize the source into spend and lead events that can be matched downstream. |
| 3 | Attach calls, jobs, opportunities, invoices, and payments from the rest of the stack. |
| 4 | Show campaign ROAS, spend without revenue, and budget recommendations with source lineage. |
Lineage route
Related categories
Bring call source, answered status, tracking number, duration, and recording context into the attribution path so phone leads are not treated as anonymous conversions.
CRM and pipelineConnect contacts, opportunities, pipeline stages, owners, tasks, and source fields so SIRJ can show whether leads became pipeline, stalled, or turned into won revenue.
FormsBring submissions, questions, answers, hidden source fields, and form metadata into the same path as CRM, calls, jobs, invoices, and payments.
Category-first integration planning
A connector is only persuasive when the buyer can see the downstream proof it unlocks. Use the category route to plan the stack before opening the first client workspace.