Why a metric has no data
Platform availability, account/post scope, selected date range, page permissions, collection delay, external posts versus MediaFox posts, and widget-specific limits.
Der redaktionelle Inhalt dieses Artikels ist derzeit auf Englisch verfügbar. Die Navigation des Hilfe-Centers ist lokalisiert.
Überblick
Platform availability, account/post scope, selected date range, page permissions, collection delay, external posts versus MediaFox posts, and widget-specific limits. Use this guide to isolate the cause safely before repeating the action. Reporting dashboards combine selected pages, date ranges, metrics, widgets, exports, and saved presentation choices.
Identify the symptom
Platform availability, account/post scope, selected date range, page permissions, collection delay, external posts versus MediaFox posts, and widget-specific limits. Note the exact point where the actual behavior differs from what you expected.
Do not repeatedly submit, delete, publish, reconnect, or purchase while the result is uncertain. First verify whether the previous action completed in another tab, activity list, Audit Log, or external platform.
Checks to make in order
Start in Reporting & Analytics in the organization navigation. Keep the affected item open where possible so you can compare the state after each check.
- Check 1: Platform availability
Review platform availability and choose the value that matches your intended result.
- Check 2: Account/post scope
Review account/post scope and choose the value that matches your intended result.
- Check 3: Selected date range
Review selected date range and choose the value that matches your intended result.
- Check 4: Page permissions
Review page permissions and choose the value that matches your intended result.
- Check 5: Collection delay
Review collection delay and choose the value that matches your intended result.
- Check 6: External posts versus MediaFox posts
Review external posts versus MediaFox posts and choose the value that matches your intended result.
- Check 7: Widget-specific limits
Review widget-specific limits and choose the value that matches your intended result.
Safe recovery
After correcting the cause, refresh the page and repeat the smallest safe action that can prove the workflow works. The issue is resolved when the dashboard, widget, metric, or export reflects the selected scope and current data availability.
If a retry could publish, delete, charge, revoke access, retire a public address, or send a message twice, contact an owner or support instead of guessing.
- Check the dashboard date range, selected pages, platform support, and the metric scope.
- Allow recently connected pages or bulk platform reports time to complete data collection.
- For exports, review freshness requirements, supported widget types, permissions, and destination configuration.
If you still need help
Send support the organization name, route, affected item ID, timestamp and timezone, exact message, screenshot, and reproducible steps. Include the relevant System Status or Audit Log entry when available.
Never send passwords, verification codes, cookies, access tokens, API keys, payment details, or other secrets.
Verfügbarkeit und Zugriff
Die Verfügbarkeit hängt von deinem Organisationszugriff und deinen Berechtigungen ab.