Located at Acquia Acceptable Use PolicyThe policy describes prohibited uses of all services offered by Acquia Inc. and its affiliates and the website located at http://www.acquia.com and all associated sites.
The fully managed SaaS search offering created by Acquia and included as part of the Acquia platform that integrates with Drupal applications built on the Apache Solr search engine, enabling Drupal website visitors to find and discover relevant content faster.
A unique account holder who has conducted a Transaction within the prior 12 months and with an identified email address, postal address, phone number, or a combination thereof. Anonymous users are tracked but not counted as Active Profiles until they have identified themselves with an email address, postal address, phone number, or a combination thereof.
The freely available web server that is distributed under an open source license.
Artificial Intelligence.
Will be calculated per calendar month, as follows:
Availability Zones
The distinct physical locations that house the AWS data centers and which are engineered to be insulated from failures in other Availability Zones and provide low latency network connectivity to other Availability Zones in the same Region.
AWS
Amazon Web Services.
A set of data that computes heavy processes to ingest, process, and surface data in CDP on schedule.
Stands for Completely Automated Public Turing test to tell Computers and Humans Apart. It is a type of challenge-response test used to determine whether a user is human. This is done by asking a user to solve a challenge that is hard for computers, but relatively easy for human beings. Acquia currently supports both image and audio CAPTCHAs.
A content delivery network provided by a third party (for example, Akamai).
Customer Data Platform.
An application that includes the following self-service features:
Drupal Modules that have been certified by Acquia through an Acquia Professional Services engagement.
One set of Drupal code and files powering one or more website(s).
A transformation that computes the value of a custom field. For example, lifetime revenue or purchase frequency are standard calculations.
A set of pre-built charts by the customer in Metrics.
An input data file that does not follow all rules in the Acquia file specifications documentation.
A table in the CDP data model that is not in the standard entity list. For example, pets is a new table in the data model and therefore is a custom entity.
A column in the CDP data model that is added to the base schema. For example, preferred pet color is not part of the base schema and therefore is a custom field.
An Identity Resolution rule that is added to the set of IRE rules. For example, exact matching on loyalty id is not part of the base set of rules and therefore is a custom IRE rule.
A Machine Learning model that does not meet the requirements to be considered a standard model.
Represents the persistent, structured storage of content for a unique Drupal website or application instance within a respective environment.
A version of Acquia Search where the Customer’s Solr service and website index live on server infrastructure used only by the Customer. When Customer purchases dedicated Acquia Search as indicated in the order, all indexes for their subscription will be delivered through the dedicated Acquia Search platform only.
A Solr data entity representing structured website entities (content or file attachments) sent to Solr from Drupal during an indexing request.
The maximum size of data for an individual record being indexed, including all field names and values. Determined by the fields selected for indexing in Search API.
Customer-selected contributed or custom Drupal modules.
The Drupal module and sub-modules used by a Customer in conjunction with the Services.
This marks the point at which a product is no longer manufactured, sold, or officially available for purchase. It usually indicates that the company has decided to discontinue the product entirely.Implications: After EOL, the product may still function, but there will be no further updates, improvements, or changes from the manufacturer. Example: A software version reaching EOL means that it is no longer available for sale or distribution, and no further versions of that software will be produced.
This refers to the point at which a company stops providing specific services associated with a product. These services can include maintenance, updates, cloud services, or technical support. Implications: After EOS, customers will no longer be able to access the service that supports the product, and the product may not function optimally without it. Example: A hardware product might reach EOS if the company stops providing repair services or if the related cloud service is shut down, even though the hardware may still be physically operational.
This is the point at which a company stops offering technical support, updates, and patches for a product. However, this doesn’t necessarily mean that the product is no longer usable. Implications: After the End of Support date, users may still use the product, but they will no longer receive bug fixes, security patches, or any form of official assistance from the vendor. Example: A version of an operating system (e.g., Windows 7) may reach the end of support, meaning it won't receive security updates or technical assistance anymore, even though users can still use it.
An addition of functionality not currently present on Customer’s websites.
Represents where a Drupal website or application is managed within the Acquia platform while the website is progressing through its development, integration test, and live delivery lifecycle. Also known collectively as dev, stage, and prod.
An entry in the event table.
A distributed revision control and source code management system with an emphasis on speed.
Positive content that is automatically published.
Represents the Solr data made up of documents and where they live in the customer’s Drupal website. Also called a Solr core.
As defined in each Order.
The solution stack of free, open source software. The acronym LAMP refers to Linux, Apache, MySQL, and PHP.
The cached JavaScript code, other software, and other works and materials that are made available to the Customer for download and use in connection with the Services, but excluding the Drupal Module and the Third Party Software.
Any written order for products, hosting and/or support services, including, without limitation, a purchase order, order, Statement of Work, or other form of ordering document delivered to Acquia, which is subject to, and incorporates by reference, the terms and conditions of the Master Agreement, and to which no other terms apply.
The maximum size for a batch of documents. Limits: 100 KB per document; maximum 10 MB per batch.
The open source server-side scripting language designed for web development to produce dynamic web pages.
A production environment through a Drupal 7-based website builder.
A row in the customer summary table.
Any open source software, free software, or any similar software.
A set of data processes to ingest, process and surface data in the CDP as a stream.
The various geographic areas in which AWS infrastructure services are hosted within the United States, Europe, and Asia Pacific. Currently, Acquia utilizes AWS services in the following regions:
Software-as-a-Service.
Acquia’s proprietary website management tools.
Represents a single Solr request made by Drupal to retrieve specific content from the customer’s index.
The Site Studio services designed to enhance Customer’s Drupal web application software, such services made available to the Customer as a service via the internet for use with Acquia’s platform.
A version of Acquia Search where the Customer’s Solr service and website Index resides on server infrastructure shared with other Customers. By default, Customer will begin with shared Acquia Search.
Site Factory platform provisioned for Customer on Acquia’s managed hosting infrastructure.
A management dashboard.
A production environment through a Drupal-based website builder.
The Git version control application.
A version of the Site Factory Platform Drupal Instance that has been customized by the Customer or on behalf of the Customer.
Drupal contributed and custom modules added to the Site Factory Platform Drupal Instance to create the Site Factory Customer Drupal Instance.
Negative content that is automatically blocked.
A transformation that computes the value of a standard field. For example, lifetime revenue or purchase frequency are standard calculations.
A set of pre-built charts by Acquia in Metrics.
An input data file that follows all the rules in the Acquia file specifications documentation hosted on docs.acquia.com.
A table in the CDP data model. The list of standard entities are customer, transaction, transaction item, product, product category, and organization.
A column in the CDP data model that belongs to a standard entity in the base schema. For example, first name is a standard field on the standard entity customer.
An Identity Resolution rule that belongs to the base set of IRE rules. For example, exact matching on email address is part of the default IRE rule and therefore is a Standard IRE rule.
A Machine Learning model, which is trained and scored on the customer’s data. The following are the standard models:
Establish Customer’s specific key performance indicators to define clear success criteria.
"Sunsetting" refers to the gradual phase-out or planned discontinuation of a product, service, or feature. It’s often a period where the product is still available, but the company is preparing to retire it. Implications: During a sunset period, users may experience a reduction in new features, or the product may not be actively promoted anymore. The sunset phase gives users time to transition to alternatives or newer versions. Example: A software feature being "sunsetted" means it will no longer be actively maintained or improved, and users are encouraged to move to a new product or version.
Located at Support Users Guide.
A template report represents an SQL based parameterizable report built by Acquia based on the customer’s specifications.
A single instance of CDP ensuring isolation of the customer’s data, configurations, and customizations.
The third party software that is added to or installed in the Customer’s Drupal instance by the Drupal Module, including the AngularJS framework software.
A defined type of activity, such as a purchase, doctor’s appointment, lunch outing, form response, or other type of prescribed interaction, that is recorded in CDP’s transaction table. More specifically, it is a combination of Transaction Lines that occur simultaneously.
A row in the transactionitem table.
The PaaS is unresponsive or responds with an error.
Anything between Ham and Spam. Acquia does not recognize the user, they are shown CAPTCHAs, and the Customer gets to decide if the content is automatically published, blocked, or sent for manual moderation.
The deployment of a subsequent release of the Site Factory Platform or Site Factory Platform Drupal Instance that Acquia generally makes available at no additional license fee. Updates are provided when available as determined by Acquia. Acquia retains the right to deploy updates Monday through Friday, between 11 PM and 7 AM data center local time.
Any of Customer’s employees, consultants, contractors, or agents authorized to use the Services in accordance with the terms and conditions of this Guide.
Represents a location on the Internet or intranet with a unique URL providing a group of World Wide Web pages.
| Date | Update |
| 7 May, 2025 | Consolidated legal terms from Product and Service Guides in this section to a single page of definitions pertaining to Acquia contracts. Added missing terms. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.