There are six top-level considerations to address in any data strategy for building a SCV database.
1. Establish business goals
Any data strategy should begin with top-level business objectives: How does each team currently use customer data, and what do they want to achieve with that data? This process involves input from teams across an organization, as the data will ideally be available to all stakeholders. So begin by ensuring everyone understands how single customer views can benefit their team and elicit input on how they envision using the tool.
2. Determine data sources
Teams should log all potential data sources for the single customer view and how data from those sources can be centralized. Data sources can include information from platforms that handle customer relationship management, e-commerce, social media, sales, website hosting and analytics, marketing automation, in-store sales, and product usage metrics. Industry-specific platforms such as those that handle ticketing, reservations, and financial transactions are often added to the mix. Remember, the more customer data sources collected, the more accurate and useful single customer views will be.
3. Set compliance guidelines
Data collection is governed by various state and national laws, as well as industry regulations. Companies must ensure the way they collect and store customer data complies with the relevant standards, such as the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and the Health Insurance Portability and Accountability Act (HIPAA).
4. Ingest, model, and clean data
Single customer views are typically housed in a centralized database such as a data warehouse or packaged customer data platform (CDP). That means finding a way to link the source data platforms with the centralized database so the data can be ingested and aggregated.
Teams make use of data modeling to address data hygiene, ensuring that the data is accurate, deduplicated, consistently formatted, and free from irrelevant information.
Then the data must be integrated, ensuring that each record represents a unique customer and that all the data related to that customer is included in that record, a process known as identity resolution. Identity resolution reconciles different records about the same customer. While it is a complex process, the functionality is built into most customer data platforms.
After the initial data is ingested into a database of single customer views, it must also be updated regularly. This involves a bi-directional connection between the database and its data sources through a process called “extract, transform, and load” (ETL), or its sister process, “extract, load, and transform” (ELT).
5. Access, analyze, and activate data
A single customer view database is only useful if teams across an organization know how to use it. Ideally, the user interfaces for analyzing and using — or “activating” — the data for marketing activities will be intuitive and easy for non-technical users to work with. That means its integration with existing platforms should be seamless.
6. Institute data governance
A single customer view is only as good as the data it contains. Data governance is the set of procedures for collecting, storing, accessing, and using data. Data governance models document how data will be kept up to date, compliant, and accurate, and that it’s stored securely. Whether SCVs are stored in a data warehouse or a traditional CDP, platform administrators will apply these procedures as new data sources are added and old ones are deprecated.