Data Hygiene
Marketing automation data hygiene
Keep contact data dependable for marketing automation by defining field values, matching imports, checking email eligibility and resolving exceptions.
Marketing automation data hygiene keeps contact data reliable enough for a workflow's next decision. Identify fields that identify a contact, select a path or decide whether an action may proceed. For each, define acceptable values, an owner, and what happens when a value is missing, conflicting or out of date.
Find the fields that change an outcome
Trace a campaign from entry to final action. At each decision, ask which data it uses and what happens if that data is wrong. A field used only in a report may need a different check from one that selects a customer message.
| Data question | Decision to record |
|---|---|
| Which contact is this? | Which identifier matches an incoming record to an existing one? |
| Which path applies? | Which values are accepted, and what happens to blanks or conflicts? |
| May the action proceed? | Which eligibility and suppression checks apply at that point? |
| Did the update work? | Where will the resulting record or action outcome be checked? |
Keep a short register for each important field: source, owner, accepted values and update rule. If two systems can change it, decide how conflicts are resolved. A two-way connection alone does not determine which value is right.
Control values where they enter
Align form choices and import mappings with the values the destination accepts. For example, a team might use NSW, VIC and Other for a state field. These are illustrative internal choices; connected systems must agree on their meaning and mapping.
Entry validation does not cover every update route. HubSpot documents property validation rules for certain field types, but says these are not enforced for workflow updates or submissions through legacy forms.
Check every route that can write a consequential value, then inspect the resulting record. Send an unfamiliar value for review rather than silently turning it into an approved option.
HubSpot validation rules can be set on custom and default text, date and number properties, and they apply when editing or importing data. Examples include restricting an Order Number text property to numeric characters or a Payment amount number property to two decimal places.
Existing values are not retroactively formatted. Setting rules requires edit property settings permissions; regex custom rules require a Professional or Enterprise subscription.
Data sync field mappings control which properties sync, in which direction, and how conflicts are handled. HubSpot supports two-way mappings for matching types such as text to text, number to number, and dropdown select to picklist.
Some types map one way only, for example a HubSpot number or date picker mapped as text to a third-party text field. Review default mappings before customising them; Data Hub Starter, Professional and Enterprise accounts can create and customise mappings.
HubSpot Property Validation Rules: Supported Field Types and Restrictions
- Field Type
- Text
- Validation Example
- Restrict to numeric characters (e.g., Order Number)
- Field Type
- Number
- Validation Example
- Enforce two decimal places (e.g., Payment amount)
- Field Type
- Date
- Validation Example
- Format must match system date standard (e.g., DD/MM/YYYY)
Two-Way vs One-Way Data Sync: Pros and Cons
- Two-Way Sync (e.g., text to text)Pros: Real-time updates across systems. Cons: Risk of conflicts if both sides update independently.
- One-Way Sync (e.g., HubSpot number → third-party text)Pros: Predictable direction; less conflict risk. Cons: Limited bidirectional feedback.
Match contacts before updating them
Choose a supported identifier for each incoming batch or connection. Confirm how the import tool or platform uses it to match records for updates; matching rules can vary between file imports, connectors and platforms.
Check repeated keys within a batch, missing identifiers, and keys that point to different existing contacts. An email address can change, so it should not be treated as a permanent identity in every case.
Keep a source reference and an import or sync reference for disputed updates. After processing, compare intended creates and updates with destination records and errors. HubSpot's import tool can display error details and, where available, recommended fixes.
Import files must be .csv, .xlsx or .xls and contain one sheet, a header row matching properties, fewer than 1,000 columns, and UTF-8 encoding if they include foreign language characters. Excel date and time picker cells must be in Number format.
During mapping you can fix incorrect or missing values without re-uploading. The tool can replace a column value across every row where it appears or exclude it from import.
Pre-Import Data Hygiene Checklist for HubSpot
- File Format.csv, .xlsx or .xls
- Single Sheet RequiredYes
- Header Row Matching PropertiesMust match HubSpot property names
- Excel Date/Time FormatMust be in Number format
Check email separately
Before an email action, confirm the intended contact has an address in a format the sending system accepts. Review known bounce or send restrictions and current eligibility for that message. A plausible address does not prove that a mailbox exists or that delivery will succeed.
For Australian commercial electronic messages, consult current ACMA guidance on avoiding spam. Recheck eligibility close to the action if a workflow waits between entry and send.
Validation rules can cover the default Email property alongside other contact properties such as First Name, Last Name and State/Region. They enforce format at entry; use them with, not instead of, send restrictions and eligibility checks.
ACMA Guidelines on Spam Avoidance for Australian Commercial Electronic Messages
- Key Requirement
- Recipient must have given consent to receive messages
- Required Action
- Include a functional unsubscribe mechanism
- Prohibited Practice
- Sending messages without clear sender identification
Resolve recurring exceptions
Give each failed check a reason, owner and outcome: correct the source, request clarification, retain the existing value or exclude the record from that action. Review missing values, disputed matches, rejected options and held email actions alongside the affected records. If the same error keeps arriving, repair its source or mapping.
Before release, define expected outcomes for a valid value, a blank, an unexpected option, a repeated identifier and a changed address. Compare those expectations with the configured system. A preview or a successful batch count alone cannot confirm the final record or send outcome.
HubSpot's automation issues view lists workflows where enrolled records have encountered errors. Super Admin or Workflows permissions are required to view them. You can mark an issue Fixed, Ignored or Deferred. Deferred sets a reminder if the issue recurs after a chosen number of days, weeks or months, or until a specific date.
Resolving Recurring Automation Exceptions in HubSpot
- Step 1Identify the error type (missing value, invalid option, duplicate key)
- Step 2Assign an owner for resolution (e.g., data steward, team lead)
- Step 3Choose outcome: correct source, request clarification, retain existing, or exclude record
- Step 4Use HubSpot’s Automation Issues view to mark as Fixed, Ignored, or Deferred
In this guide
- Keeping contact field values consistent across systemsDefine field meaning, accepted values, ownership and mapping rules so contact updates remain usable across connected marketing systems.
- Preventing duplicate contacts during automated importsChoose a contact match key, catch conflicting rows before import and reconcile creates and updates to prevent duplicate records.
- Validating an email field before a workflow uses itCheck the intended contact, email format, known send restrictions and current eligibility before a marketing workflow sends.
