A customer data platform (CDP) maintains unified customer records over time for other systems to use.
Before choosing another platform, identify a customer question your present view cannot answer and the information needed to answer it. Start the evaluation with that question.
Name the question and selected sources
Write down what the intended view needs to answer before assessing a platform. List the sources chosen for that question, what information you expect from each and where you would check it. A list of available connectors does not establish that your selected records have arrived.
The CDP Institute’s definition includes responsibility for customer identity and record structure. It allows services delivered natively or composed from external systems, including data warehouses.
A fictional venue record plan
Imagine a venue combining ticket-sale and refund entries into a maintained customer record for an internal service view. In this invented plan, entries carry customer and booking references.
| Source entry | Intended contribution | Check before use |
|---|---|---|
| Ticket sale. | Booking linked to customer reference. | Original sale remains visible. |
| Related refund. | Refund linked to same booking. | Refund source retained. |
| Missing reference. | Customer link unresolved. | Investigate before linking. |
Use the intended contribution column as a requirement to inspect. It is not evidence that a connection has run. Ask who can trace the selected entry and check what the service view actually displays before relying on the refund status.
Separate a coverage gap from a customer fact
If the selected refund source is absent, leave the refund question open. An empty place in this view cannot establish that the customer never received a refund. Identify the missing source or unresolved relationship instead of replacing uncertainty with a negative statement about the customer.
Keep the record’s intended scope with the review. Ask when the relevant source was updated and whether the displayed information is suitable for the question being asked. A useful note states what was checked and what still needs investigation, rather than calling the view complete.
Compare requirements before architecture labels
When evaluating a proposal, ask which part is missing: information from a source, a supported customer relationship or a destination that can use the result. Request evidence for that specific connection. Packaging alone does not answer those questions, so compare the proposed arrangement with the requirement it is meant to satisfy.
For a conversation handoff, ask whether a colleague can understand the current request and earlier context in the relationship record. The questions can overlap without requiring another product.
Choose the unresolved connection to inspect
Return to the question the proposal was supposed to answer. If the intended view already supports it, identify any remaining requirement before recommending another platform. If it does not, name the missing evidence and who will investigate it. The venue’s refund question needs that answer before a purchasing argument.