Closed Bug 1476688 Opened Last year Closed Last year
Support block/cap by provider
52 bytes, text/x-github-pull-request
|Details | Review|
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
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.
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
You need to log in before you can comment on or make changes to this bug.