docs: align fingerprint API counts with stats pages#800
Conversation
The script stats pages on scripts.nuxt.com count active hardware fingerprinting APIs (X Pixel: 4, Clarity: 5), but the first-party guide and v1 release notes were citing the wider entropy-weighted set (9 and 10). Use the stats-page numbers so both pages agree.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
📝 WalkthroughWalkthroughThis PR corrects quantitative documentation claims about third-party script fingerprinting behavior across two pages. The First-Party Mode guide and v1 release notes are updated to consistently state that the X Pixel accesses 4 fingerprinting APIs (reduced from 9) and Microsoft Clarity accesses 5 fingerprinting APIs (reduced from 10), while preserving other cited metrics for tracking cookies and domains contacted. These changes align the documentation with actual script behavior observations. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔗 Linked issue
Resolves #793
❓ Type of change
📚 Description
X Pixel and Microsoft Clarity fingerprint API counts were inconsistent across docs vs the live stats pages. Updates
first-party.mdandv1.mdso X Pixel reads4(was 9) and Clarity reads5(was 10), matching scripts.nuxt.com/scripts/x-pixel and /scripts/clarity.