![\"Image\"](\"https:\/\/www.artefact.com\/\/wp-content\/uploads\/2023\/12\/Nurbakyt-Kulbatshayeva-300x300.jpg\")
Customer Data Platform<\/h2><\/div>Customer Data Platform (CDP) allows businesses to collect, manage, and analyze customer data from various sources in a unified and centralized manner. The goal of a CDP<\/strong> is to create a comprehensive and cohesive view of each customer by aggregating data from multiple touchpoints<\/strong>, such as websites, mobile apps, social media, email interactions, and more.<\/p>\n<\/div>Treasure Data<\/h2><\/div>![](\"https:\/\/www.artefact.com\/\/wp-content\/uploads\/2023\/12\/image-1-article-medium-SQL-TD.png\" "\\"image")
<\/span><\/div>Treasure Data is a cloud-based Customer Data Platform. Here are some common business use cases for Treasure Data:<\/p>\n<\/div>
- <\/i><\/span>\n
Customer Data Analysis.<\/strong> Treasure Data can be used to aggregate and analyze customer interaction data. This helps businesses create a unified view of customer behavior and preferences.<\/p>\n<\/div><\/li>- <\/i><\/span>\n
Personalized Marketing.<\/strong> By leveraging the customer inisghts gathered through Treasure Data, businesses can create personalized marketing campaigns. This includes targeted messaging, personalized recommendations, and tailored offers based on individual customer profiles.<\/p>\n<\/div><\/li><\/ul>ID reconciliation<\/h2><\/div>ID reconciliation is a process in which data related to a person is compared and matched across different systems or databases to ensure accuracy, consistency, and a unified view of that person.<\/p>\n<\/div>
This is particularly important in scenarios where multiple systems or data sources store information about the same individuals, but the data may be incomplete or inconsistent.<\/p>\n<\/div>
The challenge of ID reconciliation<\/h2><\/div>ID reconciliation encounters numerous challenges, especially with extensive datasets and diverse information sources. These challenges include inconsistent data formats, quality issues leading to false matches, and the management of duplicate records resulting from errors or system changes. The key challenge is the lack of a unique ID<\/strong> representing the user accross the different sources of information, tables and databases.<\/p>\n<\/div>Organizations address these challenges by investing in advanced data tools like Treasure Data.<\/p>\n<\/div>
ID reconciliation implementation<\/h2><\/div>We implemented ID reconciliation for one of our clients using Treasure Data Unification functionality. In this article we want to share our approach and implementation logic.<\/p>\n<\/div>
Given conditions:<\/strong> in CDP databases there were available tables with information about the user journey on the website, as well as customer information from the CRM (Customer Relationship Management) database in data warehouse.<\/p>\n<\/div>The goal<\/strong> is to have a unique profile identifier in each CDP table. This will allow us to create a Master Segment with a 360 degree view on the customer and its journey.<\/p>\n<\/div>Online data available:<\/strong> views on website pages, form submissions on website, other website specific information, such as product page details that are stored in the separate table.<\/p>\n<\/div>Offline data available:<\/strong> CRM data from the data warehouse.<\/p>\n<\/div>
Customer Data Platform (CDP) allows businesses to collect, manage, and analyze customer data from various sources in a unified and centralized manner. The goal of a CDP<\/strong> is to create a comprehensive and cohesive view of each customer by aggregating data from multiple touchpoints<\/strong>, such as websites, mobile apps, social media, email interactions, and more.<\/p>\n<\/div> Treasure Data is a cloud-based Customer Data Platform. Here are some common business use cases for Treasure Data:<\/p>\n<\/div> Customer Data Analysis.<\/strong> Treasure Data can be used to aggregate and analyze customer interaction data. This helps businesses create a unified view of customer behavior and preferences.<\/p>\n<\/div><\/li> Personalized Marketing.<\/strong> By leveraging the customer inisghts gathered through Treasure Data, businesses can create personalized marketing campaigns. This includes targeted messaging, personalized recommendations, and tailored offers based on individual customer profiles.<\/p>\n<\/div><\/li><\/ul> ID reconciliation is a process in which data related to a person is compared and matched across different systems or databases to ensure accuracy, consistency, and a unified view of that person.<\/p>\n<\/div> This is particularly important in scenarios where multiple systems or data sources store information about the same individuals, but the data may be incomplete or inconsistent.<\/p>\n<\/div> ID reconciliation encounters numerous challenges, especially with extensive datasets and diverse information sources. These challenges include inconsistent data formats, quality issues leading to false matches, and the management of duplicate records resulting from errors or system changes. The key challenge is the lack of a unique ID<\/strong> representing the user accross the different sources of information, tables and databases.<\/p>\n<\/div> Organizations address these challenges by investing in advanced data tools like Treasure Data.<\/p>\n<\/div> We implemented ID reconciliation for one of our clients using Treasure Data Unification functionality. In this article we want to share our approach and implementation logic.<\/p>\n<\/div> Given conditions:<\/strong> in CDP databases there were available tables with information about the user journey on the website, as well as customer information from the CRM (Customer Relationship Management) database in data warehouse.<\/p>\n<\/div> The goal<\/strong> is to have a unique profile identifier in each CDP table. This will allow us to create a Master Segment with a 360 degree view on the customer and its journey.<\/p>\n<\/div> Online data available:<\/strong> views on website pages, form submissions on website, other website specific information, such as product page details that are stored in the separate table.<\/p>\n<\/div> Offline data available:<\/strong> CRM data from the data warehouse.<\/p>\n<\/div>Treasure Data<\/h2><\/div>
<\/span><\/div>ID reconciliation<\/h2><\/div>
The challenge of ID reconciliation<\/h2><\/div>
ID reconciliation implementation<\/h2><\/div>
![](\"https:\/\/www.artefact.com\/\/wp-content\/uploads\/2024\/01\/image-2-article-medium-SQL-TD.png\" "\\"image")
<\/span><\/div>![](\"https:\/\/www.artefact.com\/\/wp-content\/uploads\/2024\/01\/image-3-article-medium-SQL-TD.png\" "\\"image")
<\/span><\/div>![](\"https:\/\/www.artefact.com\/\/wp-content\/uploads\/2024\/01\/image-4-article-medium-SQL-TD.png\" "\\"image")
<\/span><\/div>![](\"https:\/\/artefact.com\/\/wp-content\/uploads\/2021\/03\/medium.png\" "\\"medium\\"")
<\/span><\/div>