Page-centric model
Each query in the Storefront API is designed around a page-centric concept. A single request retrieves all data needed to render a given page or view. For most user-facing pages, this means making one request to Elevate per page, with a few exceptions. This model enables the following benefits:- Built-in deduplication prevents overlapping content across areas.
- Consistent data ensures all related components share the same context.
- Optimized performance minimizes network overhead.
- Simplified integration requires fewer API calls and reduced client-side logic.
Page configurations
For more information about queries and page configurations, see the Storefront Overview.Caching
A strong recommendation is to never cache the Elevate response. The response is generated dynamically for every request. Caching this data, for example through full-page or API-layer caching, breaks key mechanisms and leads to incorrect or outdated experiences. Caching the Elevate response can lead to:- Loss of personalization and relevance
- Incorrect A/B tests
- Incorrect presentation of sponsored products
- Inaccurate behavioral tracking and attribution