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

Replace Matomo by PostHog #5035

Closed
11 of 13 tasks
Tracked by #57
pixlwave opened this issue Oct 21, 2021 · 4 comments · Fixed by #5270
Closed
11 of 13 tasks
Tracked by #57

Replace Matomo by PostHog #5035

pixlwave opened this issue Oct 21, 2021 · 4 comments · Fixed by #5270
Assignees
Labels
A-Telemetry Telemetry / analytics to understand usage T-Task Refactoring, enabling or disabling functionality, other engineering tasks

Comments

@pixlwave
Copy link
Member

pixlwave commented Oct 21, 2021

  • Integrate PostHog SDK
    • API token storage
    • Test at least one basic event works
  • Redact anything PII that's leaking - room names, usernames, etc
  • Use an API to get a track id (see James)
    • Check im.vector.web.analytics_id if present, otherwise generate a new one (web PR)
  • Ask consent again for new analytics schema (web PR)
    • Remove old enableCrashReport setting and use enableAnalytics everywhere.
    • Confirm whether crash logs should be same opt in
  • Define the right screens to track initially (event PR)
  • Finalize Podspec in events repo
  • Remove analytics reporting from debug builds switch to production server
  • Review App Store privacy disclosure
@pixlwave pixlwave self-assigned this Oct 21, 2021
@pixlwave pixlwave added T-Task Refactoring, enabling or disabling functionality, other engineering tasks A-Telemetry Telemetry / analytics to understand usage labels Oct 21, 2021
@daniellekirkwood
Copy link
Contributor

There's documentation here

TL;DR

Approvers
Denise, James, and Amsha should be additional approvers to the PR.

Designs
Figma file

  • There are 2 variations; one for users who previously said no & one for users who previously said yes
  • There are screens for each platform (iOS & Android)

When to ask:
For existing users:

  • Who previously said no: Once, on app open after upgrade to newest version
  • Who previously said yes: Once, on app open after upgrade to newest version

For new users:

  • Utilise the “previously said no” screen for now
  • Short-term: First time the user hits home screen
  • Long-term: Is a part of the FTU flow (not a part of this issue)

@pixlwave
Copy link
Member Author

pixlwave commented Dec 1, 2021

Thanks sounds good. One note related to the web PR:

For existing users:

  • Who previously said no: Once, on app open after upgrade to newest version

The original idea was to not prompt users a second time if they had previously opted out from Matomo. Should we be doing the same on iOS?

@daniellekirkwood
Copy link
Contributor

Yes. Routinely we won't ask people twice, once they've said no, they've said no. As this is a new system (not Matomo) and the circumstances for how and what we track are different, we'll ask all users once more.

WDYT?

@pixlwave
Copy link
Member Author

pixlwave commented Dec 6, 2021

Well I thought the original reasoning of "if someone has opted out already, they aren't likely to opt into a system that adds an id to it, so lets not annoy them with a second prompt" made sense. But equally given the new prompt that gives more clarity, maybe some will choose to opt in now, so I can see the rationale in asking again.

Will update to show to everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Telemetry Telemetry / analytics to understand usage T-Task Refactoring, enabling or disabling functionality, other engineering tasks
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants