@AdamBa17  would like to know the use case why you want to disable 1st party cookie ? How you are planning to use target then if cookies are disabled.you can think of custom solution to delete cookie using Java script if not able to disable thorough at.js - , cookies stored to companydomain are 1st ...

@NageshRaja  using dispatcher / CDN as proxy again indirectly depended on the AEM with limitations , keeping with AEM give more control to drive an business logic on top of the API response and hiding credential. Keeping external microservices is also an option but will bring in additional cost from...

@vs1985 @kautuk_sahni   not clear on the ask here, but so far understanding is you are looking to pass one use at a time then- aggregationType MAY Be "STRICT" [not sure] and maxUsersPerRequest should be 1 as Best effort would process data up to the limits that is 10 in example code above

yes  i agree about current API limitation however my point was most of key features / access can be done using API and have custom solution including historical logs , events etc.  Your use case is for Monitoring or specific to event audit which is nothing but a requirement to see who did what, when...

@Brad_morris  Cloud Manager API that allows you to retrieve information on pipeline executions, environments, branches, domains, IP whitelisting, execution and others can be used for tracking, what specific you want to capture here

suggestion, this could be done using Adobe IO Reading Cloud Manager API and Events - but will be  custom application deployed on cloud / server less @Brad_morris  

@NageshRaja  Approach 1 would good as AEM would work as middle layer/ business logic layer here before passing object to Vue 

yeah but it is not working , please share your finding and Adobe response to this thread  @smithchar  thx.

@smithchar  good to know then question what is the use case around  /conf/global/settings/wcm/policies  if  it is can not be used across projects/template . can you open ticket with Adobe support and check 

@smithchar when you say global understanding is between projects if yes consider storing policies in locations such as /conf/global/settings/wcm/policies so that they are reusable across different projects/ templates. I never tried though but worth checking it