Why does my Metabase dashboard filter show the wrong number of visits?

The Metabase help pages give 3 common reasons. The first to rule out: If a column used by a filter changes in the database, the filter can stop working, so a filtered visit count can drop or go blank.

What causes it?

  1. If a column used by a filter changes in the database, the filter can stop working, so a filtered visit count can drop or go blank.

    In the Metabase help: If a column changes on the database side, the filter might suddenly stop working. Troubleshooting filters, read 2026-11-12.

  2. When Metabase reads a column's values or type differently from how they are stored, a filter on that column can fail to work.

    In the Metabase help: If we make the wrong assumptions about a column’s values or data type, the filter won’t work at all. Troubleshooting filters, read 2026-11-12.

  3. Filter choices are refreshed on a scan schedule, so new values in a busy table can be missing from the list for a while.

    In the Metabase help: You might see outdated filter values if your tables are getting updated more frequently compared to your scan schedule. Troubleshooting filters, read 2026-11-12.

How do I check it myself?

  1. Check that the question behind the dashboard card includes the column the filter uses.

    In the Metabase help: Make sure the question includes the column you want to filter on. Troubleshooting filters, read 2026-11-12.

  2. Check that the column's data type suits the filter, for example that dates or numbers are not stored as text; changing a column's type can need an admin.

    In the Metabase help: Cast the column to a data type that matches the desired filter type. Troubleshooting filters, read 2026-11-12.

  3. Open the dashboard in a private browser window to rule out an old copy kept by your browser.

    In the Metabase help: Open your question or dashboard in an incognito window. Troubleshooting filters, read 2026-11-12.

How does Metabase work with Feder?

  • Connect Metabase to Feder and it joins your Visits apps.
  • When you connect Metabase, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See whether you can trust the numbers in Metabase, one of your Visits apps. Feder only reads. It never changes anything in Metabase.

Where do these answers come from?

Every cause and check on this page comes from the Metabase help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.