fix(analytics): switch to @openpanel/nextjs SDK#29
Merged
Conversation
- Use OpenPanelComponent for client-side tracking - Replace Umami server-side tracking with OpenPanel - Update client-side track helper for window.op
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.
Summary
Fixes OpenPanel integration to use the correct Next.js SDK.
Changes
OpenPanelComponentfrom@openpanel/nextjsfor client-side trackingOpenPanelclasstrack()helper to usewindow.op@openpanel/webpackage and Umami filesEnvironment
Requires:
NEXT_PUBLIC_OPENPANEL_CLIENT_ID— for client-side trackingOPENPANEL_CLIENT_SECRET— for server-side registry download tracking (optional)