Analytics, Reporting, and Site Performance
AEM integrates with Adobe Analytics and Adobe Launch (Tags) for measurement. Practitioners should understand client libraries (clientlibs) - how CSS/JS are bundled, categorized, and included via data-sly-call or the page component - because clientlib strategy directly affects performance. Know component-level performance: lazy loading, image optimization via Dynamic Media, and minimizing render-blocking resources.
Reporting surfaces include Sites console reports, Assets reports (impressions, clicks via Insights), and Adobe Analytics dashboards. Know that Assets Insights tracks asset usage and requires configuration. For performance, understand dispatcher caching, CDN, client-side vs. server-side rendering, and Core Web Vitals concepts (LCP, CLS, INP).
Traps: assuming enabling Analytics requires no Launch property (it does - the Launch property deploys the Analytics extension); confusing page performance (server/render) with campaign performance (Analytics metrics); and thinking clientlibs are merged automatically without configuration (they are, via the HTML Library Manager, but categories and dependencies must be correct).
Rule of thumb: when a question asks why a page is slow, check in order: dispatcher cache hit rate, image weight/renditions, clientlib size and blocking, then third-party tags. When it asks where to see asset usage, the answer is Assets Insights, not the Sites console. Always verify that the Launch property is published for tags to fire on publish.