A Site is a means of organizing Rules with a common context. The names given to Sites will vary from organization to organization, but for the purposes of this document, we shall refer to any public-facing Site as a PRODUCTION Site and any internal-only Site as a TEST Site.

There can be any number of test Sites, but, at a minimum, it is recommended that there should be separate test Sites for Quality Assurance (QA) testing and for Staging. QA testing is designed to test the functionality of the code to ensure that it works as expected. Staging is usually performed on hardware that mirrors the hardware used in the Production environment and is used to ensure that there are no issues when code is deployed to a particular hardware configuration.

There may also be multiple production Sites. These may be distinguished by a number of attributes such as their purpose (e.g., there may be separate Sites during a specific promotion), by their target audience (there may be separate Sites for existing and new customers), or by geography (there may be separate Sites for different territories).

Each separate Site should be defined using the Site Management functionality within Engagement Engine Editor.