Gate analytics on consent and fix Matomo SPA page views#849
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 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 |
82d08be to
f356a4e
Compare
Description
Align the documentation site's analytics behavior with the updated privacy and cookie-consent model.
Matomo and Google Tag Manager now load only after a visitor explicitly accepts analytics cookies. Visitors can reopen Cookie Settings from the footer, and withdrawing consent removes known tracking cookies before reloading the site without analytics scripts.
This also changes Matomo from cookie-only consent to full tracking consent and adds an explicit SPA page-view event after Next.js finishes updating the URL and document title. This prevents Matomo from associating a new URL with the previous page's title during client-side navigation.
Changes
requireConsentandsetConsentGiven.mtm.SpaPageViewafter client-side route changes so Matomo receives the current URL and page title together.PageViewtrigger._documentso it can be mounted conditionally from the consent-aware application tree.