We use ‘session cookies’ to allow you to use our software dashboard effectively. They are also used with the pages (advocacy, fundraising etc) that your supporters take action on. They are not used for any other reason and stop working a short period after you leave our site. You can find more information on our session cookies on this page.
Why do we use cookies?
For supporters viewing your pages, we use session cookies. These types of cookies are never written to disk but instead are stored in memory. If the browser is closed, or if the supporter browses away from the Engaging Networks pages, or after a certain length of inactivity, then the session cookie is lost. This also means it can’t “track” activity once the supporter leaves your pages.
The software needs to use these cookies otherwise supporters would not be able to proceed through your pages quickly and easily without having to authenticate or reprocess their data on each page. It also means that you are able to link up pages, or use multiple pages together, for your advocacy actions and donations.
The session cookies we use are necessary to enable the software to function as it does, without them we could not provide the service to you as set out in your contract.
You do not need consent from your supporters to use these cookies as it’s within Engaging Networks’ ‘legitimate interest’ (under GDPR) to utilise them. It is up to you – as the data controller for your supporter data – to determine whether you should let your supporters know that this activity is going on. You can take the cookie information in the table below and add it to your own privacy or cookie policies.
What cookies do we use on pages?
These are the cookies we use to display Engaging Networks pages to supporters.
If you use additional services, such as Google Analytics or Optimizely, you will have additional cookies in play.
|
Name |
Use |
|
JSESSIONID |
Standard session cookie created by Java application servers, used to serve the pages on the browser. |
|
en_sessionId |
Used to keep track of page sessions across the cluster. Sessions can contain form data, page state, query parameters, and authentication information. |
|
en_cartId |
E-commerce pages only. This cookie helps in keeping track of the supporter’s cart items as they move around the site. |
What cookies do you use in the software?
For users of the software, these cookies are used:
|
Name |
Use |
|
JSESSIONID |
Standard session cookie created by Java application servers. |
|
en_dashboardId |
This is a persistent cookie, which helps keep track of an admin user’s preferences whilst using the Engaging Networks interface. |
|
ensandbox |
Sandbox accounts only. This is a persistent cookie, that is only used in cases where a ‘Sandbox Account’ is utilized in order for agencies and partners to test various account setups. Users of these accounts must accept Terms of Use, in order to use the pre-setup account. |
Other tracking methods
We add an invisible tracking image inside emails, which is used to determine whether a supporter opens an email.
Note that messages sent to targets from email-to-target pages can be stored unless set not to via the account settings.