Connector setup

Connector setup should make access, resources, and readiness obvious before data enters reports.

Review SIRJ connector setup, OAuth and API key permissions, selected resources, webhook callbacks, credential handling, source ownership, and readiness states before reporting uses a source.

Browse integrations Review source coverage Connector health Webhook ingestion Security controls Custom sources

Buyer questions

Setup should answer access questions before a source reaches the dashboard.

Buyers need a plain path through authorization, permissions, selected resources, setup controls, and source readiness before trusting a connected provider.

Buyer answer

What does connector setup include?

Connector setup includes the authorization method, required permissions, credential state, selected provider resources, webhook callbacks, setup controls such as pipeline mapping, sync cadence, launch proof groups, and the readiness checks that decide whether records can feed product surfaces.

A buyer can see the setup work before connecting a source, then understand why a connector may be authorized but still not ready for dashboard cards, answers, reports, or exports.

Follow the setup path

Buyer answer

How are OAuth and API key sources different?

OAuth sources send the user through a provider authorization flow with requested scopes and a callback, while API key sources require a key input that SIRJ stores behind a credential reference. Both paths still need setup checks before the source becomes report-ready.

The buyer can tell whether a source needs a provider login, a key from an admin, a webhook callback, or a selected resource before treating it as part of the revenue proof path.

Follow the setup path

Buyer answer

Why does SIRJ ask for selected resources?

Some providers expose multiple ad accounts, forms, advertisers, companies, locations, or pipelines behind one authorization. SIRJ needs the exact resource before it can keep client scope clean and route records to the right dashboard or report.

Resource selection prevents a broad provider connection from blending accounts, clients, forms, or locations that should stay separate in attribution and reporting.

Follow the setup path

Buyer answer

What happens when setup is incomplete?

Incomplete setup stays visible through setup-required states, missing selected resources, inactive webhooks, unmapped pipeline stages, stale sync status, reconnect needs, unsupported dashboard cards, blocked answers, or report sections that name the missing evidence.

A partially configured connector can still be useful, but SIRJ shows the exact missing action before the source is allowed to support a client-facing revenue claim.

Follow the setup path

Setup lanes

Map each authorization path to the setup work it actually requires.

A connector may need OAuth, an API key, selected resources, a webhook callback, or mapping work before it can support a reportable number.

Setup lane	Buyer question	SIRJ path
OAuth authorization	Does the provider need a logged-in admin to approve requested scopes, return through the callback, and keep a refreshable credential available for recurring syncs?	OAuth connectors expose the authorization method, required permissions, callback behavior, token strategy, and reconnect state before records are treated as stable.
API key entry	Does the source need an API key from an account owner, and can the buyer see that key entry is separate from public provider names or dashboard output?	API key connectors use a credential input label, encrypted credential envelope, credential reference, and redacted display path so the key never becomes public page copy.
Resource selection	Which account, form, advertiser, company, location, or pipeline should this connector use for the client workspace and reporting job?	Resource-selection controls name the selected resource and save it as setup state before source rows can support dashboard or report surfaces.
Webhook callback	Does this provider need a callback URL or webhook activation before SIRJ can receive new lead, form, booking, payment, or message activity?	Webhook setup exposes a callback URL, webhook connection state, setup requirement, and health state so event delivery gaps do not look like normal reporting silence.
Pipeline and field mapping	Does the connector need won, lost, pipeline, status, or required field mapping before source records can support attribution and reports?	Setup controls and calculation rules separate connected data from claim-ready data when fields, stages, or mappings are still missing.

Permission review

Permissions should be tied to the proof surface they unlock.

The useful access question is not whether a provider is connected. It is whether the approved scope can support the reporting claim.

Permission group	Used for	Buyer check
Ad platform access	Campaigns, ad groups, spend, clicks, impressions, conversions, account ids, and date ranges that support spend and performance views.	Confirm the selected ad account matches the client workspace and that downstream revenue sources exist before ROAS or revenue claims appear.
CRM or pipeline access	Contacts, companies, opportunities, stages, owners, source fields, status changes, expected value, and activity dates used in lead progression views.	Confirm stage mapping and source fields before pipeline data is allowed to support attribution, client reports, or source-quality answers.
Form, call, or message access	Submissions, calls, conversations, hidden source fields, timestamps, answered or missed state, and contact context that support intake and lead quality.	Confirm the selected form, tracking account, or message source before treating lead intake as clean enough for dashboards and weekly summaries.
Operations and booking access	Jobs, appointments, bookings, service dates, location context, customer references, operational ids, and status changes used to prove booked work.	Confirm selected location or company scope before booked-work evidence is used in attribution, multi-location reporting, or client-ready reports.
Invoice, payment, and books access	Invoices, totals, collected amount, payment state, customer references, refunds, dates, and accounting ids used to support financial revenue proof.	Confirm financial records are scoped to the right client and date basis before collected revenue, invoice-backed ROI, or exportable proof appears.

Resource selection

A provider connection is not enough when multiple resources sit behind it.

Selected accounts, forms, companies, locations, pipelines, callbacks, and private source owners keep records scoped to the correct client workspace.

Resource	Buyer sees	Readiness rule
Selected account or advertiser	The chosen ad account or advertiser is named before campaign spend and performance data appears in source coverage, dashboard cards, or report proof.	Spend rows can support activity views once the account is selected, but revenue claims wait for downstream outcome records.
Selected form or intake source	The chosen form or intake source is separated from other provider resources so lead rows can be reviewed without mixing unrelated submissions.	Form records can support intake analysis when timestamps and source fields exist; downstream value still needs CRM, job, invoice, or payment evidence.
Selected company, location, or pipeline	The source owner can confirm which company, location, or pipeline SIRJ is reading before records enter client workspace reporting.	Operational records stay scoped to the workspace and need usable status, date, and customer references before attribution or report output depends on them.
Webhook endpoint	A webhook-required connector shows callback setup and active state instead of letting missing event delivery look like weak marketing performance.	Webhook sources do not become current until callback setup and recent delivery health can support the reporting period.
Private source owner	Enterprise and custom connector planning names the source owner, access method, required records, rollout stage, and unsupported states before private data is treated as public coverage.	Private sources stay in custom connector scope until authentication, resources, fields, validation, and reporting role have been approved.

Setup workflow

Move from access request to source-ready proof.

The setup path starts with the source role, then moves through authorization, selected resource, health checks, and supported output decisions.

Identify the source role Authorize with the right method Select the exact resource Check setup and sync health Unlock only supported outputs

Proof standards

Setup should prevent connected-but-not-ready sources from becoming report claims.

These standards keep credentials private, resources scoped, and unsupported states visible until a source can defend the claim.

Proof standardDo not treat authorization as readiness

A provider can be authorized while the selected account, form, webhook, pipeline mapping, sync history, or required field is still missing.

SIRJ separates connection status from setup requirements and health state so a connected source cannot silently become a report-ready source.

Proof standardKeep credentials out of public output

Credential values, access tokens, API keys, provider errors, and external labels can create security and trust problems if they leak into UI or public pages.

Credential envelopes, redacted credential display, escaped provider output, and public setup summaries keep sensitive setup details away from rendered marketing and app surfaces.

Proof standardSelect resources before reporting

A broad provider connection can pull the wrong ad account, form, company, location, or pipeline when multiple client resources sit behind one authorization.

Resource-selection checks keep the exact source visible before normalized rows feed dashboard cards, attribution, Ask Data, reports, or exports.

Proof standardShow unsupported states plainly

Incomplete setup can become misleading when reports fill the gap with smooth-looking charts, broad recommendations, or revenue language the source cannot support.

Unsupported answers, locked cards, missing-source report sections, custom connector scope, and connector health states keep the gap visible until the source can defend the claim.

FAQ

Connector setup questions buyers ask before trusting connected data.

These answers make access, resources, and readiness plain before the buyer turns a provider connection into a reporting dependency.

FAQ

Does SIRJ show required permissions before setup?

Yes. Connector setup data includes the authorization method, required permissions, setup notes, credential input needs, setup requirements, resource selection, sync behavior, and dashboard unlocks before a source is treated as report-ready.

FAQ

Can a connector be authorized but blocked from reporting?

Yes. A connector can be authorized while selected resources, webhook activation, pipeline mapping, recent syncs, required fields, or downstream outcome evidence are still missing.

FAQ

Where does resource selection happen?

Resource selection happens after authorization when a provider exposes accounts, advertisers, forms, companies, locations, or pipelines that must be tied to the correct client workspace.

FAQ

How does setup relate to connector health?

Setup defines what must be present for the source to be usable. Connector health shows the current state: ready, setup required, stale, failing, disconnected, or needing reauthorization.

Ready when the numbers need to hold up

Review the source path before reporting depends on it.

Browse the connector library, confirm source coverage, and use connector health to see whether setup is ready enough for dashboards, answers, and reports.

Browse integrations See connector health

What does connector setup include?

A buyer can see the setup work before connecting a source, then understand why a connector may be authorized but still not ready for dashboard cards, answers, reports, or exports.

Follow the setup path

How are OAuth and API key sources different?

The buyer can tell whether a source needs a provider login, a key from an admin, a webhook callback, or a selected resource before treating it as part of the revenue proof path.

Follow the setup path

Why does SIRJ ask for selected resources?

Resource selection prevents a broad provider connection from blending accounts, clients, forms, or locations that should stay separate in attribution and reporting.

Follow the setup path

What happens when setup is incomplete?

A partially configured connector can still be useful, but SIRJ shows the exact missing action before the source is allowed to support a client-facing revenue claim.

Follow the setup path

Setup lane

Buyer question

SIRJ path

OAuth authorization

Does the provider need a logged-in admin to approve requested scopes, return through the callback, and keep a refreshable credential available for recurring syncs?

OAuth connectors expose the authorization method, required permissions, callback behavior, token strategy, and reconnect state before records are treated as stable.

API key entry

Does the source need an API key from an account owner, and can the buyer see that key entry is separate from public provider names or dashboard output?

API key connectors use a credential input label, encrypted credential envelope, credential reference, and redacted display path so the key never becomes public page copy.

Resource selection

Which account, form, advertiser, company, location, or pipeline should this connector use for the client workspace and reporting job?

Resource-selection controls name the selected resource and save it as setup state before source rows can support dashboard or report surfaces.

Webhook callback

Does this provider need a callback URL or webhook activation before SIRJ can receive new lead, form, booking, payment, or message activity?

Webhook setup exposes a callback URL, webhook connection state, setup requirement, and health state so event delivery gaps do not look like normal reporting silence.

Pipeline and field mapping

Does the connector need won, lost, pipeline, status, or required field mapping before source records can support attribution and reports?

Setup controls and calculation rules separate connected data from claim-ready data when fields, stages, or mappings are still missing.

Permission group

Used for

Buyer check

Ad platform access

Campaigns, ad groups, spend, clicks, impressions, conversions, account ids, and date ranges that support spend and performance views.

Confirm the selected ad account matches the client workspace and that downstream revenue sources exist before ROAS or revenue claims appear.

CRM or pipeline access

Contacts, companies, opportunities, stages, owners, source fields, status changes, expected value, and activity dates used in lead progression views.

Confirm stage mapping and source fields before pipeline data is allowed to support attribution, client reports, or source-quality answers.

Form, call, or message access

Submissions, calls, conversations, hidden source fields, timestamps, answered or missed state, and contact context that support intake and lead quality.

Confirm the selected form, tracking account, or message source before treating lead intake as clean enough for dashboards and weekly summaries.

Operations and booking access

Jobs, appointments, bookings, service dates, location context, customer references, operational ids, and status changes used to prove booked work.

Confirm selected location or company scope before booked-work evidence is used in attribution, multi-location reporting, or client-ready reports.

Invoice, payment, and books access

Invoices, totals, collected amount, payment state, customer references, refunds, dates, and accounting ids used to support financial revenue proof.

Confirm financial records are scoped to the right client and date basis before collected revenue, invoice-backed ROI, or exportable proof appears.

Resource

Buyer sees

Readiness rule

Selected account or advertiser

The chosen ad account or advertiser is named before campaign spend and performance data appears in source coverage, dashboard cards, or report proof.

Spend rows can support activity views once the account is selected, but revenue claims wait for downstream outcome records.

Selected form or intake source

The chosen form or intake source is separated from other provider resources so lead rows can be reviewed without mixing unrelated submissions.

Form records can support intake analysis when timestamps and source fields exist; downstream value still needs CRM, job, invoice, or payment evidence.

Selected company, location, or pipeline

The source owner can confirm which company, location, or pipeline SIRJ is reading before records enter client workspace reporting.

Operational records stay scoped to the workspace and need usable status, date, and customer references before attribution or report output depends on them.

Webhook endpoint

A webhook-required connector shows callback setup and active state instead of letting missing event delivery look like weak marketing performance.

Webhook sources do not become current until callback setup and recent delivery health can support the reporting period.

Private source owner

Enterprise and custom connector planning names the source owner, access method, required records, rollout stage, and unsupported states before private data is treated as public coverage.

Private sources stay in custom connector scope until authentication, resources, fields, validation, and reporting role have been approved.

Connector setup should make access, resources, and readiness obvious before data enters reports.

Setup should answer access questions before a source reaches the dashboard.

What does connector setup include?

How are OAuth and API key sources different?

Why does SIRJ ask for selected resources?

What happens when setup is incomplete?

Map each authorization path to the setup work it actually requires.

Permissions should be tied to the proof surface they unlock.

A provider connection is not enough when multiple resources sit behind it.

Move from access request to source-ready proof.

Setup should prevent connected-but-not-ready sources from becoming report claims.

A provider can be authorized while the selected account, form, webhook, pipeline mapping, sync history, or required field is still missing.

Credential values, access tokens, API keys, provider errors, and external labels can create security and trust problems if they leak into UI or public pages.

A broad provider connection can pull the wrong ad account, form, company, location, or pipeline when multiple client resources sit behind one authorization.

Incomplete setup can become misleading when reports fill the gap with smooth-looking charts, broad recommendations, or revenue language the source cannot support.

Connector setup questions buyers ask before trusting connected data.

Does SIRJ show required permissions before setup?

Can a connector be authorized but blocked from reporting?

Where does resource selection happen?

How does setup relate to connector health?

Review the source path before reporting depends on it.

Preparing the source route.

Connector setup should make access, resources, and readiness obvious before data enters reports.

Setup should answer access questions before a source reaches the dashboard.

What does connector setup include?

How are OAuth and API key sources different?

Why does SIRJ ask for selected resources?

What happens when setup is incomplete?

Map each authorization path to the setup work it actually requires.

Permissions should be tied to the proof surface they unlock.

A provider connection is not enough when multiple resources sit behind it.

Move from access request to source-ready proof.

Setup should prevent connected-but-not-ready sources from becoming report claims.

A provider can be authorized while the selected account, form, webhook, pipeline mapping, sync history, or required field is still missing.

Credential values, access tokens, API keys, provider errors, and external labels can create security and trust problems if they leak into UI or public pages.

A broad provider connection can pull the wrong ad account, form, company, location, or pipeline when multiple client resources sit behind one authorization.

Incomplete setup can become misleading when reports fill the gap with smooth-looking charts, broad recommendations, or revenue language the source cannot support.

Connector setup questions buyers ask before trusting connected data.

Does SIRJ show required permissions before setup?

Can a connector be authorized but blocked from reporting?

Where does resource selection happen?

How does setup relate to connector health?

Review the source path before reporting depends on it.