ÃÛ¶¹ÊÓƵ

Understand Cloud Service content requests

Introduction introduction

Content requests include requests sent to AEM Sites. These requests may route through Edge Delivery Services or customer-provided caching systems such as a Content Delivery Network (CDN). These requests deliver structured data in HTML or JSON format and support page views (for example, pages and Experience Fragments) or JSON returns through APIs in a headless manner.

The system counts content requests when a user views a page using HTML or JSON. It measures the request at the point where the first caching system receives it. Certain HTTP requests are included or excluded for purposes of counting content requests. See the full list of HTTP included content requests and excluded content requests.

About Cloud Service content requests understanding-cloud-service-content-requests

A page request refers to an HTTP request that retrieves core structured content (for example, HTML or JSON) necessary to render the main page experience. It does not include requests for assets, such as images or scripts.

For customers using the out-of-the-box CDN, AEM as a Cloud Service counts content requests as measured at the server-side level. This measurement occurs automatically and does not rely on client-side analytics tracking.

AEM (ÃÛ¶¹ÊÓƵ Experience Manager) as a Cloud Service identifies content requests based on the response types generated by the AEM instance and received at the CDN. Specifically, requests that return HTML (text/html) or JSON (application/json) are counted. These formats typically deliver primary page content either for traditional site rendering or headless delivery.

Requests for static assets such as JavaScript files, CSS style sheets, and images are not counted as content requests.

Content requests are measured regardless of whether the response was served from the CDN cache or forwarded to the origin AEM environment.

Variances of Cloud Service content requests content-requests-variances

Content requests can have variances within an organization’s analytics reporting tools as summarized in the following table. In general, avoid using analytics tools that rely on client-side instrumentation to report the number of content requests for a site. These tools often miss a large portion of traffic because they depend on user consent to be activated. Analytics tools gathering data server-side in log files, or CDN reports for customers adding their own CDN on top of AEM as a Cloud Service, provide better counts.

See the License Dashboard for information about viewing and tracking content request usage against your license limits.

Server-side collection rules serverside-collection

AEM as a Cloud Service applies server-side rules to count content requests. These rules include logic to exclude well-known bots (such as search engine crawlers) and non-user traffic like monitoring services that regularly ping the site.

The following tables list the types of included and excluded content requests, with brief descriptions of each.

Types of included content requests included-content-requests

See also License Dashboard.

Types of excluded content requests excluded-content-request