Client-Side Cookies: A Living Fossil…

Client-side and server-side collection have different responsibilities. Understand script-access risks, privacy obligations and the controls required for each approach.

Client-Side Cookies - A Living Fossil…

Share with others

Navigating the Risks: Transitioning from Client to Server Side Tracking

According to Blockthrough, about 43% of internet users worldwide use ad-blocking software, and privacy requirements affect which customer signals you can collect and share. Plan privacy controls for both browser-side and server-side collection; moving collection changes where your team can enforce them. Browser-side collection still supplies the interactions that happen on the page.

How Client-Side Tracking Got Here

Since the mid-nineties, when internet dinosaurs roamed free on Netscape among the grayscale Yahoo! and Alta Vista search pages, cookies have provided valuable customer data to entities intent on somehow putting those data to use. In the earliest days, all cookies were accepted by default, and few consumers knew the implications. Fewer still were looking at the future of privacy and the complications that would arise from sharing a few bits of personal information online. The term “Personally Identifiable Information (PII)” had not been born, and the nefarious usage of such data was limited to just a few black hats and early online government-affiliated organizations.

Client-side tracking has, until recent years, represented the best source of direct and contextual user data. This tracking method pulls data directly from the user’s browser or browsing session. All those targeted messages, including the weird ads that seem to read your mind and the contextual browsing hints you experience as a consumer every day, have been traditionally driven by data collected client-side; unbeknownst to most, and unwanted by many. As you can imagine, companies were quick to commoditize consumer data, and have since relied heavily on client-side tracking to gather valuable customer insights.

Client-Side Script Access and Security Controls

Scripts running on a checkout page may be able to access sensitive fields. The code on that page is part of your security. The Newegg and Macy’s cases below involved card-skimming code placed on the merchants’ own pages.

Examples of Client-Side Vulnerabilities 

In 2018, malicious code on Newegg’s payment page skimmed payment information. ZDNet’s September 2018 report describes the code as active from August 13 until its removal on September 18, a span of 36 days.

Another notable example is the data breach suffered by Macy's in 2019. Hackers inserted malicious code into the company's online checkout page, collecting customers' personal information and payment details. The code was believed to have been injected on October 7 and was removed on October 15, the day Macy's was alerted. Customers who ordered online or saved card details in their wallets during those eight days may have had their information stolen.

Payment-page code needs its own security controls. Moving selected analytics tasks server-side can reduce browser requests, but it does not secure every script or payment form that remains on the page.

The Server-Side Solution

Server-side collection can put event validation and destination routing under your team’s control. By shifting data collection to their own servers and utilizing server-side tag managers, companies can gain greater control over customer data while improving website performance and data governance. A collection design has to account for both the browser and the server.

The implementation still needs access controls, monitoring, data minimization and rules for handling consent changes. Moving collection server-side does not on its own prevent a breach. Test which signals remain necessary in the browser and review the server-side configuration with your privacy and security teams.

Implementing Server-Side Tracking

To successfully transition to server-side data collection, businesses need to follow a strategic approach. The first step is to assess the current data collection infrastructure and identify areas where client-side tracking can be replaced with server-side alternatives. This may involve auditing third-party scripts, evaluating data collection requirements, and determining the necessary server-side tools and technologies.

Once this assessment is complete, companies should develop a comprehensive migration plan. This plan should outline the steps needed to implement server-side tracking, including the selection of appropriate tools, the configuration of server-side environments, and the testing and validation of data collection processes. It is essential to involve key stakeholders, such as IT, marketing, and legal teams, to ensure a smooth and compliant transition.

During the implementation phase, businesses should prioritize data governance and privacy. This includes establishing clear data handling policies, implementing secure data storage practices, and ensuring data collection meets regulatory requirements. Regular monitoring and auditing of server-side tracking should also be conducted to identify and address potential issues or vulnerabilities.

Conclusion

Set client-side and server-side responsibilities side by side, document the exposure that remains and name an owner for configuration changes.

Server-side collection gives your team another place to apply validation, routing and access controls. Its value depends on how well those controls are designed and run, and they need revisiting alongside browser-side collection as your data requirements change.

‍