+1 to this Manually reverting an unpublished change to the live version
(Compare Revisions > Use These Changes) creates a new revision, so it
appears as a 'Changed Resource' until published. Ideally we don't want
to publish these as they don't actually contain any changes, and it's
not great for traceability if our older published libraries are filled
with these "changes that aren't actually changes"
With regards to an Analytics implementation, it's not clear to me at the
moment how to format the XDM such that an event simply increments a Page
View. In AppMeasurement we had s.t() vs s.tl() to explicitly set or not
set the hit as a Page View, but there don't seem to be analogous
functions in alloy.js.Launch has web.webpagedetails.pageViews as a
suggested XDM event type when triggering a 'Send Event' action for the
AEP Web SDK - I'd assume an event with this type would automatically
flag the h...