"The Topics API was included in July's Chrome 115 release, and if you don't have it yet, you will soon."<p>Imagine that you are Google and you need to replace third party cookies with your own system so you can make more money on ad services.<p>But to do that you need to get people using Chrome to update. How.<p>(Assume for sake of argument that the update is really just for adding the Topics API, i.e., Google is not going to make/lose money from any other change contained in the update.)<p>We're seeing sites warning users that they need to upgrade soon, presumably because "the site won't continue to work" unless they do.<p>Of course, that's false. Every website works without the Topic API.<p>Changing the user-agent string in DevTools to match Chrome 115's seems an easy workaround. Will Google try to prevent that.<p>Google cannot make Topics API an option and ask users if they want to install it. This is not a choice. If you ask users if they want ads, too many will say, "No." Amazing business model.<p>"... and if you don't have it yet, you will soon."<p>Some users will not. Because they will not use Chrome. Others might try to disable it. To those users resisting this "Topics API", I salute you.