Bug 1546492 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Impression in discovery stream for recs and spoc items  are tracked inside browser.newtabpage.activity-stream.discoverystream.rec.impressions and prefs browser.newtabpage.activity-stream.discoverystream.spoc.impressions respectively

Above prefs stores mapping of story(rec) IDs to a single timestamp (time of first impression). These timestamps guarantee a story doesn't stay on top for longer than configured in the feed settings (settings.recsExpireTime).

TBD: Clarify if it's true for both recs and spocs?


1. QA Steps to test discovery stream spocs impressions are not changing browser.newtabpage.activity-stream.feeds.section.topstories.spoc.impressions

https://bugzilla.mozilla.org/show_bug.cgi?id=1522832#c13


2. QA steps to test rotations of stories on the client

https://bugzilla.mozilla.org/show_bug.cgi?id=1527702#c3


3. QA steps to test spocs filtering by frequency cap

https://bugzilla.mozilla.org/show_bug.cgi?id=1520258#c6

Frequency cap for a spoc item is stored in feed configuration (e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on)

in format shown in example below which defines that for campaign 1 no more than 5 spocs can be shown in total lifetime, and no more than 2 per hour.

  "campaign_id": 1,
    "caps": {
      "lifetime": 5,
      "campaign": {
       "count": 2,
       "period": 3600
      }
     }
Revision 1 by
on 
Impression in discovery stream for recs and spoc items  are tracked inside browser.newtabpage.activity-stream.discoverystream.rec.impressions and prefs browser.newtabpage.activity-stream.discoverystream.spoc.impressions respectively

Above prefs stores mapping of story(rec) IDs to a single timestamp (time of first impression). These timestamps guarantee a story doesn't stay on top for longer than configured in the feed settings (settings.recsExpireTime).

TBD: Clarify if it's true for both recs and spocs?


1. QA Steps to test discovery stream spocs impressions are not changing browser.newtabpage.activity-stream.feeds.section.topstories.spoc.impressions

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1522832#c13


2. QA steps to test rotations of stories on the client

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}


https://bugzilla.mozilla.org/show_bug.cgi?id=1527702#c3


3. QA steps to test spocs filtering by frequency cap

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1520258#c6

Frequency cap for a spoc item is stored in feed configuration (e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on)

in format shown in example below which defines that for campaign 1 no more than 5 spocs can be shown in total lifetime, and no more than 2 per hour.

  "campaign_id": 1,
    "caps": {
      "lifetime": 5,
      "campaign": {
       "count": 2,
       "period": 3600
      }
     }


QA steps to test lifetime and period cap https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c3
Revision 2 by
on 
Impression in discovery stream for recs and spoc items  are tracked inside browser.newtabpage.activity-stream.discoverystream.rec.impressions and prefs browser.newtabpage.activity-stream.discoverystream.spoc.impressions respectively

Above prefs stores mapping of story(rec) IDs to a single timestamp (time of first impression). These timestamps guarantee a story doesn't stay on top for longer than configured in the feed settings (settings.recsExpireTime).

TBD: Clarify if it's true for both recs and spocs?


1. QA Steps to test discovery stream spocs impressions are not changing browser.newtabpage.activity-stream.feeds.section.topstories.spoc.impressions

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1522832#c13


2. QA steps to test rotations of stories on the client

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}


https://bugzilla.mozilla.org/show_bug.cgi?id=1527702#c3


3. QA steps to test spocs filtering by frequency cap

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1520258#c6

Frequency cap for a spoc item is stored in feed configuration (e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on)

in format shown in example below which defines that for campaign 1 no more than 5 spocs can be shown in total lifetime, and no more than 2 per hour.

  "campaign_id": 1,
    "caps": {
      "lifetime": 5,
      "campaign": {
       "count": 2,
       "period": 3600
      }
     }


QA steps to test lifetime and period cap https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c3

QA steps to test spoc display by probability - https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c7

QA steps to test deduping spocs by domain - https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c8
Revision 3 by
on 
Impression in discovery stream for recs and spoc items  are tracked inside browser.newtabpage.activity-stream.discoverystream.rec.impressions and prefs browser.newtabpage.activity-stream.discoverystream.spoc.impressions respectively

Above prefs stores mapping of story(rec) IDs to a single timestamp (time of first impression). These timestamps guarantee a story doesn't stay on top for longer than configured in the feed settings (settings.recsExpireTime).

1. QA Steps to test discovery stream spocs impressions are not changing browser.newtabpage.activity-stream.feeds.section.topstories.spoc.impressions

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1522832#c13


2. QA steps to test rotations of stories on the client

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}


https://bugzilla.mozilla.org/show_bug.cgi?id=1527702#c3


3. QA steps to test spocs filtering by frequency cap

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1520258#c6

Frequency cap for a spoc item is stored in feed configuration (e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on)

in format shown in example below which defines that for campaign 1 no more than 5 spocs can be shown in total lifetime, and no more than 2 per hour.

  "campaign_id": 1,
    "caps": {
      "lifetime": 5,
      "campaign": {
       "count": 2,
       "period": 3600
      }
     }


QA steps to test lifetime and period cap https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c3

QA steps to test spoc display by probability - https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c7

QA steps to test deduping spocs by domain - https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c8
Revision 4 by
on 
Impression in discovery stream for recs and spoc items  are tracked inside browser.newtabpage.activity-stream.discoverystream.rec.impressions and prefs browser.newtabpage.activity-stream.discoverystream.spoc.impressions respectively

Above prefs stores mapping of story(rec) IDs to a single timestamp (time of first impression). These timestamps guarantee a story doesn't stay on top for longer than configured in the feed settings (settings.recsExpireTime).

1. QA Steps to test discovery stream spocs impressions are not changing browser.newtabpage.activity-stream.feeds.section.topstories.spoc.impressions

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1522832#c13


2. QA steps to test rotations of stories on the client

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}


https://bugzilla.mozilla.org/show_bug.cgi?id=1527702#c3


3. QA steps to test spocs filtering by frequency cap

Set discoverystream.config pref to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":false,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}

https://bugzilla.mozilla.org/show_bug.cgi?id=1520258#c6

Frequency cap for a spoc item is stored in feed configuration (e.g. https://getpocket.cdn.mozilla.net/v3/firefox/global-recs?version=3&consumer_key=40249-e88c401e1b1f2242d9e441c4&locale_lang=en-US&feed_variant=default_spocs_on)

in format shown in example below which defines that for campaign 1 no more than 5 spocs can be shown in total lifetime, and no more than 2 per hour.

  "campaign_id": 1,
    "caps": {
      "lifetime": 5,
      "campaign": {
       "count": 2,
       "period": 3600
      }
     }


QA steps to test lifetime and period cap https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c3

QA steps to test spoc display by probability - https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c7

QA steps to test deduping spocs by domain - https://bugzilla.mozilla.org/show_bug.cgi?id=1546492#c8

QA steps for personalization:
For personalization v1 steps for spocs use this: https://github.com/mozilla/activity-stream/pull/4864#issuecomment-479962039

For personalization v1 steps for recs use this: https://github.com/mozilla/activity-stream/pull/4911#issuecomment-484588673

Back to Bug 1546492 Comment 1