Hi @danellegodinez13,

I actually abandoned the employee Journey Analytics model in favor of a different type of project. I manage 4 lifecycle projects and several annual/quarterly projects within our team. I created a survey project that had every question from every survey. I then created a dashboard and imported each survey as a data source. I currently have tested 6 surveys in this dashboard, and have run into no issues. Each of the surveys maps to their own questions within my Journey survey. This allowed me to create benchmarks and comparisons for all of them and allow my new hire, engagement, onboarding and exit data to all live in the same survey. the benefit of this arrangement is, unlike the Journey Analytics project, my data is live so I don’t have to refresh my lifecycle data, it updates automatically. it took a little more setup on my part the JA dashboards do, but this allows me to use basically every widget except response rates (that one gets too messy as I only have 1 participant in my project to pull in the right metadata fields). I think the Journey Analytics has the right idea, but using flat files for ongoing surveys, to me, is silly. I want to set something up and have it run automatically. I try to remove as many manual requirements as I can from my projects. If you have any additional questions about how I set this up, please let me know.