feat(analytics): migrate to GTM container, drop standalone Reo script - #51
Merged
Conversation
Load analytics via the shared steel.dev GTM container (GA4, Reo, LinkedIn, X, Clarity) using @next/third-parties instead of the hardcoded Reo script. Removes components/analytics/reo.tsx so Reo fires only from GTM and isn't double-counted. GTM is gated on NEXT_PUBLIC_GTM_ID so previews/forks without the var inject nothing.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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
Migrates docs.steel.dev analytics onto the shared steel.dev Google Tag Manager container (
GTM-TGM3B3GV), which already holds GA4, Reo, LinkedIn, X, and Clarity.@next/third-parties(official Next 15 helper — handles the<head>loader +<noscript>iframe for App Router/streaming).components/analytics/reo.tsxand its mount inapp/layout.tsx. Reo now fires only from GTM, so it isn't double-counted.NEXT_PUBLIC_GTM_ID, so previews/forks without the var inject nothing..env-exampledocuments the GTM var and drops the now-unusedNEXT_PUBLIC_REO_CLIENT_ID.Deploy notes
NEXT_PUBLIC_GTM_ID=GTM-TGM3B3GVset on Vercel (production).steel.dev+docs.steel.devto the GA4 web stream's cross-domain domain list, verify all five tags fire on a docs page in GTM Preview, and confirm Clarity text-masking is on (docs render API keys in code samples).