Chrome 80’s SameSite Cookie Change Previewed a Tougher Tracking Environment
In February 2020, Chrome 80 began enforcing new SameSite cookie behavior. Cookies without a declared SameSite value were treated more restrictively, and cross-site access required SameSite=None; Secure. The change was technical, but it previewed the privacy and measurement complexity that would shape the next several years.
For SMBs, the immediate impact depended on the tools they used. Login flows, embedded forms, personalization, tracking scripts and analytics integrations could all be affected if vendors were not prepared. More broadly, the update reminded marketers that browser rules can change how data is collected.
Measurement depended on technical hygiene
Marketing teams often assume tracking just works. Chrome 80 showed why that assumption is risky. A business can spend money on ads and content, but if conversion tracking or session behavior breaks, decision-making becomes cloudy.
Brand Fuel Digital CEO/Founder Paul Burns sees this as a reason to connect marketing and technical checks. “You do not need to be a browser engineer to ask good questions. Are forms working? Are conversions firing? Are customers getting a smooth experience across the tools we use?”
What SMBs should have checked
- Conversion tracking: Confirm important events still record correctly.
- Form tools: Test embedded forms and third-party widgets.
- Vendor updates: Make sure marketing platforms support browser changes.
- HTTPS: Secure pages are part of modern tracking and trust.
Brand Fuel Digital’s View
Chrome 80’s cookie change showed that marketing measurement is fragile when the technical foundation is ignored. SMBs should routinely test tracking, forms and customer paths instead of assuming the data is complete.
Sources: Chromium Blog on SameSite cookie changes and Google developer guidance on SameSite=None; Secure.