What counts as a filled field
Every fill rate in MarqIQ — in the audit, in Field intelligence and in an Ask — uses one definition of filled. This article states it, so a number that says “71% filled” means the same thing wherever you read it.
The definition
A field is filled when it holds a value that is not empty, not only spaces, and not the literal words null or undefined. Those two words are what some tools, exports and imports write into a field that was never set, and a person reading the record would not call them a value.
- Filled: “Inbound”, “0”, “false”, “none”, a date, a number.
- Empty: nothing, spaces only, null, NULL, undefined — in any case, with or without spaces around them.
Where it applies
- Field intelligence and the Integration Audit: the fill rate of every field, and which fields are worth using.
- Data audit: the field-completeness table and the value lists under each field.
- Ask: the fill rate measure, and any grouping — a record whose field holds the word “null” sits under (not set), never under a group called “null”.
One deliberate exception
A filter’s is empty condition matches nothing, or spaces only — not the words. It mirrors the filter you build in a report, which reads a stored “null” as a value you can see and remove. To find those records, filter on equals “null”.
What changed on 2026-09-28
Before this date the words null and undefined counted as filled in the audit’s field-completeness table and in some readers, and as empty in Field intelligence. If a completeness figure moved down slightly after this date, that is why: the records did not change, the definition did.
Related articles
Was this article helpful?