The Optimizely Attack and Consumers
For the past few days, the attack on Optimizely has been making headlines. If the news hasn’t reached you yet, a quick search (link) will turn up reports of hacked websites belonging to many companies, including IKEA, Levi’s, SkyShowtime and the Polish TMS Brokers. The media report 178 affected websites, although the full scale of the incident is not known. If you would like to learn about the technical details of the attack, I recommend this video that discusses it (link).
Why am I writing about this? The Optimizely case is not just a cybersecurity issue. It is also highly significant in the context of consumer compliance.
First it is worth explaining what Optimizely and similar services do.
Optimizely provides a marketing tool that, by means of a dedicated script, can change the look and content of a website directly in the visitor’s browser – without touching the code of the website itself, e.g. an online shop. This makes it possible to experiment with different interface variants and to measure their effectiveness and other parameters. As a result, each user may see a different version of the same page, and customers can be split into groups – some see version A, others see version B. Therea are many possibilities. The reference to the Optimizely script is placed in the head section of the website so that it loads first and applies changes before the page is rendered in the customer’s browser. The script updates automatically, running every interface experiment that has been set up.
You can probably see where I’m going. Optimizely is not a passive analytics tool. It actively rebuilds the interface the consumer is able to see. It does so outside the shop’s standard deployment process, often solely at the decision of the marketing team, or even based on decisions made by algorithms. This has a direct impact on liability for the content and layout of the website (e.g. when assessing market practices or dark patterns), on transparency towards consumers, and on security. The attack showed that whatever ends up in an Optimizely project is executed on every page of the shop where the script is embedded. The tool itself is very widely used – recall the 178 websites mentioned above that are known to have been attacked. And there are more tools and services like it. Optimizely itself states on its website that more than 10,000 brands use its services.
Since businesses are responsible for the marketing messages on their websites, including interfaces, purchase paths and essentially the entire UX, using tools such as Optimizely without appropriate procedures and prior review of the proposed changes can lead to serious trouble. Not only in the event of a hacking attack (where there is still room to argue that the changes were made without authorisation), but also in the everyday use of such solutions. They allow deep modifications of the interface, their automation and very broad marketing activities. As a result, it is easy to lose control over what customers actually see. That is why it is worth implementing appropriate procedures and mechanisms for reviewing the variants that are published, and making sure such tests are properly documented – if only to be able to defend yourself effectively against potential allegations, e.g. from UOKiK (the Polish Office of Competition and Consumer Protection). After all, it is easy to imagine a scenario in which, as part of automation, the service uses deceptive interfaces or content during tests that constitute prohibited practices.