Skip to content

Data completeness score (calculated property across key fields)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeEvery 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 mapdata-quality-022
Contact created or a scored field changes leads to Custom code: count how many of 4 fields are known. Custom code: count how many of 4 fields are known leads to Set Data completeness score = passed / 4 x 100. Contact created or a scored field changes Custom code: count how many of 4 fields are known Set Data completeness score = passed / 4 x 100
Contact created or a scored field changes leads to Custom code: count how many of 4 fields are known. Custom code: count how many of 4 fields are known leads to Set Data completeness score = passed / 4 x 100. Contact created or a scored field changes Custom code: count how many of 4 fields are known Set Data completeness score = passed / 4 x 100

When to use it, when not to

Use it

  • Use 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.
  • Use it to prioritize manual cleanup: sort a view by ascending score to find the records that need the most work.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 2 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 1 case, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library