Closed Bug 1476688 Opened Last year Closed Last year

Support block/cap by provider

Categories

(Firefox :: Messaging System, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Firefox 63
Iteration:
63.5 - Sep 3
Tracking Status
firefox63 --- fixed

People

(Reporter: k88hudson, Assigned: ahillier)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

There are several use cases that require the id of "campaign ids" that are needed for messages:

- we should be able to specify frequency caps for both an individual message as well as a group of messages (e.g. max 5 for all CFR messages per day, max 1 per individual message)
- some snippets require the ability to an entire campaign instead of just the individual message
Blocks: 1471328
Priority: -- → P2
CFR also needs the ability to block by campaign (or maybe by provider makes more sense?), since users must be able to opt-out of all future CFR recommendations.
Summary: Support campaign_id for AS Router messages → Support block/cap by campaign for AS Router messages
Summary: Support block/cap by campaign for AS Router messages → Support block/cap by provider
Let's scope this specifically to allowing blocking of a particular provider, as well as specifying frequency cap information for all messages from a given provider.
Assignee: nobody → ahillier
Iteration: --- → 63.5 - Sep 3
Priority: P2 → P1
Commit pushed to master at https://github.com/mozilla/activity-stream

https://github.com/mozilla/activity-stream/commit/0aba142328b3e2ba3bf34c3b9c43064092f321a8
Fix Bug 1476688: Add ASRouter provider blocking and frequency capping (#4266)
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Blocks: 1486631
Component: Activity Streams: Newtab → Messaging System
You need to log in before you can comment on or make changes to this bug.