The best time to invest in your first-party data set was yesterday. The second best time is today. Here are principles you can follow to build your first-party data strategy and details on how a Customer Data Platform can help.
Although attention is often focused on a business’s end product, great teams set themselves apart by mastering the supply chain. Henry Ford, for example, revolutionized the automotive industry with the release of the Model T in October, 1908. The model T was not the fastest or the safest car on the market, but its production efficiency allowed it to be listed at an extremely affordable price, making automotive travel accessible to the masses for the first time.
Many teams today, however, do not just sell cars and do no not operate factories. They write code, and deliver digital experiences through mobile apps. Mobile experiences are driven not by the assembly of chassis and axles, but by data. Think of the personalized recommendations from Netflix, or the seamless push notifications from Airbnb. These experiences are built upon the ability to collect, organize, and activate data. They are the result of a different kind of assembly line–as Harvard Business Review recently coined it, a data supply chain.
Supply chains must evolve with the market, and your data supply chain is no exception. While many brands have relied upon third-party data and cross-app data to power campaigns and measure engagement, new market shifts, such as Apple’s App Tracking Transparency, are forcing teams to change their strategies. To evolve your data supply chain and optimize your mobile experiences, you need to master your first-party data strategy.
How to build your first-party data strategy
As with building cars, there are multiple steps to delivering data-driven experiences. An effective, privacy-conscious first-party data strategy must account for the entire data lifecycle, from collection, to management and storage, to activation.
Salesforce’s 2020 State of the Connected Customer reported that 83% of consumers are concerned about sharing personal data and 72% would stop buying from a company or using a service because of privacy concerns. To successfully collect first-party data, you must create a data transaction that provides value for the customer and ensures trust by communicating transparency of use and responsible data governance.
In Responsible Marketing with First Party Data, Boston Consulting Group (BCG) notes that advanced teams have followed three best practices when asking to track customer data.
Visibility: They don’t hide banners, they design the ask with a neat user interface, and they make it easy to withdraw permission by giving users control
Candor: They are upfront about the reasons for collecting data and the benefits of collection and usage
Value: They highlight the incentives, such as a better customer experience, that comes from sharing data
Customer data can no longer be handled unknowingly. It is a privilege that must be earned through trust, and constantly re-earned through secure data governance.
Different types of companies connect with their customers in different ways. Brands with a direct relationship with their users, such as retail, financial services, and travel, have built their value exchange upon exclusive offerings, such as member-only content and loyalty programs.
Companies in industries such as Consumer Packaged Goods (CPG) and Automotive often do not sell directly to consumers. These companies can build up their first-party data set by reaching their end customers with auxiliary digital offers. For example, the Weber charcoal grill I just bought arrived including a QR code to download their mobile app. The app is packed with 3D set-up instructions, grilling tips and recipe recommendations that have helped me avoid setting the house on fire.
Media and publishing companies in particular have been heavily reliant on third-party data, as many use third-party cookies to deliver ads through a Data Management Platform (DMP) and other Ad Tech solutions. As third-party tracking becomes more restricted, it will be important for publishers to invest in infrastructure that allows them to take ownership of their first-party data collection and use it to deliver relevant ad experiences to their readers. Certain publishers have already led the way in this transition, such as the New York Times, which is investing in first-party audiences and data science insights to power their advertising campaigns. You can read more about their progress so far here.
In addition to the challenges of building customer trust are the technical challenges of collecting first-party data on mobile. Every tool that you collect first-party data into requires a Software development kit (SDK) implementation in your client side app. With the average enterprise using dozens of marketing and analytics tools, excess vendor code can quickly impact load time and app stability.
Customer Data Platforms (CDPs), such as mParticle, help by simplifying your first-party data collection. CDPs ingest all customer data from your app through an SDK implementation or API connections, and then enable you to connect it out to any of your marketing, analytics, and data warehousing tools via server-side integrations. This allows engineers to spend less time supporting business teams with vendor code management and custom development, and enables marketing and product teams to access the data they need when and where they need it. Dive deeper into Customer Data Platforms here.
Management and storage
Building a value exchange that encourages privacy-conscious customers to share their first-party data with you is difficult. But without secure data management and storage, customers’ trust can waver and all of your hard work can go to waste in an instant. Responsible data governance is critical, as a single lapse in data privacy can lead your customers to file a request for their data to be deleted or leave you vulnerable to a class action lawsuit.
Consent management One of the pillars of responsible data stewardship is the lawful basis for data processing. Customer consent is the process through which customers signal their choices with respect to data uses. Ensuring that each customers’ data is being used in accordance with their consent preferences at all times is required for compliance. For example, when a customer opens your app, they may allow their data to be collected for analytics and security purposes but not for marketing and advertising purposes. It is your responsibility, therefore, to ensure that the data collected after those preferences are set is sent to the appropriate systems within your tech stack.This can be achieved either by using your Consent Management Platform (CMP) settings to trigger which vendor SDKs fire after consent preferences are set by the user, or by integrating your CMP with your CDP to filter how data flows across your tech stack based on customer consent state. You can dive deeper into both of those strategies in this article. More on aligning with Apple’s AppTracking Transparency later in this article.
Deterministic identity resolution Consent management and other aspects of data governance, such as fulfilling data subject requests, are nearly impossible if you don’t know who your customers are. This challenge is less daunting if your customers are only engaging through a single touchpoint, as engagements and preferences can then be tied to a device-level identifier. Once your customers begin engaging across multiple touchpoints, such as a website and a mobile app, however, you need a way to tie device-level data to unified customer profiles. Without the ability to tie consent preferences declared in one channel to a unified customer profile, it’s possible that you’ll continue using a customer’s data collected from another channel in a way that violates their signaled preferences. Furthermore, if a customer files a data subject request, you may fulfill the request for data that exists in one system but fail to fulfill it for the data that is siloed in other systems.
Data storage While activating first-party data in real time enables powerful use cases such as transactional messaging, equally important is the ability to cleanly store your data for the long term. Having first-party data in your data warehouse will enable you to build historical audience segments and run Business Intelligence (BI) queries. A data warehouse is also an excellent place to combine data from different sources, such as device-level engagement data with transactional data. The traditional method for getting first-party data from the client side into your data warehouse is to use an analytics tracking tool, such as Snowplow Analytics, to collect data from the client side, and then an Extract, Transform, Load (ETL) tool such as Fivetran, so transfer data from your cloud app to your data warehouse. Alternatively, Customer Data Platforms allow you to collect data from client-side and server-side environments and export it to your data warehouse with a single tool.
What can you do with your first party data?
Third-party data has made it easy for brands to follow a model of acquiring new customers, letting them churn, and re-acquiring them through retargeting campaigns. While this has allowed many companies to increase brand recognition and drive acquisition, it has also enabled them to avoid doing the hard work of figuring out how to build customer trust and loyalty.
First-party data, on the other hand, will help teams do the rewarding work of understanding their customers and delivering highly-relevant experiences throughout the customer lifecycle.
A lot of attention has been focused on initiatives designed to acquire new customers, but any experienced growth leader knows that strong customer retention is equally (if not more) important to success. In Bain’s Prescription for Cutting Costs whitepaper, Fred Reichheld reports that increasing customer retention by just 5% can result in a 25% increase in profits. Dumping money into acquiring customers that soon after churn, on the other hand, can result in a net loss.
First-party data enables you to improve customer retention by helping you deliver a more relevant experience to your customers. By gaining an understanding of each customers’ preferences via their engagements with your app, you’re able to thoughtfully re-engage with customers through your owned channels and spread customer lifetime value (CLTV) over a longer period of time.
Customer Data Platforms help here by making it easier for growth teams to use their first-party data to deliver relevant experiences to their customers. For example, mParticle’s 280+ server-side integrations allow marketers and product managers to forward unified customer profiles to the customer engagement tools of their choice without any custom development, enabling them to power timely experiences, such as in-app recommendations and follow-up emails, that increase customer retention.
While retention functions to spread CLTV over a longer period of time, personalization functions to raise the absolute lifetime value of each user.
Insights gained through first-party data analysis can be used to increase the relevancy of the experiences you delivered to your customers. Additionally, by running experiments and tying engagement metrics to your first-party customer profiles, you can increase the effectiveness of your campaigns over time. BCG research has shown that digital marketers that deliver relevant experiences to customers at multiple moments across the purchase journey achieve cost savings of up to 30% and revenue increases of as much as 20%.
One of the challenges with using first-party data to create personalized experiences is that data is often siloed across a number of different systems. Every tool has its own identifier and its own segmentation engine, and translating data across tools requires hours of painstaking developer work. When each tool is operating with its own data set, it’s nearly impossible to coordinate personalized experiences throughout the customer journey.
Customer Data Platforms simplify this challenge by streamlining first-party data collection, deterministic identity resolution, and audience segmentation into a single system, and making it easy to forward profiles and audience segments to all of the growth tools you are using via server-side integrations. You’re able to design personalized experiences in each tool, confident that `first_name` in your email vendor will be the same value as `firstName` in your mobile push vendor.
How to align with Apple’s AppTransparency Tracking
AppTrackingTransparency (ATT) is Apple’s privacy protection framework. It requires IOS app developers to explicitly prompt users for opt-in permission to “track” them. The definition of tracking is defined on Apple’s User Privacy and Data Use page.
Compliance with the latest App Store Review guidelines is predicated on the proper usage of this new framework. Additionally, each app must ensure that all user data processing obeys user ATT consent elections.
To successfully align with Apple’s ATT you need to be able to ingest your customers’ ATT status and use it to control how IDFA is collected and shared across your tech stack.
This presents a challenge to many mobile teams, as up until now IDFA had been collected by default and used as a universal identifier across tools and systems to simplify acquisition and measurement.
Implementing a privacy-conscious data infrastructure at the foundation of your tech stack is a great way to support ATT compliance. mParticle, for example, automatically collects ATT consent from the client-side, and allows you to federate ATT status out to any of the other tools in your stack. You can also control how IDFAs are forwarded across your tech stack based on ATT consent status, and check a customer’s ATT status at any time.
Learn more about supporting Apple’s ATT with mParticle here.