Outcome. Every contact carries a single completeness percentage across the fields your team actually relies on, so segmentation, reporting, and cleanup prioritization stop depending on eyeballing which fields are blank.
Workflow map
Enrollment, branches and actions at a glance
data-quality-022
flowchart TD
A[Contact created or a scored field changes] --> B[Custom code: count how many of 4 fields are known]
B --> C[Set Data completeness score = passed / 4 x 100]
When to use it, when not to
- UseUse it when several different fields matter for a contact to be usable, such as a working email, a phone number, a job title, and a lifecycle stage, and you want one number to sort or filter by instead of checking each field separately.
- UseUse it to prioritize manual cleanup: sort a view by ascending score to find the records that need the most work.
- SkipDo not use it as a lead-scoring substitute. This measures whether fields are filled in, not whether the contact is a good fit or ready to buy. Keep it separate from HubSpot's lead scoring properties.
- SkipDo not use it with more than around eight to ten fields in the calculation; beyond that the score becomes hard to act on and the custom code gets harder to maintain. Pick the fields that actually drive a decision downstream.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
