Fix Missing Data
Responses not showing up? Run through this checklist
Most missing data? It's a filter or settings mismatch. Quick to diagnose, quick to fix. Run through this checklist.
Check Your Streams
Check that you're viewing the correct Location or Website in the sidebar. If the wrong one is selected, you will see data from elsewhere -- or nothing at all.
If your Stream's end date has passed, it will no longer collect responses. Open the Stream, go to the Settings tab, and extend the End date under Schedule this Stream.
Check the Reporting Dates
The dates in the date picker must cover the period when the Stream was actually live and collecting responses. If you are looking at a week when the Stream did not exist yet, there is nothing to show.
Clear Your Browser Cache
Sometimes stale cached data prevents new results from appearing.
- Log out of Ombea.
- Clear your browser cache (Chrome · Edge · Safari).
- Log back in at insights.ombea.com.
Check the Hardware
If your dashboard settings look fine, the issue might be on the device side.
Low or dead batteries can stop the device from recording or sending data — even if the screen still looks normal. If the device has been running for several months, swap in fresh D-cell batteries. See Change ExpressPod Batteries.
Check the LED indicator. If it's blinking or off, the device may have lost its cellular connection. See ExpressPod 4G Connectivity Issues for a full walkthrough.
Press each button and watch for the beep and LED flash. If nothing happens, the touch sensor may need attention. See ExpressPod Not Responding to Touch.
If the tablet lost its Wi-Fi connection, it can't send data. Check the Wi-Fi settings on the device and reconnect if needed.
A simple power cycle solves most sync issues. See Reboot Your ExpressPod or Reboot Your ExpressTab.
Still Nothing?
If none of the above helps, contact support@ombea.com with:
- The device serial number (on the back of the unit).
- The Location and Stream name you expect data for.
- The date range when data is missing.
We'll trace the issue from our end.
Was this helpful?