The CAPA website makes use of HTML5 local storage as a cache, so that it can quickly display Alerts settings, use your User ID, and remember your authentication token between browser sessions (ie. if you leave this site or close your browser and open it again, you won't need to log in again). If you are interested in what data we are storing in local storage for this site, you can get a live view of it by clicking here.
CAPA makes use of several technologies to collect data from you as you use the website. They are detailed below. The data collected by these tools is only directly viewable to CAPA and the companies hosting the analytics tools, however it may be disclosed in an anonymous, broad aggregate format in certain situations (ie. a potential advertising client would want to know how many views per month our website gets).
CAPA uses the industry-standard Google Analytics platform to collect data related to how users are using the site. We use this data in an aggregated form in order to figure out overall site traffic, which types of content are performing well, how long users spend on the site, how long pages take to load, how various marketing campaigns have performed and so on. This data is anonymous, unless you are logged into the site. When logged into the website (and only when logged into the website), your User ID is transmitted to Google Analytics and your activity will be linked to that ID. CAPA can then potentially use that data to identify the product usage of individual users and companies. Agreeing to this tracking is part of the Terms of Service for CAPA Membership and other products.
The IIRIS tracker is a service which helps our parent company (Informa) to track user behaviour across multichannel touchpoints.
It's used to:
- Track and understand user behavior across channels such as web, email and mobile.
- Understand how users interact with products on site.
- Collect, govern and model behavioural data.
Data collected when a crash occurs:
- URL - the web page address that the crash occurred on. This helps us quickly narrow the scope of possible crash causes.
- Error Details - this will contain a list of components that the error occurred within. Due to minification, this list usually isn't helpful, but sometimes it has helped us quickly get to the bottom of where an error is occuring.
- Browser Type - the web browser user-agent string. We use this to determine whether the bug only affects one brand/version of web browser.
- Page History - this is a list of the previous pages of the CAPA website you were on in the current browser tab during the leadup to the crash occuring. Pages from outside the CAPA site are not included in this list. We use it to troubleshoot whether something on a previous page triggered a bug that caused a crash on the next page.
- User ID - if you are logged into the CAPA website, your user ID will be transmitted. This helps us figure out whether it was a particular setting you had under your account that caused the crash.
- Message - if you've included any message in the crash data submission, this would be it. Note that automatic crash data submission doesn't contain a message.
Crash data is very helpful for our development team when it comes to troubleshooting and fixing bugs with the site. Previously we've used it to solve crash bugs with the financial graphs, traffic graphs, route maps, the Alerts sidebar and many other things.
Last Updated: 19-Jan-2023