diff --git a/work/projects/ios-subscription-day7-promo-kickoff.md b/work/projects/ios-subscription-day7-promo-kickoff.md
index f10f3c49..e02d1682 100644
--- a/work/projects/ios-subscription-day7-promo-kickoff.md
+++ b/work/projects/ios-subscription-day7-promo-kickoff.md
@@ -1,19 +1,21 @@
 # Kick-off: (iOS) Grow active subscriptions by increasing paywall impressions with a day 7 promo half-sheet
 
-Zoom link: <Zoom link>
+Zoom link: https://duckduckgo.zoom.us/my/malex
 
 **Stakeholders and their responsibilities**
 
-- Project Advisor: Noelia
-- [Other stakeholders](https://app.asana.com/0/0/1207268731049844/f): Alessandro
+- Project Advisor: https://app.asana.com/1/137249556945/profile/1201807753392396
+- [Other stakeholders](https://app.asana.com/0/0/1207268731049844/f): https://app.asana.com/1/137249556945/profile/1200848785550295 https://app.asana.com/1/137249556945/profile/1206329551987277 https://app.asana.com/1/137249556945/profile/1211198099252476 https://app.asana.com/1/137249556945/profile/1200727780991749
 
 **Scope updates**
 
 - iOS port of the Android implementation. See [Android kick-off](https://app.asana.com/1/137249556945/project/72649045549333/task/1211002275165337) for the original.
+- Pixels?
 
 **Discussion items**
 
-- Should we add Phase 1 instrumentation (pixels for users who haven't seen the paywall + Grafana boards), as Android did? Or is Android's data sufficient to validate the iOS opportunity without it?
+- Who are the users targeted by this project? Scenarios where a user hasn't seen the subscription promo by day 7: (1) completed onboarding normally but the promo wasn't shown (e.g. installed before the onboarding promo existed); (2) skipped onboarding (reinstaller/returning user path — already covered by the existing reinstaller promo). Worth aligning on whether the scope covers both and how they're handled.
+- Do we need to add a Grafana board to monitor the promo impression/tap/dismiss pixels?
 
 **Next steps**