Common Connection Errors

Ad platform APIs are strict. If a password changes, an account is flagged, or a permission level is downgraded, the platform will immediately reject requests to pull data.

Unlike legacy tools that fail silently or give you a generic “An error occurred” message, Metric Might shows you exactly what the ad platform’s API reported.

If your query fails or a scheduled refresh displays a red warning triangle (⚠), it is almost always due to one of the common issues below.

1. “Failed to Fetch” or Network Errors (Ad Blockers)

Because Metric Might executes queries directly from your browser’s front-end, your browser is communicating directly with graph.facebook.com, googleads.googleapis.com, etc.

If you have an aggressive ad blocker installed (like uBlock Origin, Ghostery, or use the Brave Browser), it may intercept and block these API requests, assuming they are tracking scripts.

How to fix it:

• Disable your ad blocker or “Shields” specifically for app.metricmight.com and docs.google.com (if using the Sheets Extension).
• Metric Might does not run ads or sell your data; whitelisting our domain simply allows your browser to communicate with the reporting APIs.

2. “Token Expired” or “Authentication Failed”

When you connect a data source, the ad platform gives Metric Might a secure “token” to access your data. These tokens routinely expire for security reasons.

• Meta (Facebook) & TikTok: Tokens often expire after 60–90 days, or immediately if you change your password or enable 2FA.
• Google: Tokens rarely expire unless you explicitly revoke access in your Google Account security settings.

How to fix it:

1. Navigate to the Connections tab in the main left-hand menu.
2. Locate the data source that is failing.
3. Click the three-dot menu (⋮) next to the source and select Sign In Again.
4. Log back in to refresh the token. Your queries will instantly start working again.

3. “Permission Denied” or “Insufficient Access”

If you can successfully authenticate the data source, but a specific query fails with a permission error, your user account no longer has the required access level for that specific client’s Ad Account.

This usually happens when an agency client removes your access in their Business Manager, or if your user role is downgraded.

How to fix it:

• Log directly into the ad platform’s UI (e.g., Meta Business Manager or Google Ads MCC).
• Verify that your email address still has at least Analyst or Read-Only access to the specific Ad Account ID you are trying to query.
• If you do not have access in the UI, Metric Might cannot pull the data. You must ask the client to restore your permissions.

4. “Rate Limit Exceeded” or “Too Many Requests”

Ad platforms strictly limit how much data you can pull in a specific timeframe. If you have dozens of heavy queries scheduled to run at the exact same minute, the ad platform (especially LinkedIn or TikTok) might temporarily block the requests.

How to fix it:

• Manual Queries: Wait 60 seconds and click Apply again. The block is usually temporary.
• Scheduled Queries: Metric Might’s backend manages scheduled refreshes automatically. If you notice persistent rate limit failures across multiple scheduled reports, contact support — this may indicate an issue we can help resolve on our end.

What’s Next?

• Why Doesn’t My Data Match? (Troubleshooting timezone and attribution window differences)
• Account Limits Explained (Understanding exactly what counts as an “Account” across different data sources)