What is data quality? Definition, dimensions and tips.

Every business decision rests on data and its reliability depends entirely on whether the underlying data is accurate, complete and current. When data quality breaks down, so do the models, campaigns and forecasts built on top of it.

Data quality is not simply about having more data. It is about whether the data is reliable and fit for its intended use, whether that means understanding customers, training a model, measuring performance or making a business decision.

In this article, we’ll cover:

• What is data quality?
• What are the core dimensions of data quality?
• Why does data quality matter for business outcomes?
• What are the most common data quality challenges?
• How do you measure data quality?
• What does data quality management involve?
• How do you choose the right approach for your organisation?

Data quality measures how well a dataset meets the requirements of its intended use, covering accuracy, completeness, consistency, timeliness and validity. A customer record missing an email address may be technically present in a database, but it has zero quality for an email campaign use case.

Three roles encounter data quality problems most often. Data engineers discover schema mismatches during pipeline ingestion. Marketers notice audience counts that do not reconcile across tools. Analysts find metric definitions that conflict between dashboards.

Data quality becomes operationally critical the moment a downstream system consumes the data. A predictive model or personalisation engine that ingests low-quality inputs produces outputs that are wrong but appear credible, which is more dangerous than producing no output at all.

Data quality is also distinct from data quantity. A large dataset full of duplicates and stale records can score lower on every dimension than a smaller, carefully maintained dataset. Volume does not compensate for poor data hygiene.

Six dimensions define data quality. Each fails independently and produces a different downstream symptom.

• Accuracy means the data value matches the real-world state it represents. An inaccurate phone number collected at checkout prevents customer service from completing a return call, costing both the relationship and the transaction.
• Completeness means all required fields are populated. A customer profile missing a Postcode cannot be used for geo-targeted offers, shrinking the addressable segment.
• Consistency means the same entity has the same value across every system that stores it. When a customer's birthdate differs between the customer relationship management (CRM) platform and the loyalty platform, neither system can be trusted for age-gated offers or compliance.
• Timeliness (data freshness) means data reflects the current state of the entity. A lead status updated 90 days ago may still show "prospecting" for a customer who signed a contract last week.
• Validity means data conforms to defined formats, ranges and business rules. When refunds are tracked separately, a transaction amount recorded as a negative number in a sales table will inflate reported returns.
• Uniqueness means each real-world entity is represented exactly once. Duplicate customer records inflate audience counts, distort lifetime value calculations and cause redundant communications.

Most production failures span multiple dimensions. A stale address (timeliness) is also an inaccurate address and often incomplete once the current address is unknown. Fixing one dimension frequently surfaces another.

Poor data quality has a direct cost in wasted marketing spend. Campaigns sent to invalid email addresses, churned customers still in active nurture sequences and lookalike models trained on bot-contaminated data all produce lower return on ad spend.

Compliance risk is frequently underestimated. Consent records that are incomplete or inconsistently stored can expose organisations to regulatory action under GDPR and CCPA, not because data was collected wrongly, but because its quality made it impossible to honour a deletion or opt-out request accurately.

Customer experience degrades when personalisation runs on low-quality data. A returning customer addressed by the wrong name or served a recommendation for an item they already purchased, signals that the brand does not know them. That trust erosion is expensive to rebuild.

Analyst trust is a less visible cost. According to Anaconda's 2022 State of Data Science report, data scientists estimated that roughly 40% of their time was spent on data preparation and cleansing. That time produces no analysis, models or recommendations. It is overhead created by upstream quality failures.

Data quality monitoring, the practice of continuously checking data against defined quality rules, separates organisations that catch issues before a campaign launches from those that discover them in a post-mortem.

Data quality issues can arise at any stage of the data lifecycle. Here are some of the most common challenges organisations face:

• Siloed data sources create data consistency failures by design. When the same customer appears under three different email formats across a CRM, an e-commerce platform and a marketing automation tool, no single record can be confirmed as accurate without manual resolution or an identity resolution layer.
• Manual data entry introduces errors that compound at scale. Free-text address fields produce format variations, misspellings and missing components that degrade accuracy and completeness simultaneously.
• Schema drift occurs when upstream systems change their data structure without notifying downstream consumers. A field renamed from "customer_id" to "cust_id" can silently null out an entire downstream column for days before anyone notices.
• AI training data is an emerging concern. A product recommendation engine trained on a dataset with duplicate purchase records will overweight certain SKUs, distorting output in ways that are difficult to diagnose without tracing the error to the source data.
• Lack of data ownership may be the most damaging challenge. When no team is accountable for a dataset's quality, orphaned tables accumulate outdated records with no workflow to trigger updates. Establishing a data stewardship function, even informally, is often the highest-leverage intervention before any tooling investment.

Measurement starts with defining quality rules per dimension and applying them to produce a score. For completeness, a rule might be: "the email field must be populated for 100% of records in the leads table." Running this rule produces a completeness score trackable over time.

Data quality analytics aggregates quality scores across datasets, pipelines and time periods, giving data teams a system-level view of where quality is improving or degrading. This requires ongoing data quality monitoring tied to the systems that produce and consume data.

Six metrics are commonly used in enterprise reporting:

Thresholds vary by use case. A financial ledger requires near-100% accuracy, while a behavioural event stream may tolerate a small percentage of malformed events.

Quality reporting should be connected to the business processes that depend on each dataset. A completeness dashboard for customer profiles should be reviewed by the campaign team, not only by data engineering. Shared visibility creates shared accountability.

Data quality management is the ongoing process of profiling, cleansing, standardising and governing data across its lifecycle. It implies continuous monitoring, defined ownership and a workflow for resolving failures as they arise.

• Data profiling analyses a dataset's structure, content and relationships to establish a baseline. It reveals field population rates, value distributions and referential integrity gaps, answering "What do we actually have?" before "What do we need to fix?"
• Data cleansing removes or corrects records that fail quality rules. Standardisation applies consistent formats, such as phone numbers in E.164 format and addresses validated against a postal authority reference, so records from different sources can merge without creating new consistency failures.
• Data stewardship assigns human accountability at the dataset level. A steward defines quality rules, triages failures and co-ordinates with upstream producers when a source system change degrades quality downstream.

Data quality best practices at the enterprise level include defining quality SLAs for each critical dataset, automating quality checks at ingestion rather than after the fact, logging every failure with enough context to trace it to its source and reviewing quality metrics on the same cadence as operational KPIs.

A data maturity model helps organisations assess their position. At the lowest level, quality problems are fixed reactively after business impact. At the highest, automated pipelines catch and remediate issues before they reach a consumer system.

If your organisation has fewer than three data sources and discovers quality failures manually, start with data profiling and manual stewardship. A spreadsheet tracking quality rules and dataset owners is more valuable at this stage than an enterprise platform with no one to configure it.

If you operate five or more data sources with different schemas and update frequencies, automated data quality monitoring at pipeline ingestion is the minimum viable investment. Manual checks will not scale.

If personalisation or real-time decisioning is a priority, data accuracy and data completeness in customer profiles directly determine the ceiling of what those systems can achieve. Adobe Experience Platform addresses aspects of data quality at the infrastructure level, applying configurable schema enforcement through its Experience Data Model (XDM) and performing identity resolution across ingested data, though organisations may still need separate validation and monitoring patterns to fully ensure data consistency.

If compliance drives the initiative, the completeness and consistency of consent and identity data are the highest-priority dimensions. Evaluate any data quality platform and data quality tools against their ability to enforce rules on consent attributes specifically.

Before selecting a solution, work through this checklist:

1. Have quality rules been defined for each critical dataset?
2. Is data quality monitoring automated or manual?
3. Is there a named owner for each dataset?
4. Are quality metrics reviewed on the same cadence as business KPIs?
5. Does the solution enforce quality at ingestion or only after data has propagated?

Organisations that answer yes to all five are ready for an enterprise-grade solution. Organisations with more than two "no" answers should address governance and ownership first.

To see how schema enforcement, identity resolution and built-in data governance can help to maintain data quality across your customer data, explore Adobe Experience Platform at Adobe Experience Platform.