Documentation of supported COOKIES files in the widget
COOKIES name | Script setting/reading the cookies | Validity period | Cookie domain | Website WWW | Website owner/administrator | Description | Purpose of cookie | Data that the cookie collects | Does it collect location data? | Do other companies have access to the data? If so, which ones? | Will the cookie data be used for behavioural advertising or tracking ads? | Is it possible to use the website without using cookies? |
| JS | 180 days | customer (main e.g. | (where the customer installs the widget) | customer startquestion.com | Information about the user's session on the site made available to the widget. | The conditions defined in the display rules, e.g. user time on page, number of page views, are checked against this cookie. | Session expiry time ( The user's time spent on the site (calculated in seconds). Number of pages visited by the user. | Not if we are talking about geolocation data. | If the widget is hosted at the client, it is the client's server service provider. If the widget is hosted on the Starquestion panel then the server service provider (Asseco, Hostersi.pl ...) | No, but potentially the client can configure the widget in this way | Yes, but the widget will not work |
These cookies can be many: | JS | 180 days | customer (main e.g. | (where the customer installs the widget) | customer startquestion.com | The rules for displaying the widget are checked on the basis of these cookies. | closed: boolean indicating whether the widget is closed.filled: boolean indicating whether the widget is filled.id: widget identifier.views: number of views of the widget.lastViewDate: date of last display of the widget. | Not if we are talking about geolocation data. | If the widget is hosted at the client, it is the client's server service provider. If the widget is hosted on the Starquestion panel then the server service provider (Asseco, Hostersi.pl ...) | No, but potentially the client can configure the widget in this way | Yes, but the widget will not work |
Please note the presence of localStorage.
FAQ
1. For what purpose are biscuits set?
Biscuits and localStorage are used to collect information:
about the user's session on the website
The actions associated with each widget.
Data from localStorage cannot be shared directly between subdomains of the same domain. This is due to the "same-origin policy" (same-origin policy) enforced by web browsers. Therefore, our answer is to mirror localStorage cookies. They are set so that the user can manage display rules between their products in different subdomains. The startquestion-session cookie updates the user's session data in the main domain.
2. Is it necessary to save them for 6 months?
We chose this period based on the average needs of users.
3) Why are the cookies set on the main domain exampleadomena.pl instead of the domain of the website www.przykladowadomena.pl?
The reason is the sharing between subdomains mentioned in point 1.
4. What is the reason for performing a write/read cookie/LocalStorage every 5 sec?
By setting such an interval, we chose a compromise between CPU (processor) usage and the frequency of updating the time of user presence on the site. We felt that setting such an interval would induce an unnoticeable load on the current processes and a reasonable response time for a display rule such as Time across the site.
5. Which browser versions do you support?
All that support es2016plus (Array.from, Array.map, Array.includes, Array.filter, Set, Map, ...). We do not support IE11, which does not receive technical support from Microsoft as of 15 June 2022. List of browsers:
"es6" | Can I use... Support tables for HTML5, CSS3, etc
6. Would it be possible for you not to use the biscuit mechanism or is it, however, absolutely necessary for proper operation?
It is not absolutely necessary, but it extends the configuration possibilities with display rules
Example from the browser console: