Connector auth errors

Symptoms

• A connector shows Authorization failed, Token expired, or a red error state in Settings → Connectors.
• A previously working connector stops syncing and the Last synced timestamp goes stale.
• After authorising, VisibilityIQ reports Insufficient permissions or No properties found.

Connector auth errors mean VisibilityIQ can no longer exchange data with the external service. Auth credentials live entirely inside the connector and are stored encrypted — they are never logged or exposed — so the fix is almost always to re-issue a token, not to recover one.

Likely causes

• Expired OAuth token. Refresh tokens can be invalidated by the provider after a long idle period, a password change, or a security event on the Google/Microsoft account.
• Revoked access. Someone removed VisibilityIQ from the account’s third-party app list, or the granting user lost access to the property.
• Insufficient role. The connecting account was downgraded and no longer holds the required permission level on the property.
• Wrong account. You authorised with a Google/Microsoft account that doesn’t own the property you expected.
• First-sync lag. A freshly connected connector hasn’t completed its initial sync yet — this is not an error.

How to fix it

1. Re-run the OAuth flow. Go to Settings → Connectors, click Disconnect next to the affected connector, then click Connect and complete consent again. This issues a fresh token. Historical data already synced is preserved and the connector resumes from its last checkpoint rather than re-pulling everything.
2. Confirm your access level. Re-consent only succeeds if the account holds the right role:
   • GSC — Owner or Full User on the property.
   • GA4 — Viewer or higher on the property.
   • Bing — admin access to the Webmaster property. Sign in to the relevant console, verify the role, and reconnect with a sufficiently privileged account if needed.
3. Resolve “No properties found”. After authorising, VisibilityIQ found no properties on that account. Confirm you signed in with the correct account, that the property exists and is verified in its console, and (rarely) that you haven’t hit Google’s unverified-app limit during API review.
4. Check for a revoked grant. In the Google account’s Security → Third-party access (or Microsoft equivalent), confirm VisibilityIQ is still authorised. If it was removed, reconnecting restores it.
5. Give a new connector time. Data can take up to 24 hours to appear after first connecting. Treat it as a problem only past 48 hours.

Connected but no data syncing

If a connector shows Connected but nothing arrives after 48 hours, check the Last synced timestamp. If it’s more than 48 hours old, disconnect and reconnect to force a fresh token and sync. Google’s Search Console and Analytics APIs also have daily quota limits; running many projects and connectors under one Google account can occasionally exhaust them. If you suspect quota exhaustion, contact support.

Still stuck?

If reconnecting doesn’t restore the sync, email support@visibilityiq365.com with your project domain and the connector name. For Google-specific consent-screen, scope, or redirect-URI problems, see Google OAuth setup problems. If a connector is connected but downstream findings or rankings are missing, see Audit shows no issues or empty results and Missing rank data.