(In reply to Marius Coman [:mcoman], Experiments QA from comment #4) Ah. So after this landed, we switched to the Remote Settings Provider (Bug ). To test this targetting, you'll have to switch back to the local provider: Pref name - "browser.newtabpage.activity-stream.asrouter.providers.cfr" Value - `{"id":"cfr","enabled":true,"type":"local","localProvider":"CFRMessageProvider","frequency":{"custom":[{"period":"daily","cap":1}]},"categories":["cfrAddons","cfrFeatures"]}` We'll need to update the targeting in Remote Settings. I guess we can do that already because only Firefox 68 is using those.
Bug 1538804 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Marius Coman [:mcoman], Experiments QA from comment #4) Ah. So after this landed, we switched to the Remote Settings Provider (Bug 1517306). To test this targetting, you'll have to switch back to the local provider: Pref name - "browser.newtabpage.activity-stream.asrouter.providers.cfr" Value - `{"id":"cfr","enabled":true,"type":"local","localProvider":"CFRMessageProvider","frequency":{"custom":[{"period":"daily","cap":1}]},"categories":["cfrAddons","cfrFeatures"]}` We'll need to update the targeting in Remote Settings. I guess we can do that already because only Firefox 68 is using those.