Data Not Syncing
Troubleshoot when data stops appearing in your dashboard.
Identifying Sync Problems
If your dashboard is not showing new data -- new leads are not appearing, ad spend numbers are stale, or transactions are missing -- the issue is almost always related to one of your integration connections. The first step is identifying which integration has the problem.
Check Connection Status
Go to Settings > Connections in the Adsu dashboard. This page shows the real-time status of every connected integration (Meta, GoHighLevel, Google Ads, and Stripe POS). Look for:
- Green -- connected and working normally
- Yellow -- connected but with a warning (e.g., token expiring soon)
- Red -- disconnected or error state
Check Sync Status Page
Navigate to Dashboard > Sync to see the full sync log. This page shows a history of every sync job including when it ran, how many records it processed, and whether it succeeded or failed. Look for recent entries with error status for clues about what went wrong.
Try a Manual Re-sync
On the Sync Status page, click Sync Now to trigger an on-demand sync for the selected location. This runs all connected integrations immediately instead of waiting for the next scheduled sync. If the manual sync succeeds, the issue was likely a temporary glitch.
Reconnect the Affected Integration
If the manual sync fails or the connection status is red, you likely need to reconnect the integration. Go to Settings > Connections and click Reconnect on the affected integration. This initiates a fresh OAuth flow and generates a new access token.
Sync frequencies
Each integration syncs on its own schedule. Here is how often Adsu pulls data from each source:
- Meta ad insights (spend, impressions, clicks) -- every 6 hours
- Meta lead forms -- every 30 minutes
- Google Ads insights (spend, impressions, clicks) -- every 6 hours
- GoHighLevel contacts -- every 30 minutes
- Stripe POS transactions -- every hour
- Matching engine -- every 30 minutes
If data seems delayed, it may simply be that the next sync has not run yet. Use the Sync Now button for immediate results.
Common Causes by Integration
Meta Ads Not Syncing
The most common cause of Meta sync failures is an expired token. Meta long-lived tokens expire after 60 days and must be manually renewed. See the Meta Token Expiry guide for detailed instructions on reconnecting.
Other potential causes:
- Ad account permissions changed -- if your role on the Meta ad account was downgraded or removed, Adsu can no longer access the data. Verify your access in Meta Business Suite.
- Ad account deactivated -- if Meta disabled or restricted your ad account, API access may be blocked. Check your Meta Business Suite for account status alerts.
GoHighLevel Not Syncing
GHL tokens are automatically refreshed by Adsu every hour, so token expiry is rarely the issue. If GHL data stops syncing, check for:
- OAuth revoked -- if someone revoked the Adsu app from your GHL account settings, the connection breaks. Reconnect from Settings > Connections.
- GHL API outage -- GoHighLevel occasionally has API issues. Check their status page or try again in a few minutes.
- Pipeline not configured -- if your location does not have a GHL pipeline mapped in Settings > Funnel, contact stage sync will not run.
Google Ads Not Syncing
Google Ads tokens are refreshed automatically on each API call using OAuth2. If Google data stops appearing:
- OAuth revoked -- if you revoked Adsu's access in your Google account security settings, reconnect from Settings > Connections.
- Customer ID changed -- if you are tracking a different Google Ads account, update the customer ID in your location settings.
Stripe POS Not Syncing
If transaction data stops appearing in your dashboard:
- Stripe disconnected -- the Stripe Connect OAuth connection may have been revoked from the Stripe dashboard. Reconnect from Settings > Connections.
- No recent charges -- if your gym has not processed any payments recently, there is nothing new to sync. Check your Stripe dashboard to confirm charges are coming through.
- Charges not matching -- transactions sync correctly but may not appear attributed if the matching engine cannot link them to a contact. Check the Attribution Gaps guide.
If the Problem Persists
If you have checked the connection status, tried a manual re-sync, and reconnected the integration but data still is not flowing:
- Wait 30 minutes and check the Sync Status page again -- some issues resolve after the next scheduled sync cycle
- Check the browser console for any JavaScript errors when loading the dashboard
- Contact support at support@adsu.ai with the location name, the affected integration, and any error messages from the Sync page
Reconnecting is safe
You can always safely reconnect any integration without losing data. Adsu uses upserts for all sync operations, which means reconnecting and re-syncing will fill in any missing records without creating duplicates. Historical data is always preserved.