Flag Target experiences in AEM to avoid page updates and test interruptions?

[sethgarske]

Is there an easy/automated way to flag pages that are currently running tests or personalized experiences?  The good news is our testing and personalization program is now running across a large number of pages across our site.  But this has created some operational challenges.  Our web team has to manually review the list of active tests (or just notice the page looks different in AEM), before they make any updates to a page.  I’m wondering if anyone has come up with a better solution to help avoid web content updates from breaking tests and personalized experiences? 

It would be great if there was a way to add a flag in AEM so authors could quickly see a given page has a live test running on the page.

[bc_99]

We developed an internal chrome extension allowing all Target activities to be captured (in the same fashion as what you see in Adobe Debugger for activities).  It is a bit manual and not bullet proof.