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/HubSpot
Review HubSpot 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: Hourly. During setup, permissions and client-resource scope have to be confirmed first.
Graph
SIRJ previews lead stage velocity output from fields such as Lead ID, Submitted at, Contact source.
Review
HubSpot record to Leads and source attribution to Scoped client workspace to Lead stage velocity before the result is used in dashboards, Ask Data, or reports.
Uncontacted leads + Pipeline by channel
Leads and source attribution: Normalized. Available to dashboard and Ask Data
Connection and sync stay visible before client reporting.
Revenue proof lens
HubSpot 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 | HubSpot is scoped to use Lead ID, Submitted at, Contact source, UTM campaign from records such as lead records, contact details, submitted at before SIRJ lets the source influence reporting. |
| Revenue match target | The important question is whether those records can be matched to job, invoice, payment, and follow-up records that show whether the lead became revenue inside the same client workspace. |
| Dashboard result | The visible output is lead stage velocity as lead stage velocity output, with sample evidence such as Leads and source attribution: Normalized; Booked work, jobs, deals, or opportunities: Normalized. |
| User decision | The user should verify during setup how does lead records affect booked revenue without jumping into the raw provider account. |
| Safe fallback | If HubSpot is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting lead stage velocity 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.
HubSpot appears as lead stage velocity output with rows such as Leads and source attribution: Normalized, plus source-field context before the card is trusted.
HubSpot record to Leads and source attribution to Scoped client workspace to Lead stage velocity before the card can be treated as reportable evidence.A user can ask how does lead records affect booked revenue and get a cited answer only when HubSpot records are scoped, current, and matched to downstream evidence.
If HubSpot is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting lead stage velocity 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 uncontacted leads from HubSpot 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.HubSpot 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.
Lead stage velocity can appear in dashboard cards, cited Ask Data answers, and report sections after setup, permissions, and first synced records are reviewed.
HubSpot record to Leads and source attribution to Scoped client workspace to Lead stage velocity before client-facing output can use HubSpot.
HubSpot 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 HubSpot is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting lead stage velocity 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
HubSpot 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 records | Lead stage velocity | How does lead records affect booked revenue? |
| Contact details | Uncontacted leads | How does contact details affect booked revenue? |
| Submitted at | Pipeline by channel | How does submitted at affect booked revenue? |
| Source fields | Lead stage velocity | How does lead records affect booked revenue? |
HubSpot records show up as lead stage velocity so buyers can see what the source changed downstream.
How does lead records affect booked revenue?
How does contact details affect booked revenue?
How does submitted at affect booked revenue?
Proof contract
A connected logo is not proof. SIRJ shows the validation path that turns source data into reportable evidence.
HubSpot must complete setup, be scoped to the right client workspace, and sync on its expected cadence before its records can affect a dashboard.
Leads and source attribution, Booked work, jobs, deals, or opportunities 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.
Lead stage velocity appears only when the required source fields can support the visible chart, card, or cited answer.
Evidence basis
If HubSpot is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting lead stage velocity as proven.
Lineage route
Related connectors
Bring lead records, contact details, submitted at, source fields, utm campaign, lead status into client dashboards, weekly reports, and Ask Data answers with source lineage intact.
CRM and pipelineReview Follow Up Boss setup, expected fields, and validation gates before its records are treated as reporting evidence.
CRM and pipelineReview the planned Pipedrive 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 is scoped to map lead records, contact details, submitted at, source fields, utm campaign, lead status from HubSpot. The page also names the fields used for visible proof, including Lead ID, Submitted at, Contact source, UTM campaign, so buyers can see which source records support the dashboard output.
HubSpot 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 lead stage velocity.
The sample revenue view models HubSpot as lead stage velocity output. Example rows include Leads and source attribution: Normalized; Booked work, jobs, deals, or opportunities: Normalized, with the exact output depending on the client's connected sources and synced records.
If HubSpot is disconnected, stale, or missing required fields, SIRJ shows the missing source path instead of presenting lead stage velocity 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.