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

Investigate and fix inaccurate events tracking #11446

Open
shiki opened this issue Apr 10, 2019 · 3 comments
Open

Investigate and fix inaccurate events tracking #11446

shiki opened this issue Apr 10, 2019 · 3 comments

Comments

@shiki
Copy link
Member

shiki commented Apr 10, 2019

These were found during #11395. These events are tracked way too much and warrant an investigation if we are tracking them correctly.

  • stats_period_accessed
  • stats_insights_accessed
  • notifications_accessed
  • notifications_notification_details_opened
  • login_accessed
  • push_notification_alert_tapped
@stale
Copy link

stale bot commented Apr 23, 2020

This issue has been marked as stale because:

  • It has been inactive for the past year.
  • It isn't in a project or a milestone.
  • It hasn’t been labeled [Pri] Blocker, [Pri] High, or good first issue.

Please comment with an update if you believe this issue is still valid or if it can be closed. This issue will also be reviewed for validity and priority (cc @designsimply).

@stale stale bot added the [Status] Stale label Apr 23, 2020
@peril-wordpress-mobile
Copy link

Fails
🚫 Please add a feature label to this issue. e.g. 'Stats'

Generated by 🚫 dangerJS

@dangermattic
Copy link
Collaborator

Thanks for reporting! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants