[Blog] In-depth: Posthog vs Fathom #9836
Merged
+178
−6
Conversation
This file contains 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
This is unrelated to the current post I'm writing, but I just noticed it in production and didn't want to forget to fix. Not sure how I fucked this up.
I felt like the screenshots are probably one of the easiest ways to see the similarities between the two products, so it felt like a good idea to move this up towards the top of the page.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ivanagas
requested changes
Nov 8, 2024
Co-authored-by: Ian Vanagas <[email protected]>
2 tasks
ivanagas
approved these changes
Nov 12, 2024
contents/blog/posthog-vs-fathom.mdx
Outdated
Comment on lines
39
to
46
| <ProductScreenshot | ||
| imageLight="https://res.cloudinary.com/dmukukwp6/image/upload/web_analytics_dashboard_light_bc76a94566.png" | ||
| imageDark="https://res.cloudinary.com/dmukukwp6/image/upload/web_analytics_dashboard_dark_42ac39a5f7.png" | ||
| classes="rounded" | ||
| alt="PostHog web analytics dashboard" | ||
| /> | ||
|
|
||
|  |
There was a problem hiding this comment.
This is a lot of screenshots to have all at once, maybe move them below the table with some context on why you are including them? For example:
"In terms of design, both PostHog and Fathom's web analytics dashboards look similar..."
(PostHog screenshot)
"The big difference is that PostHog includes sessions where Fathom only includes visitors"
(Fathom screenshot)
There was a problem hiding this comment.
we desperately need a carousel option for screenshots!
Co-authored-by: Ian Vanagas <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
Co-authored-by: Ian Vanagas <[email protected]>
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.
Changes
This is an in-depth breakdown between PostHog and Fathom Analtyics. It follows a similar structure to the ones we have for Sentry and Plausible.
https://posthog-git-posthog-vs-fathom-post-hog.vercel.app/blog/posthog-vs-fathom
Checklist
vercel.jsonArticle checklist
posthog vs fathomto existingfathom alternativesandfathom competitorskeywordsUseful resources