Troubleshoot a provider connection
Distinguish authorization, API eligibility and incorrect website mappings.
Last reviewed
- Who can use this
- Owner, Admin, Finance, Viewer within their assigned sites
On this page
A connection error can come from the upstream provider's permissions as well as Brightstone's form. Review the safe error before replacing credentials.
Identify the failure
- Missing Google account/property/network: check the signed-in Google identity and its reporting access.
- Rejected publisher token: verify the token, client/account ID and required publisher API eligibility.
- API disabled or unavailable reporting: ask the relevant provider/project administrator to enable the required access.
- Connected but empty: check the selected site, dates, synchronization and reporting scope.
Do not use advertiser credentials where publisher revenue access is required. Do not reuse an account-wide total for several independent sites. Revcontent and Outbrain currently have blocked general reporting adapters, so normal reconnect attempts cannot establish unavailable upstream reporting.
Recover safely
Reconnect the existing integration after fixing its actual prerequisite. Preserve the website and historical records unless you deliberately intend to remove them. Repeatedly submitting a valid Google consent screen will not fix a disabled network API.
Share the provider name, approximate time and customer-safe error wording with support. Never include an API key, client secret, bearer token, raw private API response or a screenshot showing credential fields. Provider account approval and API permissions must come from the provider, not from a Brightstone demo.
If these steps do not resolve your question, contact Brightstone support. Never include passwords, tokens or recovery codes.
Contact support →