A heartbeat study sends users to a survey to fill out. It is important for Data Science to link these survey answers to their Firefox usage, prefs. The way this works right now:

• Locally when evaluating the recipe, the Normandy id is appended to the survey URL
• A ping is sent containing the survey id and the Normandy id if the user does not take the action

We're looking to support Heartbeat style surveys in other messaging surfaces like CFR doorhangers and continue to support the same workflow.

I did not see a telemetry review on the initial code that landed Heartbeat (probably because it predates our data collection policy) and I wanted to check if this collection can still happen or we should change it.

There wouldn't have been a review because heartbeat predates the Data Collection Review process. I wouldn't expect there to be a problem with the Privacy Notice in combining those ids, but without a Data Collection Review request I don't know that I know enough about these ids and what purposes they intend to serve to say for sure that your review will pass.

(( Does the ping contain the Normandy Id? The docs don't include it (though it does say it sends the Telemetry client_id for some reason). ))

For clarity it might be best to submit a Data Collection Review for the collection. That way we'll have all the information together in one place. Who knows? Maybe we'll be able to remove some unused collections at the end of this.