Before You Build Another Dashboard, Write the Metric Contract 

A dashboard cannot settle an argument the business has never resolved. 

Ask three teams how many “qualified leads” the company generated last month and you may get three perfectly defensible answers. 

One team counts after form validation. Another count after sales accepts the lead. A third counts after a conversation. 

The problem is not necessarily bad reporting. 

It may be an undefined metric. 

This is why customer journey analytics should begin with meaning before visualisation. 

The metric contract takes five minutes to understand 

Before connecting another source, write down five things: 

Question	Example
What are we calling it?	Qualified enquiry
What event creates it?	Sales accepts a valid request
What excludes it?	Test, duplicate, invalid contact
Which date counts?	Acceptance date
Who owns the definition?	Revenue Operations

That is the metric contract. 

It does not need legal language or another committee. It simply gives everybody the same rule. 

Without that rule, customer data integration can bring information together while leaving the disagreement untouched. 

Connected data can still produce conflicting answers 

Suppose marketing, CRM and finance data all reach one customer insights platform. 

Great. 

Now ask: when did the conversion happen? 

At the original enquiry? The sales qualification? The order? The payment? 

All those events can belong to the same customer journey. 

They are not the same business event. 

Good customer journey analytics keeps those stages visible instead of collapsing them into one convenient number. 

This becomes especially important when leaders ask apparently simple questions such as: Which activity created revenue? 

That answer depends on the definition of revenue, the attribution rule, the time period and which customer event can reliably be connected. 

One number does not have to answer every question 

Businesses often create reporting problems by expecting one metric to satisfy several teams. 

• Marketing wants to understand demand. 
• Sales wants to understand opportunities. 
• Operations wants completed work. 
• Finance wants recognised value. 

Those are related views of the business. They are not interchangeable. 

A useful customer insights platform should help connect them while preserving what each stage actually means. 

The goal is not to force every department to use the same number. 

The goal is to make the relationship between the numbers understandable. 

Where customer data integration actually helps 

Once definitions are agreed, customer data integration becomes far more useful. 

It can help connect an enquiry to the CRM record, the CRM record to an order, the order to fulfilment and the eventual financial outcome. 

Then the business can answer richer questions: 

Which enquiries became accepted opportunities? Which accepted opportunities became completed transactions? Which sources produced customers rather than just activity? 

This turns customer journey analytics from reporting into a way of understanding progression. 

A metric contract also needs exceptions 

Real data is messy. 

Refunds happen. Orders get cancelled. Records are duplicated. Customers change details. One system may record an event later than another. 

Do not hide these cases just to make the dashboard look clean. 

Define how they are handled. 

A trustworthy customer insights platform should make unresolved records visible rather than silently pretending every record connected perfectly. 

Where WeAddo bridges the gap 

WeAddo’s data capabilities can help bring business information together, standardise definitions and create reporting views across connected customer and operational events. 

But technology should come after the decision: What exactly are we trying to know? 

Before you commission another dashboard, choose one disputed number from your next leadership meeting. 

Write the five-line metric contract. 

You may discover that the reporting problem starts long before the chart.