General terms
ASSE
Abbreviation for Asynchronous Server-Side Events. An event triggered by the shop that sends an HTTP request in the background to a configured external URL, e.g. to transmit data to a tracking service after an order. “Asynchronous” means that the request is sent with a time delay. The page rendering that triggers it does not wait for the response. ASSE events are triggered in the template via$wsAsse and set up in the ASSE configuration.
ASSE
Abbreviation for Asynchronous Server-Side Events. An event triggered by the shop that sends an HTTP request in the background to a configured external URL, e.g. to transmit data to a tracking service after an order. “Asynchronous” means that the request is sent with a time delay. The page rendering that triggers it does not wait for the response. ASSE events are triggered in the template via$wsAsse and set up in the ASSE configuration.
Consent
A visitor’s explicit consent that the shop may set certain cookies or process data. It is not required for technically necessary cookies, but is usually mandatory for marketing and tracking cookies (GDPR). In the template, you check the consent with$wsConsent.checkAllowed() before you set a non-necessary cookie. Details: $wsConsent.
Cookie
A small piece of information that the browser stores per website and keeps across multiple page views, for example a chosen setting or an identifier. Without a cookie, the shop “forgets” everything from the previous page on each page view. In WEBSALE, you read and set cookies via the $wsCookie module.Flag
A flag is a simple marker value that records a state, usually with only two possible values such as “yes/no” or “seen/not seen”. The term comes from the English word for a small banner: it is either set or not. In WEBSALE, you may encounter a flag, for example, as a cookie value that records whether a visitor has already seen an info popup. Based on the flag, the template decides whether the popup is still displayed.JSON
A text format for structured data such as lists or key-value pairs (the abbreviation stands for “JavaScript Object Notation”). It is human-readable and supported by many tools. In WEBSALE, complex cookie values (lists, maps) are automatically stored internally as JSON. External data is also often provided as JSON (see$wsExternalData, check path).
Campaign link
A link to the shop that carries additional information, usually as parameters in the address. This makes it possible to identify which marketing activity a visitor comes from, for example a newsletter or an advertisement. A campaign link is one of the typical triggers for setting a cookie (entry path). Related: Referrer.Onsite personalization
Targeted delivery of individual content or offers directly on the shop pages, depending on the behavior or characteristics of a visitor. Distinction: Simply storing a setting in a cookie, such as a personal greeting, does not on its own constitute onsite personalization. (Docs page to be added once available.)Referrer
The address of the page from which a visitor comes. When someone clicks a link to your shop, the browser usually transmits the address of the previous page. This is how you recognize where the visitor came from. The referrer is one of the typical triggers for setting a cookie (entry path). (In a technical HTTP context, the term is also spelled “Referer”.)Session cookie
A cookie without a defined lifetime. It only exists until the browser is closed and is then deleted. In WEBSALE, a session cookie is created if you do not specify a lifetime (age) when setting it. If the information should be retained longer, specify a duration. Details: module $wsCookie, method setCookie.
Stylesheet
A CSS file that defines the appearance of the pages: colors, fonts, spacing, and layout. Switching the stylesheet changes the look, for example from a light to a dark presentation.WEBSALE-specific terms
Template code
Code in the WEBSALE templates (the.htm files) that is executed on the server during page rendering, not only when the user clicks.
Important consequence: actions such as setting a cookie happen during a page view, not at the moment of the click. A click only takes effect when it triggers a new request and the template runs through again. (Concept page on templates to be linked once available.)