Looking Beyond the Golden Record: Unified Profiles in Salesforce Data Cloud

This post is a collaboration between Derrick Ellis, Director Success Architect — Data Cloud Customer Success & *Stanislav Georgiev, Director Product Management — Data Cloud Identity @ Salesforce.*

It’s time to talk about Data Cloud’s unified profile. We know what you’ve been thinking — this is your new customer master, your shortcut to that perfect ‘golden record.’ If you’re nodding along with this statement, it’s time to reset some of your expectations. We’re going to take some time to help you really understand the unified profile, enabling you to leverage it effectively in your enterprise architect designs.

In discussions with customers, architects, and partners on these topics, we’ve found that many don’t understand the difference between a golden record and a unified profile. Sometimes this discovery makes them worry that they won’t be able to use unified profiles how they intended. Don’t worry, Data Cloud’s unified profile can still help you meet your business needs — you just have to use it differently than you might be thinking. You’ll be OK and you might just get excited by all of the potential! Ready? Let’s do it!

Let’s start with some basic concepts to build a shared foundation for our discussion. By the end, you’ll see unique ways the Unified Profile can benefit your business. We’ll also hint at future articles exploring Data Cloud’s relationship to your master data management (MDM) strategy. There’s a lot to cover, but we have to start somewhere! In this blog post, we’ll focus on four things.

(1) Data Cloud as a system of reference (2) The mutability of the unified profile (3) The key ring model versus the golden record approach (4) Additional advantages of this model

Spoiler Alert: Data Cloud’s Unified Profile is NOT a golden record and that’s a good thing!

Data Cloud is a System of Reference

By now you’ve heard that Data Cloud brings all your customer data together to give you a single view of your customer. Data Cloud should be ingesting data from every system of record you have, bringing all those master data fragments together to find relationships between them and surface that crucial single view. Important to note, Data Cloud isn’t becoming your new system of record; it’s using data from your existing systems to find connections between those disparate data sets.

With such varied customer data, how does Data Cloud find relationships? First, you map the different datasets to a common set of objects (data model objects, aka DMOs) and fields, harmonizing all data models into a single shared model within Data Cloud. Next, you explore data across systems, using the rules you set in identity resolution to link records, thus allowing you to uncover new insights, patterns, and trends.

Figure 1: Data Cloud’s Unified Profile does not master data, it links existing data together based on the relationships found through identity resolution.

The unified profile isn’t taking over your data mastery; it’s helping you discover the full view of your customer across all of the records you already have! Additionally, because each record’s data lineage is preserved in the Unified Profile, you can trace every bit of information back to the original system of record. That’s why Data Cloud is a system of reference.

Data Cloud’s Unified Profile is Mutable

Data Cloud’s unified profile is designed to evolve and improve automatically as your customer data evolves and improves. Your data isn’t perfect (don’t worry, we won’t tell anyone!). Some of your systems of record need quality spring cleaning and data stewardship. Can you still bring flawed or incomplete data into Data Cloud? Absolutely! How else can we help improve things and provide unique insights? Most systems have messy data — but the data you bring doesn’t have to be of the highest quality data to help your business.

Your customer data will change over time, becoming more complete, accurate, and robust through customer actions or structured internal data quality efforts. As identity resolution incorporates the latest data from various systems of record and the relationships between fragments of master data change and improve, your unified profiles also evolve. This mutability ensures you always have the latest and best unified profile that can be built from your customer records. For example, two records that were once related to different unified profiles might now be linked through a single unified profile after the latest identity resolution run.

Figure 2: The relationship between source records and the Unified Profile can change over time.

What does this mean for the UUID (the Unified Profile’s ID)? It means you shouldn’t use it as a permanent ID in your external applications — it’s not your new Subscriber Key or Customer ID! Using an old UUID means missing out when your profiles are updated with the latest updates to your data, leading to an outdated single view of the customer.

Unified profiles prioritize accuracy first and stability second. Will the makeup of each unified profile’s set of linked records change constantly? No. But some relationships will change with each run. To take advantage of improvements in your unified profiles, your model needs to support this reality. Don’t worry, these changes to unified profiles won’t be random, and they’re always based on the rules you give to identity resolution. Expect shifts based on factors like data quality changes in source records, new data source, new records, and changes to your identity resolution match and reconciliation rules.

We know what you’re thinking, “If the unified profile can change for any given source record, how can we use the profile?” It’s time to talk about the key ring.

Unified Profile as Key Ring, not a Golden Record

When people think about distributed customer data fragments, they often conclude that they must have a single golden record for each customer to handle different email addresses, phone numbers, or missing information like birthdates or middle names. This can be one way to approach your customer information challenge, and many enterprise MDM solutions are designed to help with this.

A golden record is the result of mastering the “best” single value (or values) for all customer attributes across the enterprise. Activating that golden record often means propagating the winning values to original source systems, overwriting losing values that originated in those systems, or it means setting up a central service to query the golden record for the best values. Designing and implementing solutions for this model takes significant time and compromise to align all business and IT stakeholders. Consensus is hard-won and involves decisions around business logic for survivorship, merges, splits, and the use of the golden record.

Data Cloud’s unified profile isn’t attempting to determine the single best values for customer attributes or to propagating “winning” values. Instead, it focuses on discovering relationships across your fragmented customer data and linking those records together. The goal is to build a holistic view of your customer, not to merge the data into a single “best” record.

Enter the Key Ring Think of the unified profile as a like you think of the ring of keys in your pocket. Suppose your key ring holds a car key, a house key, and a USB key. These keys are linked together because they belong to the same person. Each key is unique and interacts with a specific external system to perform a specific function.

Let’s say you have a truck and an SUV — each with its own key on your key ring. Would it make sense to pick the best vehicle key and use it for both? Can the truck key unlock or start the SUV? Can the USB key unlock your house’s front door? Of course not. Each key has a specific purpose, value, and set of information associated with it. Like your key ring, the unified profile holds multiple keys, each with its own purpose.

Figure 3: Keys on a Key Ring have specific value, purpose and set of information associated with them.

Extending this metaphor to a key’s related information — how important is it to understand the context and lineage of that data? Both of your vehicles have a key fob for remote starting. The truck’s fob shouldn’t remote start the SUV — that’s specific key-related information. But what if we aggregate related data at the key ring level? Can we activate based on that?

Consider related data for each vehicle’s remote start capabilities, such as fuel level, door lock status, and proximity to the operator. You need to be close to the vehicle for remote start to work. Does your proximity to the truck matter if you want to start the SUV? No. Does the SUV’s fuel level matter if you’re trying to start the truck? Of course not. This remains true even if both vehicles are the same make, model, and year.

In this example, it’s clearly incorrect to pick the best vehicle, best fuel level, latest door lock status, or average proximity without considering the proper context — specifically, which vehicle the data is related to. Ideally, we would keep all the data’s context (it’s lineage) intact and maintain the mastered information and relationships associated with each key. This is what Data Cloud’s unified profile does: it retains the full mastered dataset and the relationships for each key linked by the key ring.

It can be useful to know if you have “2 vehicles” or if you tend to fully fuel your vehicles or wait until they’re almost empty. These are potential Data Cloud Calculated Insights, aggregate insights built from data related all the keys on your profile. We could segment unified profiles associated with more than one vehicle, but when activating or surfacing data to a customer, we drill down to the key-specific level. These unified insights drive significant business value, deeper customer understanding, advanced support interactions, and even loyalty and marketing strategies. However, the primary means of engaging with the customer remains the relationship of the actual data to its specific context. We want you focus on context-specific activation.

Looking at Data Cloud’s unified profile, the key ring doesn’t contain 2 vehicle keys, a house key, and a USB key. Suppose a particular unified profile holds various records (with IDs) from Marketing, Service, Sales, Commerce, POS, Order Management, and other systems of record across your enterprise. Each key will have a full set of related data specific to that key ingested into Data Cloud along with it. Sometimes the data contains a single key from each system, and sometimes it may contain several keys from a single system.

A Word about Duplicate Data We know what you’re thinking — “several keys from a single system on the same unified profile? Bad data! We need Data Cloud to dedupe.” Okay, take a breath. First, understand that Data Cloud isn’t designed to dedupe your data — remember, we aren’t picking winners; we’re linking. Second, while some systems might have bad or unintentional duplicate customer records, it’s also possible that some systems intentionally create multiple records that appear to be the same person. This doesn’t mean you did a bad job; it might be the right choice based on that system’s data model or workflow rules.

Figure 4: The Unified Profile’s Key Ring will often have many keys; sometimes multiple keys from each system

For example, Marketing Engagement excels at tracking subscriber key-level (contact point) details, but its data model doesn’t support more than one email address per contact. The same goes for active mobile numbers in SMS campaigns. If a customer has multiple contact points, you’ll end up with multiple subscriber keys. These aren’t duplicates; they’re the best way to track that data in Marketing Engagement.

Each subscriber key has specific context — like business unit, personally identifying information (PII), subscription status, and engagement history, including knowledge of current journeys for that subscriber key. These details are specific to the mastered subscriber key-based data and don’t generalize across multiple subscriber keys. This is how Marketing Engagement can have multiple subscriber keys linked into a single unified profile, with each referencing a specific contact point. In practice, this might result in different Subscriber Keys for your work and home email addresses — each has its own distinct related PII and subscription preferences that have been explicitly set by the customer.

B2C Commerce often lets customers check out as guests, meaning they don’t log in or connect a profile to the order. This requires mapping the Order object in B2C Commerce to both the Sales Order and Individual DMOs in Data Cloud, so the guest can be registered as an Individual on the unified profile. Linking these individual records enables valuable insights, like lifetime value inclusive of both logged-in and guest checkouts, driving strategy across commerce, loyalty, and marketing. Arbitrarily deduping these mapped Individuals would be counterproductive, as we might need to send a back-in-stock notification, order status update, recall notice, or other important communications. These actions should rely on the mastered data lineage rather than some mashed-together record from a bunch of separate systems. The shipping address from a guest order should be used in the context of that specific order, rather than picking a “winner” address from all addresses the customer has used.

Figure 5: Unified Profile insights can come from an aggregate view, but through the Key Ring, you can trace back to the specific Order record to find the right shipping information, the product purchased, the transaction date, and other details.

Key Ring’s Magic: Unified Link DMOs The unified profile’s key ring (found in the Unified Link DMOs) offers the best of both worlds: it maps relationships between source records to retain the full data lineage of those records and their related data. You can use the unified profile to drive aggregate signals, understanding, views, and segmentation while carefully activating along system of record-defined sets of mastered data. One of Data Cloud’s biggest strengths is its ability to engage directly with operational and transactional systems using keys those systems understand, driving business workflows and engagement. Can you use these views to improve your data stewardship efforts? Absolutely! Take a look at the AppExchange for Data Cloud-native stewardship applications. To be clear, Data Cloud can’t magically fix everything — each system of record has different business requirements and stakeholders with specific logic to incorporate into the process. One size definitely doesn’t fit all!

This flexibility and value potential is made possible by the unified profile’s key ring model. As discussed, a golden record’s survivorship decisions involve complex business logic to pick the best values across systems and stakeholders. Data Cloud’s identity resolution includes a process called “Reconciliation” — which sounds like survivorship and even generates a single Unified Individual (or Unified Account) DMO with values picked from the set of keys on the unified profile. This resulting DMO can be useful as metadata to describe the key ring. For example, this set of keys belongs to Derrick and has these attributes. Are those attributes ‘the best’? No. They are simply a heuristic, an at-a-glance way to describe that specific unified profile. They aren’t meant for mastering a new golden record — and they won’t always be the “best” values to activate, because “best” always depends on the context in which a value is needed.

When are these reconciled views useful? Architecturally, you can access these values via the Profile API with very low latency. They are valuable for use in a Lightning Web Component header block (an at-a-glance summary view of basic characteristics) for the unified profile. They can also label or describe some of the aggregate Calculated Insights you’ve generated at the unified level. However, the real value lies in the Unified Link DMOs, where you access the underlying key ring. You may surface those reconciled attributes to quickly describe the unified profile, but should follow up by loading specific keys to provide a more nuanced, lineage-based view. Traversing the key ring is also important when you are forwarding actionable data to your internal users and when you’re exposing PII directly to your customers.

Other Advantages of Data Cloud’s Key Ring Model

Using both the aggregate insights of the Unified Individual and the full lineage and context of your data makes your control in activation incredibly valuable. Beyond honoring the context and mastery of your existing systems of record, there are further advantages:

• Alignment with decentralized data reality: Data Cloud’s key ring design aligns with your existing enterprise landscape, promoting insights without disrupting data ownership structures.
• Smoother organizational adoption: This model reduces friction and resistance within your company by linking identifiers rather than overhauling data structures, streamlining cross-functional buy-in.
• Scalability and adaptability: The key ring model simplifies the addition of new systems or updates to existing ones, enhancing scalability and adaptability in a dynamic enterprise environment.
• Faster integrations: This approach speeds up integrations by connecting to any enterprise data source without requiring cleansing or pre-processing, removing common blockers.
• No survivorship conflicts: The key ring model avoids debates and conflicts over survivorship and reconciliation logic, yielding faster consensus and smoother implementations.
• Reduced life-cycle complexity: By focusing on identifier mapping rather than data attribute consolidation, maintaining the key ring (unified profile) is simpler and less complex over time.

In Conclusion

Phew! That was a lot to cover, but it was necessary. Let’s revisit where this journey started: “We know what you’ve been thinking — this is your new customer master, your shortcut to that perfect ‘golden record.’” By now, you should be shouting, “No! It’s a key ring!” The advantage of this model is that it never overwrites your mastered data but links those fragments or records together, providing the best of both worlds — preserving the full, intact data lineage for your customer data and creating critical insights from across the unified profile. Use those unified profile-based calculated insights to drive deeper understanding and power internal dashboards, business intelligence, segmentation, or outreach strategies based on a single view of your customers. When you activate or engage a customer directly, use the right key and that key’s related data in the right context (or in the right system).

This combination of the unified profile and easily access to system-specific related customer data gives you tremendous flexibility and removes the implementation barriers that typically accompany survivorship or mastery-oriented solutions.

With your new understanding of this powerful system and the value it provides, you’re ready to have better follow-up conversations within your company and design quality solutions that take advantage of this value proposition to address your business’ needs. Data Cloud’s relationship to your master data management strategy is another topic worth exploring in-depth, but we’ll tackle that in another post.