I. DEFINITIONS:
1. SitecoreAI Essentials
“Asset Storage” means the storage and retention of file-based assets in SitecoreAI including but not limited to images, videos, document files, data models, prompts, embeddings, and other digital content created, processed, transformed, or managed by SitecoreAI or its agentic components. This is measured across all modules of SitecoreAI, including (but not limited to) in the CMS and DAM modules.
“CDN Use” means the distribution and delivery of digital content content (including web assets such as HTML pages, JavaScript files, stylesheets, images, media assets and Gen AI generated or agent-assembled outputs) through Sitecore Content Delivery Network (“CDN”). It is tracked based on the total amount of data transmitted and metered on the SitecoreAI CDN facility, including delivery initiated by automated or agentic processes. This is measured across all modules of SitecoreAI, most notably in the CMS and DAM modules, and any Gen AI-powered or agentic delivery services.
"Non-Production Environments” means the total number of non-production environments included in or provisioned under the customer’s SitecoreAI subscription, used for testing, development, staging or training purposes only.
“Production Environments” means the total number of production environments included in or provisioned under the customer’s SitecoreAI subscription, used for live, customer-facing, or business-critical operations.
"Experience Interaction” means any instance in which the SaaS Product dynamically personalizes, delivers, or responds to a user’s activity, profile, or context across digital channels. Examples include, but are not limited to, search queries, personalized content, recommendations, messages, or offers. “Experience Interactions” also include system-triggered, agentic, or user-defined events configured within the application, such as custom actions, signals, or API calls that initiate or record a personalized or contextual response.
2. CMS:
“Visit” means an instance in which an application (including, without limitation, a website, mobile application, or other software application running on a digital device) presents, uses, accesses, or otherwise leverages any content, data, or functionality originating from (whether accessed directly or indirectly) the SaaS Product within a defined period of time (a “Time Frame”) or defined number of content requests from the CMS request.
For the purposes of this definition, a Visit may include the following categories of activity:
(i) Browser Activity means
- Direct human browser visits; and
- Visits or requests made through web integrations, including but not limited to RSS feeds, iFrames, browsing agents or similar mechanisms that emulate browsing behaviour, including agents that emulate browsing behaviour.
- For purposes of Browser Activity, a Visit shall be deemed to commence when such application first interacts with the SaaS Product after the end of any prior Time Frame, and shall be deemed to conclude upon the earliest to occur of:
- (a) Continuous activity for more than 12 hours from commencement;
- (b) No interaction with the application for a period of thirty (30) consecutive minutes;
- (c) A total of three thousand (3,000) content requests;
- (d) More than two hundred (200) content requests occuring within any one hundred (100) second period; or
- (e) The closure or termination of the application session.
(ii) Crawler Activity: means automated access for purposes such as indexing, discovery, aggregation, AI training or inference, cataloguing, or marketplace listing, carried out by a crawler that (a) accurately identifies itself, (b) originates from a verifiable and reputable source, and (c) complies with robots or other standard access-control instructions applicable to the SaaS Product. Crawler Activity includes retrieval of syndicated data feeds and marketplace catalogue requests. Automated access that does not meet these criteria is treated as Bot Activity.
(iii) Bot Activity: means any automated access that is not Browser Activity or Crawler Activity, whether authorized or unauthorized. Bot Activity includes scripted tools, headless browsers, unverified AI agents, testing or monitoring utilities, and automation that conceals or misrepresents its origin, disregards robots or other access-control instructions, more than two hundred (200) hits that occur in any one hundred (100) second period of the visit or otherwise exceeds reasonable use parameters for the SaaS Product.
Classification precedence: If an event could fall into multiple categories, Browser Activity prevails, then Crawler Activity, then Bot Activity.
The treatment of Crawler Activity and Bot Activity, including whether such activities constitute billable Visits, shall be determined by Sitecore’s policy in effect from time to time or as otherwise agreed in writing between the Parties.
If Customer does not implement Sitecore SDK as described below, irrespective of whether its Browser Activity, Crawler Activity or Bot Activity, a Visit will equal: seventy-five (75) requests for content for all digital properties other than websites created and published by SitecoreAI (non-website use cases (applications, mobile, aggregator sites)).
3. Agentic Studio
“Custom Agent” means any software or AI-driven agent (including a bot, model, workflow, or automation) that is (a) developed, configured, or supplied by Customer or a third party on Customer’s behalf, and (b) integrated with, or permitted to interact with, Sitecore Products and Services via any API, SDK, connector, plug-in, webhook, or other interface, and (c) not provided or supported by Sitecore. Custom Agents are used at Customer’s sole risk.
“Builder Seat” means a permission-based role within the Sitecore Agentic Studio that grants an individual the ability to create and configure Custom Agents.
4. DAM
“Power User” means the total number of registered users who can manage and modify the following within the DAM: assets, content/content types, product, custom content, campaigns/collections and metadata. This includes the actions create, update, add, delete, lock, submit, publish, archive. Power Users can also execute the same action types (where relevant) on the following within the operations tools of the DAM: projects, project types, workflows, tasks and task types. A user is considered a Power User if they have permission to do one or more of these activities.
“Consumers” means the total number of registered users who can view and download the following in the DAM: assets, content, product, custom content, campaigns/collections. Consumers can also share assets and make content/asset approvals within workflow tasks. All Consumers will have permission to add/update comments. A user is considered a Consumer if they have permission to do one or more of these activities. A Consumer shall include any employee of Customer whose primarily role within Customer’s organisation is not website administration or a third party whose role is to upload materials to Customer’s Sitecore platform.
II. TRACKING RULES:
Experience Interaction:
- SitecoreAI Essentials: Only instances that return content are counted as Experience Interactions.
- SitecoreAI Tiers 1 and above: Every instance is counted as an Experience Interaction, whether or not the SaaS Product returns content.
This distinction allows Customers to configure usage rules or consumption management policies within the Essentials entitlements.
CMS Visit:
a) Implementation of SDK
Customer shall implement Sitecore’s analytics software development kit (the “Analytics SDK”) for the purpose of Visit tracking. Sitecore may offer two versions of the Analytics SDK, as follows:
(i) a Visits tracking Only version, designed solely to capture Visit-level metrics; and
(ii) a full analytics version, designed to capture both Visit-level metrics and extended analytical data.
Sitecore may, from time to time, update, enhance, or replace the Analytics SDK, provided that any such updates do not materially degrade the performance or functionality of the SaaS Product.
b) Mandated Use Customer shall deploy and maintain an operational version of the Analytics SDK within its implementation of the SaaS Product as a condition of continued access to Visit-level analytics and reporting functionality. Sitecore may, by written notice, specify the minimum version of the Analytics SDK that Customer must use (the “Mandated Version”).
c) Performance and Compatibility. The Mandated Version of the Analytics SDK shall be designed such that its implementation does not materially slow load speeds or interfere with the performance of the Customer’s environment when used in accordance with Sitecore’s documentation.
If Customer elects not to implement the Analytics SDK, usage will be calculated by reference to the number of content requests, as captured in Sitecore system logs.
III. GOVERNANCE AND AMENDMENTS
Sitecore may, from time to time, update the Visit Definition or Visit tracking methodology described in this Schedule for legitimate business or technical reasons, including to reflect industry standards or product enhancements. Any material change that impacts billing shall be communicated to Customer in writing not less than thirty (30) days in advance.