Bugzilla

Notes for QA testing:

This patch implements a holdback experiment for the extended triplets added in bug 1568909. There are two branchs in this experiment:

* The `control` branch (99%), in which one should see the extended triplets if the profile age is younger than 7 days;
* The `holdback` branch (1%), in which one should NOT see the extended triplets regardless of the profile age.

To test the `control` branch is straightforward, simply use a new profile, it should show the triplets on the about:home or about:newtab. It's worth checking the `shield_id` field in the onboarding `IMPRESSION` telemetry ping, it should include the string `activity-stream-extended-triplets:control`.

It's hard to verify the `holdback` branch since it only accounts for 1% of the targeting audience. However, we can manually enroll themselves into this branch by overwriting `trailhead.extendedTriplets.experiment` in about:config, simply set it as `holdback` then restart the browser. Users in this branch will not see the extended triplets, hence it won't send the `IMPRESSION` ping. Still, `shield_id` should include `activity-stream-extended-triplets:holdback` in other pings of Activity Stream.

Notes for QA testing:

This patch implements a holdback experiment for the extended triplets added in bug 1568909. There are two branchs in this experiment:

* The `control` branch (99%), in which one should see the extended triplets if the profile age is younger than 7 days;
* The `holdback` branch (1%), in which one should NOT see the extended triplets regardless of the profile age.

To test the `control` branch is straightforward, simply use a new profile, it should show the triplets on the about:home or about:newtab. It's worth checking the `shield_id` field in the onboarding `IMPRESSION` telemetry ping, it should include the string `activity-stream-extended-triplets:control`. You can find how to check the telemetry in this [doc](https://github.com/mozilla/activity-stream/blob/master/content-src/asrouter/docs/debugging-docs.md#how-to-test-telemetry-pings). 

It's hard to verify the `holdback` branch since it only accounts for 1% of the targeting audience. However, we can manually enroll themselves into this branch by overwriting `trailhead.extendedTriplets.experiment` in about:config, simply set it as `holdback` then restart the browser. Users in this branch will not see the extended triplets, hence it won't send the `IMPRESSION` ping. Still, `shield_id` should include `activity-stream-extended-triplets:holdback` in other pings of Activity Stream.

Notes for QA testing:

This patch implements a holdback experiment for the extended triplets added in bug 1568909. There are two branchs in this experiment:

* The `control` branch (99%), in which one should see the extended triplets if the profile age is younger than 7 days;
* The `holdback` branch (1%), in which one should NOT see the extended triplets regardless of the profile age.

To test the `control` branch is straightforward, simply use a new profile, it should show the triplets on the about:home or about:newtab. It's worth checking the `shield_id` field in the onboarding `IMPRESSION` telemetry ping, it should include the string `activity-stream-extended-triplets:control`. You can find how to check the telemetry in this [doc](https://github.com/mozilla/activity-stream/blob/master/content-src/asrouter/docs/debugging-docs.md#how-to-test-telemetry-pings). 

It's hard to verify the `holdback` branch since it only accounts for 1% of the targeting audience. However, we can manually enroll ourselves into this branch by overwriting `trailhead.extendedTriplets.experiment` in about:config, simply set it as `holdback` then restart the browser. Users in this branch will not see the extended triplets, hence it won't send the `IMPRESSION` ping. Still, `shield_id` should include `activity-stream-extended-triplets:holdback` in other pings of Activity Stream.