Opened 5 years ago

Closed 4 months ago

#2227 closed change (rejected)

new notification trigger mechanism based on usage of blocking features

Reported by: annlee@… Assignee:
Priority: Unknown Milestone:
Module: Core Keywords: closed-in-favor-of-gitlab
Cc: 2162 Blocked By:
Blocking: Platform: Unknown
Ready: no Confidential: no
Tester: Verified working: no
Review URL(s):

Description

Background

There are many relevant messages which could be shown to users who are not currently using one or more of the blocking 'features'

Our malware blocking feature is popular with other users. Check out this and more on our Options page.
Scared of malware infecting your computer? Block this and more on our Options page.
Sick of being tracked online? Block tracking and more on our Options page.

These messages will be most relevant once the new Options UI is available to the stable build.

The main growth goal of messages such as these, is to get users to interact more with the extension, via the Options page, Also, increased feature usage, can result in increased satisfaction---> increased shares.

What to change

Create 4 new notification mechanisms that will trigger different / new notification messages depending on which of the below situations is true for the user:

  1. a user is NOT using 'disable tracking'
  2. a user is NOT using 'disable malware'
  3. a user is NOT using 'disable social media buttons'
  4. a user is NOT using ANY of the additional blocking features

Each of the above should be a separate trigger, and trigger a separate message

Change History (1)

comment:1 Changed 4 months ago by sebastian

  • Keywords closed-in-favor-of-gitlab added
  • Resolution set to rejected
  • Status changed from new to closed

Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.

Note: See TracTickets for help on using tickets.