Marketing Cloud problems often begin long before the first journey goes live.
One of the most important decisions is also one of the easiest to underestimate: how the business identifies a person.
In Salesforce Marketing Cloud, that decision is often expressed through the Contact Key. To a technical team, it can sound like a configuration detail. To the business, it becomes the foundation for recognition, reporting, consent, segmentation, journey history and future platform change.
When that decision is weak, the consequences rarely appear immediately. The first few journeys may still work. Messages may still send. Campaigns may still launch. But as the environment grows, the cost starts to show.
Reports become harder to reconcile. Preferences become harder to enforce. Customers appear in more than one place. Teams lose confidence in whether they are speaking to the same person across different journeys, products or channels.
That is why identity design is not a technical afterthought. It is one of the most important Marketing Cloud decisions a business makes.
The mistake is treating Contact Key as a setup field
The Contact Key is often decided during implementation pressure. A team needs to get the first audience loaded, the first journey built and the first campaign sent. Someone chooses an identifier that appears to work: an email address, a CRM ID, a lead ID, a quote ID, a customer number or another operational key.
The problem is not that any one of those is always wrong. The problem is choosing one without understanding what it means for the operating model.
An email address may change. A lead ID may represent an enquiry, not a person. A quote ID may represent a transaction, not a customer. A customer number may work well for known customers but not for prospects. A CRM contact ID may not exist for every record entering Marketing Cloud.
Each choice carries a trade-off.
If the trade-off is not understood, the business may unknowingly build journeys around an identity assumption that does not hold up at scale.
Identity design decides what the system can understand
Marketing Cloud is not only sending messages. It is also building a memory of interactions.
That memory depends on identity.
If the same person enters through different product journeys, different quote processes, different forms or different channels, the system needs a clear way to decide whether those records belong together or should remain separate.
Without that clarity, the same person can become multiple marketing contacts. The business then has to ask awkward questions.
- Did this person already receive a related message?
- Which version of the person has the latest details?
- Which record owns the valid consent state?
- Which journey history should be used for reporting?
- Which identifier should be used if the environment later connects to Data Cloud or Marketing Cloud Next?
Those questions cannot be solved properly inside one campaign. They require an identity model.
The wrong key can make reporting look unreliable
Reporting problems are often blamed on dashboards, but identity is frequently underneath the issue.
If the Contact Key does not represent the person in a way the business understands, reporting becomes harder to interpret. Engagement may be split across multiple records. Conversion may sit against a transaction while message history sits against a contact. Suppression may happen at one level while performance reporting happens at another.
The result is not always a broken report. It is worse: a report that needs explanation every time it is used.
When leadership asks how many people engaged, the answer should not require a technical caveat about how many identifiers were involved. When marketing asks whether someone converted after a journey, the answer should not depend on manual matching across disconnected records.
A weak identity model makes every performance conversation harder.
Preference management depends on the same decision
Consent and preference handling also depend on identity.
If a person opts out of email, blocks a WhatsApp message, re-subscribes through a later interaction or changes their mobile number, the system needs to know what that signal applies to.
Does the preference apply to the email address? The mobile number? The customer? The lead? The quote? The product line? The channel?
These are business rules, not only technical mappings.
A poor Contact Key decision can make preference management fragile because the system cannot confidently connect the preference signal to the correct person or communication context.
That is where teams start adding manual suppression lists, one-off exclusions and campaign-specific checks. Those workarounds may protect one send, but they do not create a dependable operating model.
The decision affects future migration options
Many teams only discover the importance of identity when they need to modernise.
A business may want to introduce newer Salesforce capabilities, prepare for Marketing Cloud Next, connect richer customer data, improve segmentation or build a stronger cross-channel operating model. Suddenly, the old Contact Key decision becomes a constraint.
If the environment was built around a transaction identifier, it may struggle to support a person-level engagement model. If it was built around email address, it may struggle when mobile-first or multi-channel communication becomes more important. If it was built around a CRM record that only exists for part of the audience, the business may struggle to include all relevant customer journeys.
Migration is easier when the current identity model is clear. It is harder when nobody can explain why the original decision was made.
The practical question is how the business recognises a person
The right starting point is not “what field is available?”
The better starting point is: how does the business need to recognise a person across communication, consent, reporting and future data use?
That question forces the right discussion.
- Is the business communicating with prospects, customers or both?
- Can one person have multiple product interactions?
- Can one person hold multiple policies, quotes, applications or subscriptions?
- Which system is most reliable for person-level identity?
- Which identifier is stable over time?
- How should anonymous, prospect and customer stages be handled?
- What will future reporting need to count: sends, records, opportunities, quotes, customers or people?
Those answers shape the identity model. The Contact Key should support that model, not accidentally define it.
A stronger identity model creates calmer delivery
When identity is designed properly, Marketing Cloud becomes easier to operate.
Teams know which record represents the communication relationship. They understand how preferences are applied. They can explain reporting with fewer caveats. They can build reusable journey patterns because the underlying assumption is stable. They can prepare for future architecture decisions with less rework.
That does not mean every organisation needs a perfect customer data platform before it can send a journey. It means the identity decision must be deliberate.
A practical identity model is better than an accidental one.
Questions every business should ask before scaling Marketing Cloud
- What does the current Contact Key represent?
- Does it represent a person, a transaction, an enquiry, a CRM record or something else?
- Can one person appear under more than one key?
- How does the Contact Key affect consent and suppression?
- How does it affect reporting and conversion analysis?
- Would the same decision still make sense if the business added more channels?
- Would it support future Marketing Cloud Next or Data Cloud planning?
- Is the decision documented well enough for a future team to understand it?
If these questions are difficult to answer, the environment may already be carrying identity risk.
Business takeaway
Identity design is one of the most important Marketing Cloud decisions a business makes.
The Contact Key decision shapes reporting, preference management, segmentation, journey history and future migration options. If the business does not decide how it recognises a person, the platform will make that decision by default.
That is rarely where good architecture comes from.
How Cloud Genii helps
Cloud Genii helps organisations stabilise and improve Salesforce Marketing Cloud environments by clarifying the foundations before scaling the journeys.
That includes identity design, audience structure, consent and suppression handling, reporting visibility, journey logic, monitoring and the operating model needed to keep Marketing Cloud understandable after delivery.