DropboxYasmin McDowell,Lawrence GoodProblem & solution
Testing cookie behavior across hundreds of web surfaces with our in-house auditor
Summary
Maintaining cookie consent behavior across more than 200 web surfaces is difficult because URLs, integrations, experiments, languages, and page settings change over time. Dropbox built an in-house cookie auditor that uses Playwright and fresh isolated browser sessions to test three experiences—a standard US visitor, an EU visitor, and a visitor sending a Global Privacy Control signal. Each test records cookies before interaction, finds consent controls without relying on visible button text, declines non-essential cookies, reloads the page, and verifies that the resulting cookies and saved preference match expected behavior. A companion URL detector narrows the audit set from traffic records, while configurable classifications, exceptions, weekly reports, and historical results support review, trend detection, and follow-up by Privacy and Engineering teams.
Context
Dropbox operates more than 200 web surfaces whose URLs, consent controls, integrations, experiments, languages, and settings change over time. Manual quality assurance across those surfaces required substantial effort, while the company also needed to verify Global Privacy Control handling and whether cookie choices remained effective after page reloads.
Approach / What changed
Dropbox built a Playwright-based cookie auditor that tests fresh browser sessions for standard US, EU, and GPC experiences. It records cookies before interaction, identifies consent controls across different interfaces and languages, declines non-essential cookies, reloads pages, and checks the resulting behavior. A companion URL detector filters traffic-derived candidates into a manageable audit set, while classifications and exceptions remain configurable outside the auditor’s code.
Takeaways
The auditor tests actual browser behavior, including cookies loaded before consent, the result of declining non-essential cookies, and whether preferences persist after reload.
Consent classifications, approved cookies, and known exceptions are maintained outside the auditor’s source code so the Privacy team can update them without an engineering release.
Weekly reports separate likely violations from known false positives, and historical results help teams identify when previously correct consent behavior changes.
Source and freshness
- Source
- dropbox.tech
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.