Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve User Referral and Journey Tracking in PostHog #879

Open
ori-near opened this issue Jul 16, 2024 · 4 comments · May be fixed by NEAR-DevHub/neardevhub-contract#145
Open

Improve User Referral and Journey Tracking in PostHog #879

ori-near opened this issue Jul 16, 2024 · 4 comments · May be fixed by NEAR-DevHub/neardevhub-contract#145
Assignees
Labels
enhancement New feature or request

Comments

@ori-near
Copy link
Collaborator

Problem

Our current PostHog reports lack the details needed to understand how users find and navigate our DevHub platform. This makes it difficult to know which engagement activities are working and what we need to improve in the user journey.

User Story

As the Moderator in charge of developer engagement (Joe), I want to see reports in PostHog that provide insights into user referral and user journeys so that I can optimize our strategies based on data.

Acceptance Criteria

  • Reports should allow user so specify a date range
  • Referral Traffic
    • High-Level Overview: Show the total number of new users acquired through referrals for the selected date range (e.g. a table showing referral source (e.g. Instagram) in the first column, and the number of new users from each source in the second column).
    • Page Breakdown: For each page on DevHub, show the referral source driving traffic to that page.
  • User Paths
    • Show the most frequent sequences of pages users visit after a specific Landin page
    • Identify pages where users drop off or leave the platform (e.g. exit/bounces)
@ori-near ori-near added the enhancement New feature or request label Jul 16, 2024
@Tguntenaar Tguntenaar self-assigned this Jul 17, 2024
@Tguntenaar Tguntenaar moved this from 🆕 Triage to 🏗 In progress in 🚀 DevHub Products Jul 17, 2024
@Tguntenaar
Copy link
Collaborator

Tguntenaar commented Jul 18, 2024

In order to track bounce rate I turned on autocapture in the PostHog dashboard settings as mentioned in the docs

Edit:
To my knowledge autocapture won't work if we can't call posthog.init(. Also tracking $pageleave events won't work without access to the window object or packages like react-router-dom.

@frol
Copy link
Collaborator

frol commented Jul 19, 2024

@Tguntenaar Bringing your discussion from NEAR-DevHub/neardevhub-contract#142 (review).

Consider starting with checking if it would be enough if Joe will start adding extra props to all links he shares, e.g. https://devhub.near.page/proposal/155?r=i, where r stands for referral and i for Instagram. If we pass there props in, and capture all the props in our Posthog already, that should be enough. We don't need to add anything specific to our domain specifically, I believe

@Tguntenaar Tguntenaar moved this from 🏗 In progress to 👀 In review in 🚀 DevHub Products Jul 19, 2024
@Tguntenaar Tguntenaar moved this from 👀 In review to 🏗 In progress in 🚀 DevHub Products Jul 19, 2024
@Tguntenaar
Copy link
Collaborator

Thanks for the tip! That would work for the refferral tracking, but not the bounce rate / user paths.

telegram-cloud-photo-size-4-5821461066444555807-y

Also, I've been playing around in a "test" dashboard. While trying to add a new insight to trace where they drop off posthog asked to upgrade to have advanced path insights. @frol Can we opt-in for that?

@Tguntenaar
Copy link
Collaborator

To improve referrer tracking we made a spreadsheet to standerdize the query parameters of sharable links.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 👀 In review
Development

Successfully merging a pull request may close this issue.

3 participants