I think this is a great Idea considering Adobe itself capped scheduled report time to 24 mths. The ability to then manually extend large groups of reports like this then is critical. 

Yah the page itself is a low quality explanation bit there is a link on it:   https://experienceleague.adobe.com/docs/analytics/implementation/launch/elements-to-variable.html?lang=en That link then in left side has a section on: https://experienceleague.adobe.com/docs/experience-platform/tags/ui/da...

https://experienceleague.adobe.com/docs/analytics/implementation/launch/layer-to-elements.html?lang=en

ok I see . I think then what could be an option is to just use custom link tracking,   add , props, evar, events as needed. Im guessing much of what you have in data layer can be attributed to those items so its an easy thing to add.   https://experienceleague.adobe.com/docs/analytics-learn/tutorial...

Unless your using some type of page coding that doesn`t support css then buttons and links should all be trackable via Activity Map. Will save you and devs a ton of work and allow all sorts of flexibility. Even has a browser plugin for a sort of heat map.   Caveats If you have 5 buttons with same na...

I think you should try this run a monthly trended for click instances by page.(I expect you will see just that page or are there multiple pages involved?)   Once you clarify the exact page then look at correlation against it of things like...   referring domains(pre and post drop) camapign IDs(maybe...

ok I recommend you do an   Activitymap Link/Region report. Pick monthly break down for last few months where drop was seen.   Lets start by finding dropping links them selves.(eventually we hope we can locate key page(s) contributing to loss).

Often times when Activity map tagging is lost it can be related to things like   -Implementation of SPA code(Angular for single page app) so links are no longer tagged. - custom JS code used to activate link clicks vs actual reg standard html links -Broken analytics code on pages that contributed to...

See my comment below on DAU/MAU definition below. In your case to understand UV Excluding login or a given page..   You need to segment users by excluding those visiting a given page only You need to define a prop/evar for users to differentiate logged in/ anonymous state        

So based on the fact you are using Lifecycle DAU or MAU as a reference. You should be able to use Daily/Weekly/Monthly/Yearly Unique Visitors.   See definition of DAU and MAU: https://aep-sdks.gitbook.io/docs/foundation-extensions/mobile-core/lifecycle/lifecycle-metrics   The challenge again here is...