The Google Global Site Tag extension from Acronym supports GA4.

We haven't provided any best practices because it's different for each customer. You are correct that anything you add to your property can potentially increase library size and thus have a negative impact on performance and user experience. This is generally true for anything you add to your page, ...

I recommend you take a look at the Link Delay explainer.The Click event from the Core extension uses this behavior when it is configured with the link delay option on.  My guess is that you've got a Click Event with link delay turned on, and the selector in that event is selecting this link and doin...

This is correct. Each build is done from scratch based on the exact resources that are upstream and included in your library. The process is repeated when you move from Dev to Stage to Prod.

Unfortunately, yes. Launch continues to support IE in the browser runtime (given the market share that IE still has), and ES6 remains unsupported in IE.From a Launch perspective, we have an item on our roadmap to enhance our build compiler to be able to transpile from ES6 to ES5 for you, such that y...

@Antti_Ko, these changes happened several months ago. The folders themselves were introduced because of a limitation on the number of unique items per folder with our CDN partner. We needed a less-flat folder structure on the CDN in order to continue growth. The names of those folders are tokens tha...

You'd have to have your IT team touch the page code in order to switch to an async deploy anyway.  But yes, if you link your embed code, it should work just the same.

There is no mechanism to define Rule Actions that should occur for any direct call rule.  You'd simply need to add the Action to any of the Rules you have that use Direct Call as the Event.

We're actually wrapping up work on this now.  Code review and testing ongoing, should be released soon.

You might try asking in the Analytics community, but AppMeasurement has a variable you can set to force HTTPS connections.  It is not exposed as a setting in the Analytics extension configuration, so you have to write some custom code, but I believe you just set s.ssl=true.