Cookies
We do not use cookies but localStorage to save some information about the current messaging session. All the data we save in the localStorage is listed below
| Name | Explanation | Required for messaging | Contains | Type | Access | Valid | Domain | Version |
|---|---|---|---|---|---|---|---|---|
| parleychat_xIrisidentification | Device identification, used to recognize this browser during calls to Parley | yes | ID | string (alphanumeric) | Parley, local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_showMessengerDate | Last time the chat was opened | no | Unix timestamp | integer | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_messengerOpenState | Last 'state' the chat was in. Is used to show preserve the state when people navigate through your site | yes | enum not use cookies but localStorage to sa | string | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_minimizeMessengerDate | Last time the chat was minimized | yes | Unix timestamp | integer | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_closeMessengerDate | Last time the chat was closed | yes | Unix timestamp | integer | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_pushReady | Indicates if push is available on this device or we need to start polling for new messages | yes | true/false | boolean | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_lastNewMessage | Date of latest message. Used to mark to the user what the last message was that they could have read. | yes | Unix timestamp | integer | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_lastInviteNotificationTime | Last time the invite notification was shown to a user. We use this to prevent that we show the invite notification every time a user navigates around your site to prevent from looking like we 'spam' them. | yes | Unix timestamp | integer | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_sendedMessageTime | Last time the users send a message to the company | yes | Unix timestamp | integer | Local JavaScript, servers on domain | session | \ | 1.0.1 |
| parleychat_xIrisAuthHeader | User authorisation, is used to authenticate a 'registered'/logged-in user to Parley | yes | Hash (Authorization header) | string | Parley, local javascript, servers on domain | session | \ | 1.0.1 |
| parleychat_pushToken | The pushToken as generated by FCM. This is used to send the browser push notifications when the company replies to the user. | yes | Hash | string | Parley, local javascript, servers on domain | session | \ | 1.0.3 |
| parleychat_pushType | The type of push used by this device. This is used to "upgrade" old push tokens to be used with the new push type 6. If this value doesn't exist or doesn't match the value hardcoded in the library; it deletes the push information from the storage and generates a new one for this new type. | yes | Number | integer | Parley, local javascript, servers on domain | session | \ | 1.5.0 |
| parleychat_userAdditionalInformation | The additional information that is send with the device registration API call. | yes | Object | object | Parley, local javascript, servers on domain | session | \ | 1.2.0 |
This functionality has been removed in version 1.0.2. The chat uses localStorage for both unregistered as registered
clients. Instead the hideCloseButton setting should be used so the client can remove its cookies by clicking the close
button.
The messenger uses html5 localStorage and sessionStorage.
Upon loading the messenger, it will check whether or not there is an authHeader set in the settings.
If there isn’t one present, the messenger will delete all data from localStorage.
If there is one present, all data that is in the sessionStorage will be moved to the localStorage.
All the saved data for an “unregistered” user (unregistered means, there is no authHeader supplied in the settings)
will be deleted when the browser tab, that contains the messenger, is closed. This data is saved in the sessionStorage.
All the saved data for an “registered” user (registered means, there is a valid authHeader supplied in the settings)
will be kept when the browser tab, that contains the messenger, closes. This data is saved in the localStorage.