# Problem Many of our call to action statements are too generalized and do not present the value and ease of use of a feature to a project. Because we do not have a clear picture of what the project is doing with their code, we do not know how to personalize our messaging and communicate how the features of our product can benefit them nor how to guide them through an integration given the projects specific infrastructure or code. Because many of our features require specific setup from established open source code, we use terminology like "Configure Prometheus to monitor your deployments", this assumes that I am familiar with Prometheus (I'm not) and that I am "deploying" something that needs to be monitored but I have no idea what "monitoring" means in this context. ## Tests this data will enable | Test | KPI Estimate | Blocked By | | ------ | ------ | ------ | | [Add feature flag action to email campaigns](https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/481) | SpO + 3% | | | [Add feature flag action to continuous onboarding](https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/482) | SpO + 4% | [Link](https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/483) | ## Proposal for how to record this data