Mar Dat
Insights

One Customer, Two Databases, Half the Truth

June 22, 2026 · Mar Dat

One Customer, Two Databases, Half the Truth

B2B and B2C are how companies organize. They are not how people live.
Let me introduce you to a customer your database probably doesn’t know very well.
At work, she helps make purchasing decisions for her company. At home, she is a retail customer.
She used her corporate email to download a business guide, her personal email to join the loyalty program and her mobile phone when she contacted customer service.
Your B2B system calls her a contact. Your commerce platform calls her a shopper.
Your service platform calls her a case. Your marketing platform may have two subscriber records for her.
None of those records is necessarily wrong. Together, they are still incomplete.
The customer thinks she has one relationship with your brand. Your company may believe it has four relationships with four different people.
That disconnect is becoming harder to ignore.

Companies love categories. People are inconveniently whole.

The separation between B2B and B2C data made sense when organizations first built these systems.
The B2B team needed accounts, contacts, opportunities and longer buying cycles.
The consumer team needed transactions, loyalty activity, digital behavior and high-volume campaigns.
Sales bought one platform. Marketing bought another. Commerce kept its own order history.
Service managed customer issues somewhere else. Each team organized information around the job it needed to do.
The problem is that customers move across those categories all the time. A consumer customer becomes a business buyer. A corporate contact makes personal purchases.
An employee changes companies. A small-business owner uses the same product at work and at home.
We built our systems around departments and then acted surprised when the customer came out fragmented.

What happens when every team has part of the truth

When identities remain disconnected, each team makes decisions using the part of the relationship it can see.
Marketing may treat a loyal customer like a brand-new prospect.
Sales may not know that an account contact has been purchasing personally for years.
Service may not realize that the person calling about a problem also manages an important business relationship.
Analytics may divide the same person’s revenue and engagement across several profiles.
The company sees fragments. The customer expects recognition. Imagine being a longtime customer who decides to evaluate that same brand for your company.
You submit a business inquiry. The first email explains who the brand is. The salesperson asks questions the company should already know.
Your consumer promotional emails continue as though nothing else is happening.
Inside the company, everything may be functioning as designed.
From the customer’s perspective, a familiar brand has suddenly developed amnesia.

A unified profile is not a giant data landfill

When companies hear “unified customer profile,” the instinct is sometimes to put every available piece of information into one enormous record.
That isn’t the goal. A useful unified profile helps the business understand how records and relationships connect. It doesn’t erase the systems that created them or pretend every piece of data has the same purpose.
Commerce may remain the authority for order information. The CRM may own the business account relationship.
A consent or privacy platform may remain the authority for certain preferences. A service platform may own the case history.
The unified view helps the organization recognize that these records may belong to the same person and understand how the relationships fit together.
It gives the business context. It should not strip the context away.

Recognition and permission are different things

This is one of the most important parts of the conversation. Knowing that two records belong to the same person does not automatically give the company permission to use every piece of information in every interaction.
A work email and a personal email may serve different purposes. A person may agree to receive transactional messages but not promotions.
Consent may differ by brand, channel, address and type of communication. Someone may have a consumer relationship with the company without agreeing to have that activity used in a corporate sales conversation.
Identity resolution answers one question:
Do we believe these records belong to the same person?
Consent answers another:
What are we allowed to do with that knowledge?
Those questions should never be treated as though they are interchangeable.
A better customer view should make the company more thoughtful, not more intrusive.

B2B and B2C describe selling motions

I understand why companies still need different B2B and B2C strategies.
The sales cycles are different. The decision-makers are different. The communications are different. The economics are different.
But B2B and B2C describe how a company sells. They do not describe the full life of the customer.
The same person can belong to a household, influence a corporate purchase, own a small business and participate in a loyalty program.
A unified profile should help the organization understand those relationships without flattening the individual into a generic “customer” label.
The goal isn’t one customer, one message. It’s knowing enough about the relationship to choose the appropriate message.
Sometimes that will be a professional communication tied to an account.
Sometimes it will be a personal message related to a recent purchase.
Sometimes it will be a service response. And sometimes the appropriate decision will be to say nothing.

Try the ten-customer test

Before building another segment or identity framework, choose ten real customers who are likely to exist in more than one system.
Don’t begin with millions of records. Begin with ten people. For each person, ask: 
How many profiles can we find?
Which email addresses and phone numbers are connected to them?
Are they associated with an account, household or employer?
Which system owns each piece of information?
What consent has been captured, and for what purpose?
Would sales, marketing, service and commerce describe this person the same way?
What would happen if the customer changed jobs tomorrow?
You will learn a great deal from those ten profiles.
You may discover that the company can match the person but cannot represent the relationship.
You may find that consent is stored separately from the channels using it.
You may see that the customer has been counted as both an existing customer and a new prospect.
You may also find that everyone has been using the phrase “customer 360” without agreeing on what anyone actually needs to see. That is useful information.

Start with the decisions, not the data volume

Most organizations do not need more customer data.
They need greater clarity about the data they already have.
What does the business need to know to provide a better experience?
Which relationships affect eligibility, service or sales prioritization?
Which source should be trusted when records disagree?
Which information should each team be allowed to see?
What should happen when identity confidence is low?
Those decisions should shape the unified profile.
Otherwise, the organization may spend a great deal of money creating a more complete view without knowing what anyone is supposed to do with it.

Show me one real person

At Mar Dat, I don’t need ten million records to begin an identity conversation.
Show me one person who has a work email, a personal email, a purchase history and a relationship with a business account.
Show me how marketing sees him. Then show me what sales, commerce and service see.
We can learn more from one complicated customer than from a hundred slides describing a perfect future state.
Book a profile working session with me at Mar Dat. Bring one customer your systems see as several different people, and we’ll map what the business knows, what it is missing and what it has permission to do. 

Next in the series
Recognizing the customer is a major step forward. Recognizing her tomorrow may still be too late. In the final article, we’ll talk about the moments that have a clock on them.

Ready to talk about your agents?

Tell us what you want your team to hand off, and we will map the first agent with you.