Repository navigation
Add Microsoft Clarity to the root layout - #12
Merged
Merged
Conversation
Loads the Clarity tag through next/script after hydration so the site has session recordings and heatmaps. Gated to production builds so local dev sessions stay out of the data. next/script ships with Next, so this adds no dependency. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Adds the Microsoft Clarity tag (project
yq9lytqnm9) toapp/layout.tsx, loaded withnext/scriptusing theafterInteractivestrategy. No effect, registry item, or gallery file is touched.Why
The site had no analytics. Clarity gives session recordings and heatmaps for the landing page and gallery.
Reviewer notes
NODE_ENV === "production", sonpm run devsessions are not recorded. Vercel preview deployments are production builds and will still record.next/scriptis part of Next.index.html; whether data arrives can only be checked after deploy.The gate
Every PR
npm run lintpasses (run onapp/layout.tsx)npm run buildpasses🤖 Generated with Claude Code