Connectors keep your data flowing — ad spend, store orders, payments, and more — but every connection relies on credentials and permissions that can change over time. This page helps you read each connector's health at a glance, understand what a "reconnect required" prompt means, and fix the most common sync problems yourself.
Read your connector health
Open the Connectors page to see every platform you've connected and how it's doing. Each connected platform shows four things:
| Indicator | What it tells you |
|---|---|
| Status | Connected, disconnected, or error |
| Last Sync | When data last synced successfully |
| Data Flow | How many records synced in the last 24 hours |
| Errors | A count of recent sync errors, if any |
A healthy connector shows Connected, a recent last-sync time, and no errors. A warning or error icon on a card is your cue to investigate that connector.
Build a weekly habit
Glance at the Connectors page once a week. Catching a stalled sync early — before a reporting deadline — is far easier than reconstructing missing data after the fact.
"Reconnect required" — what it means and how to fix it
Ad-platform connections (Google Ads, Meta Ads) authorize UMAP360 to read your data on your behalf. That authorization is renewed automatically in the background, so you normally never think about it. Two things can interrupt it:
- The authorization was revoked — someone removed UMAP360 from the platform's connected-apps list, or the platform itself invalidated the grant. When this happens, UMAP360 notices on the next sync and surfaces a Reconnect required notification automatically. The connector is paused so it stops retrying (and stops wasting your account's API quota) until you reconnect.
- The authorization expired — Google and Meta sign-ins are renewed periodically, and occasionally one needs a fresh approval.
To fix it: click the connector, choose to connect/re-authorize again, and sign in to the platform. Once you grant access, syncing resumes on its own.
One unreachable account won't take down the whole connector
If UMAP360 simply can't reach one specific ad account (for example, a permissions gap on that single account), that connector shows an error state but stays connected — your other accounts keep syncing. This is different from a revoked authorization, which pauses the whole connector.
Common problems and fixes
Connector shows "Disconnected"
- Click the connector and sign in / re-authorize again.
- For API-key connectors (email, WhatsApp, analytics, and similar), check that your keys or credentials haven't expired in the provider's own dashboard.
Data isn't syncing
- For webhook-based connectors (Shopify, Razorpay, Segment), confirm the webhook URL you pasted into the third-party platform is correct.
- Check the connector's error details for a specific failure message.
- Make sure your network or firewall allows outbound connections to the provider.
Duplicate data is appearing
- Check that you don't have the same event configured under multiple webhooks.
- Review your field mapping for duplicate mappings.
A sync just failed
When a sync fails, the Connectors page shows an alert icon with error details. Common causes:
- Expired or revoked credentials — re-authenticate, or regenerate the API key.
- Rate limiting from the provider — these syncs retry automatically; reduce sync frequency if it keeps happening.
- Scope or permission changes — the provider may need you to re-authorize with updated permissions.
- Network timeouts — usually transient and clear up on the next sync cycle.
You can always trigger a manual re-sync from the connector's settings panel, and the connector's sync history and error log are there for a closer look.
Credentials are write-only
For security, UMAP360 never shows you saved credentials again — when you edit a connector, the credential fields are blank and you re-enter them. Your saved credentials stay encrypted; rotating your API keys periodically is still good practice.
When to get help
If a connector still fails after you've re-authenticated and confirmed the credentials are valid in the provider's dashboard, reach out with the connector name, the error message, and the timestamp — that detail helps support pinpoint the issue quickly.
Next steps
- New to connectors? Start with Connecting your data: overview.
- Setting up or reconnecting an ad platform: Connect ad platforms.
- Stores and payments: Connect your store and payments.
- Anything deeper, or a problem this page didn't cover: Troubleshooting & support — or contact us.
Last updated 2026-06-11