Add Pug to Analytics - #1019
Open
poluruprvn wants to merge 1 commit into
Open
Conversation
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.
Adds Pug to Analytics, after Plausible.
Disclosure: I maintain Pug, so this is a submission rather than a recommendation.
Every entry currently in Analytics is web analytics (Aptabase being the one app-analytics entry).
Pug is product analytics — autocapture, funnels with drop-off, retention cohorts, user flows and a
unified profile per person — so it fills a category gap rather than adding a fourteenth entry that
does the same job as the previous thirteen.
Against the inclusion criteria:
nothing is written to a visitor's device. Visitor ids are derived server-side from an HMAC under a
salt that rotates daily and is deleted on expiry rather than archived, so yesterday's ids are
permanently unlinkable. IP and User-Agent are hash inputs only — never stored, never returned.
https://docs.pug.sh/self-hosting/
The hosted version is in free open beta; self-hosting is available today.