Overlay Integration FAQ
Practical guidance for browser protection, session requirements, and diagnostics when integrating @v.ersions/analytics.
Why does overlay sometimes not appear in Brave?
Brave Shields can block third-party cookies, iframes, or cross-site requests used by auth-helper. Disable Shields for your site or allow cross-site cookies for versions.se, then refresh.
Do I need to pass tokens manually?
No. The intended flow only needs applicationId. The helper page at versions.se issues analytics-token from your logged-in versions.se session cookie.
Which browser settings can break the flow?
Strict tracking prevention, third-party cookie blocking, ad/script blockers, or corporate privacy gateways can block auth-helper iframe and token calls.
How do I troubleshoot quickly?
Open DevTools and check requests for /auth-helper, /api/analytics-token, and /api/analytics/authenticated. Also review logs prefixed with [versions/analytics] and [versions/analytics/ui].
Quick Verification Checklist
You are logged in at https://www.versions.se in the same browser profile.
The helper URL resolves: https://www.versions.se/auth-helper.
analytics-token returns 200 from versions.se.
authenticated returns 200 from i.versions.se.
No blocker is stripping iframe/message/cookie traffic.