{"id":1816,"date":"2024-09-10T19:00:44","date_gmt":"2024-09-11T02:00:44","guid":{"rendered":"https:\/\/salesforcechronicles.com\/?p=1816"},"modified":"2024-09-10T19:03:04","modified_gmt":"2024-09-11T02:03:04","slug":"data-unification-using-identity-resolution","status":"publish","type":"post","link":"https:\/\/salesforcechronicles.com\/?p=1816","title":{"rendered":"Data Unification using Identity Resolution"},"content":{"rendered":"\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"Unify Customer Data with Identity Resolution \u2013 Here&#039;s How!\" width=\"726\" height=\"408\" src=\"https:\/\/www.youtube.com\/embed\/aAMcyOxJ1Wc?feature=oembed\" loading=\"lazy\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<p>In this post, we continue our deep dive into Salesforce Data Cloud, moving from data mapping to the next crucial step identity resolution. We\u2019ll walk through the key steps and best practices for effective data unification, using practical examples.<\/p>\n\n\n\n<p><strong>What is Identity Resolution?<\/strong><\/p>\n\n\n\n<p>When you gather data from multiple sources like CRMs, marketing systems, or third-party tools you may end up with duplicate or fragmented records for the same customer. Identity Resolution helps solve this by merging data from various sources into one complete, accurate profile for each customer or account.&nbsp;<\/p>\n\n\n\n<p>With Salesforce Data Cloud, identity resolution focuses on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li> Matching records across different data sources.<\/li>\n\n\n\n<li> Resolving conflicts to decide which information to prioritize.<\/li>\n\n\n\n<li> Creating unified profiles for each customer or account.<\/li>\n<\/ul>\n\n\n\n<p>Let\u2019s walk through the four critical steps of identity resolution:<\/p>\n\n\n\n<p>1. Validate Your Data<\/p>\n\n\n\n<p>Before you even begin the identity resolution process, it\u2019s essential to ensure that the data you\u2019ve imported into Salesforce Data Cloud is clean and ready for matching. Using the Data Explorer tool, check whether your data has been properly ingested and harmonized. This step saves you from running into errors down the road.<\/p>\n\n\n\n<p>2. Set Up Match Rules<\/p>\n\n\n\n<p>Match rules are key to identifying which records belong to the same customer. These rules allow you to determine how strict or flexible your matching process should be. For example, you can match based on First name, Email address, Phone number.<\/p>\n\n\n\n<p>The more fields you include in the match rules, the stricter the matching will be. However, if you use fewer fields, you increase the chances of creating a unified record but also run the risk of mismatches. It&#8217;s all about striking the right balance!<\/p>\n\n\n\n<p>3. Configure Reconciliation Rules<\/p>\n\n\n\n<p>Once the system matches records, reconciliation rules help determine which data to keep when there are conflicts. For instance, if two systems have different email addresses for the same customer, the reconciliation rule will decide which one should be retained. <\/p>\n\n\n\n<p>4. Run the Identity Resolution Job<\/p>\n\n\n\n<p>After configuring your match and reconciliation rules, you\u2019re ready to run the Identity Resolution Job. Once the job is complete, you can review the Identity Resolution Summary&nbsp;&nbsp;to see how records were merged. This summary will also show the consolidation rate, which gives you insights into how effective your rules were in unifying the data.<\/p>\n\n\n\n<p><strong>An Example: Techron Group\u2019s Identity Resolution<\/strong><\/p>\n\n\n\n<p>To better understand the process, let\u2019s look at a practical example using Techron Group , a fictional company. Our goal is to unify their customer data from multiple sources into one clean, accurate profile.<\/p>\n\n\n\n<p>1. Start by logging into Salesforce, and navigate to the Data Model tab Use the graph view to examine the relationships between profile objects like Individual and Contact Point.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"460\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-5.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1817\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-5.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-5-300x153.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-5-768x391.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"418\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-6.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1818\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-6.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-6-300x139.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-6-768x355.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n<\/div>\n\n\n<p>2. Create a New Identity Resolution Rule Set:<\/p>\n\n\n\n<p>Select Individual as the primary data model object. Set up match rules using fields like first name, email, and birth date. You can adjust\u00a0\u00a0the precision to decide how strict the matching should be.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"464\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-7.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1820\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-7.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-7-300x154.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-7-768x394.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"468\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-8.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1821\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-8.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-8-300x155.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-8-768x398.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<p>3. Add Match Rules:<\/p>\n\n\n\n<p>\u00a0\u00a0For instance, configure how records should be merged using attributes such as first     name, last name, email, or phone number.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"464\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-9.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1822\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-9.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-9-300x154.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-9-768x394.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<p>4. Add Reconciliation Rules:<\/p>\n\n\n\n<p>\u00a0\u00a0\u00a0 For example, you may want to prioritize the CRM email address over other data     sources to ensure that the most relevant data is used in the unified profile.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"464\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-11.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1824\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-11.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-11-300x154.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-11-768x394.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<p>5. Validate Results:<\/p>\n\n\n\n<p>Run the Identity Resolution Job and review the results. In this case, we created 496 unified profiles with a consolidation rate of 12%. Reviewing the unified records shows that they were merged correctly, and the data is now clean and consolidated.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"466\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-12.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1825\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-12.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-12-300x155.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-12-768x396.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"904\" height=\"464\" src=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-13.png\" loading=\"lazy\" alt=\"\" class=\"wp-image-1826\" srcset=\"https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-13.png 904w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-13-300x154.png 300w, https:\/\/salesforcechronicles.com\/wp-content\/uploads\/2024\/09\/image-13-768x394.png 768w\" sizes=\"auto, (max-width: 904px) 100vw, 904px\" \/><\/figure>\n\n\n\n<p><strong>What Happens After the Identity Resolution Process?<\/strong><\/p>\n\n\n\n<p>Once the identity resolution process is complete, Salesforce creates Unified Objects that store the merged data. These include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unified Individual<\/li>\n\n\n\n<li>Unified Account<\/li>\n\n\n\n<li>Unified Contact Point<\/li>\n<\/ul>\n\n\n\n<p>Each of these unified records consolidates all the relevant information from various data sources into one clean profile. In addition, Salesforce creates Unified Link Objects that store the history of how records were merged. For example, the Unified Link Individual Object records which individual data entries were combined to form a unified profile.<\/p>\n\n\n\n<p><strong>Best Practices for a Successful Identity Resolution Process<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ensure that data has been successfully ingested and accurately modeled from your source systems into Salesforce Data Cloud.<\/li>\n\n\n\n<li>Develop unification strategies that effectively integrate all necessary data sources using the best-suited methods<\/li>\n\n\n\n<li>After setting up your ruleset, confirm that the summary statistics and unified profiles align with expectations based on your source data.<\/li>\n\n\n\n<li>Create different Identity resolution rulesets to compare the consolidation rate<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>In this post, we continue our deep dive into Salesforce Data Cloud, moving from data mapping to the next crucial step identity resolution. We\u2019ll walk&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[26],"tags":[],"class_list":["post-1816","post","type-post","status-publish","format-standard","hentry","category-data-cloud"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts\/1816","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1816"}],"version-history":[{"count":2,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts\/1816\/revisions"}],"predecessor-version":[{"id":1834,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=\/wp\/v2\/posts\/1816\/revisions\/1834"}],"wp:attachment":[{"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/salesforcechronicles.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}