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

feat(reference): act-1447 - added capture events to reference pages #1394

Merged
merged 1 commit into from
Jul 9, 2024

Conversation

TrofimovAnton85
Copy link
Contributor

@TrofimovAnton85 TrofimovAnton85 commented Jul 8, 2024

Description

  • added capture events ( "Page Viewed", "Request Sent", "Request Configuration Started", "Customize Request" ) to new reference pages

Screenshot 2024-07-08 at 15 00 34
Screenshot 2024-07-08 at 15 01 56
Screenshot 2024-07-08 at 15 03 29

Links:

JIRA Issue

@TrofimovAnton85 TrofimovAnton85 self-assigned this Jul 8, 2024
@TrofimovAnton85 TrofimovAnton85 requested a review from a team as a code owner July 8, 2024 12:57
Copy link

vercel bot commented Jul 8, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
metamask-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 8, 2024 0:58am

export const trackClickForSegment = ({
eventName,
clickType,
userExperience,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TrofimovAnton85 Just out of curiousity what info does this provide in the analytics. Does it give us insight into loading metrics, or customer satisfaction, etc...?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@joaniefromtheblock Hey!
We have several types of events/metrics (they are described in the ticket) that we would like to collect for analytics. Based on them, we can test: what percentage of users use our updated reference pages and how convenient they are for them (do they use the parameter configurator, sending requests).

Copy link
Contributor

@joaniefromtheblock joaniefromtheblock Jul 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry I meant specifically the userExperience? I can see how the event, response status, and timestamp are used, but just wondering what the userExperience translates to in Mixpanel @TrofimovAnton85

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First, we plan to release updated pages for 10% of users (based on the feature flag condition). For them, this userExperience metric will take the value “new”, and the remaining 90% users => old pages will be displayed.

Copy link
Contributor

@joaniefromtheblock joaniefromtheblock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@TrofimovAnton85 TrofimovAnton85 merged commit f0001dc into main Jul 9, 2024
6 checks passed
@TrofimovAnton85 TrofimovAnton85 deleted the feat-segment-events branch July 9, 2024 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants