feat(analytics): add Moderok analytics provider#2393
Open
VaughnBosu wants to merge 1 commit into
Open
Conversation
Adds a Moderok provider alongside the existing GA4 and Umami providers. Moderok is an analytics platform built for browser extensions. Also persists the auto-generated anonymous user id to storage so it stays stable across MV3 service worker restarts — previously a fresh id was created on every restart, inflating user counts for every provider.
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
the
pkg/analytics
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.
Overview
Adds a Moderok provider to
@wxt-dev/analytics, alongside GA4 and Umami. Moderok is an analytics platform built specifically for browser extensions.The one thing I changed outside of adding a new provider is how UUIDs are persisted. When developing Moderok, I found they had to be persisted to storage so that service-worker restarts wouldn't create a new UUID, because that would massively inflate user counts. So I made that fix in this PR.
Manual Testing
I used a test WXT extension and ensured that proper data was showing up in the Moderok dashboard.
Related Issue
Proposed and greenlit in discussion #2388 by @aklinker1