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.
Pricing/Connector QA
See how SIRJ Scale reviews source setup, sync history, required fields, connector health, reporting readiness, and unsupported states before client reports depend on a source.
Buyer answers
Scale buyers need more than a support label. They need to know what happens when a source is connected, stale, missing setup, or unable to support a report claim.
It includes a review of source setup, selected resources, sync history, missing requirements, required fields, recent failures, dashboard card eligibility, report readiness, and unsupported states for the connectors that matter to recurring client reporting.
Scale buyers can see whether a source is ready to support reports before a client meeting turns a connector issue into a trust issue.
Follow the source pathScale is for agencies where more client workspaces and more source combinations create operational risk. Connector QA gives those teams a clearer path for reviewing source readiness before recurring reporting depends on the data.
The plan difference becomes concrete: Scale adds operational review around the source layer, not just a bigger workspace limit.
Follow the source pathNo. Provider APIs, permissions, source records, credentials, and outages can still affect syncs. The QA lane reviews readiness and failure states so unsupported or stale source data does not quietly become a confident report claim.
The offer reduces operating surprise without weakening SIRJ's evidence standard or making promises the product cannot control.
Follow the source pathConnector health is the product surface that shows current setup, sync, stale, and failure states. Connector QA is the Scale support lane that reviews those states across a portfolio and turns them into source-readiness actions.
Buyers can distinguish the live product signal from the higher-touch review path that helps growing agencies operationalize that signal.
Follow the source pathQA surfaces
The lane follows each source from inventory to setup, sync freshness, required fields, and the reports that depend on it.
| Surface | Buyer sees | Review path |
|---|---|---|
| Source inventory | Which ad, call, form, CRM, operations, payment, and messaging sources exist across the client portfolio and which sources are active for reporting. | Review the current connector list, source categories, provider status, selected resources, client workspace scope, and whether each source has a reporting role. |
| Setup requirements | Missing setup such as credentials, selected account, selected form, webhook readiness, mapped pipeline stage, or required provider resource. | Compare each connector against setup requirements before the source is treated as ready for dashboard cards, Ask Data answers, reports, or exports. |
| Sync history and freshness | Recent sync attempts, latest success, latest failure, cadence, normalized event count, provider error, stale state, and consecutive failures. | Use connector health and recent sync runs to identify source drift before a stale connector feeds reporting or client-ready recommendations. |
| Required fields and card support | Whether imported records contain the fields needed for spend, leads, calls, jobs, invoices, payments, ROAS, source performance, and campaign rows. | Check source fields against metric definitions, dashboard card eligibility, report sections, and unsupported-state behavior before the report path is approved. |
| Report readiness | Which reports, weekly insights, Ask Data answers, and exports can rely on the connector, and which outputs need a gap message or another source. | Trace source readiness into dashboards, report snapshots, weekly delivery, Ask Data citations, export paths, and disclosure boundaries. |
Review path
Connector QA turns source health into an operating path: identify the source, check setup, inspect sync history, match fields to claims, and route the next action.
Workflow
| Step | What happens | User-visible proof |
|---|---|---|
| List the sources that matter | Start with the sources that support the agency's recurring reporting promises: ad platforms, call tracking, forms, CRM, operations, invoices, payments, messaging, and private sources. | The integration library and category pages show the source roles before the QA review decides whether each source is ready for client-facing proof. |
| Check setup requirements | Each connector is reviewed for credentials, selected provider resource, webhook readiness, mapped fields, required setup checks, and any missing action that blocks trustworthy reporting. | Onboarding and connector health pages show readable setup states instead of leaving the buyer to guess why a source is not ready. |
| Inspect sync history | The QA lane reviews cadence, latest success, latest failure, normalized event counts, provider errors, skipped runs, and consecutive failures for the connectors that support client reports. | Connector health keeps run history and failure patterns visible before a stale source becomes a report-ready number. |
| Match fields to reporting claims | Imported fields are checked against metric definitions, dashboard cards, Ask Data citations, report rows, weekly insight needs, and any unsupported claim the source cannot support yet. | Metric definitions and integration detail pages show which fields and sample rows can support visible dashboard and report output. |
| Route the next action | The review ends by naming whether the connector is ready, needs setup, needs reauthorization, needs another source, belongs in custom connector scope, or should stay out of reports for now. | Reports, custom connectors, Enterprise, and disclosures pages show the next path when source readiness changes what the product can safely claim. |
Readiness risks
The lane is valuable when it keeps predictable source problems from becoming client-facing reporting problems.
A provider can appear connected while the required account, form, pipeline, webhook, or resource selection is still missing.
The QA lane reviews setup requirements and routes missing actions back to onboarding or connector health before the source supports reports.
Inspect the related surfaceA client report can look current while the latest successful sync is outside the cadence needed for the reporting period.
Sync history, cadence, last success, last failure, skipped runs, and severity are reviewed before reports use the source.
Inspect the related surfaceA connector may import useful records but still lack the fields needed for a specific metric, dashboard card, report row, or attribution claim.
Required fields are checked against metric definitions and report sections so unsupported claims stay visible instead of becoming polished guesses.
Inspect the related surfaceA must-have source outside the public catalog can create false expectations if it is treated like a normal supported connector.
The QA lane can identify the blocker, but private source scope moves to custom connector and Enterprise planning before production reporting depends on it.
Inspect the related surfaceProof standards
Connector rows are reviewed with account and client scope intact before readiness is applied to a report path.
Setup requirements are reviewed before dashboard cards, report sections, weekly insights, or Ask Data answers rely on the source.
Sync cadence, latest run, stale state, repeated failures, and provider errors stay visible before output is treated as current.
Unsupported metrics, missing source fields, private connector needs, and provider limitations stay named in the report path.
FAQ
Yes. Scale includes a connector QA lane for reviewing source setup, sync history, required fields, connector health, and reporting readiness across the sources that support recurring client reporting.
No. Onboarding gets the first workspace and source path moving. Connector QA is for Scale teams that need recurring review across more clients, more connectors, and more reporting surfaces.
No. Provider uptime, API behavior, account permissions, and missing source records remain outside SIRJ's control. The QA lane makes those states visible so reports do not quietly rely on weak evidence.
Enterprise is the cleaner path when the blocker is SSO, procurement, custom retention, a private source, custom destination scope, or implementation planning that changes the rollout agreement.
Ready when the numbers need to hold up
Talk through the connector stack, setup requirements, sync history, required fields, report readiness, and whether a private source belongs in Enterprise planning.