They say that data is knowledge and knowledge is power.

This new feature that we are releasing today is going to give you a lot of data, knowledge and power to make decisions.

It will allow you to know which user have seen each one your posts.

Unfortunately this implementation only works for new post views since today and you must add an extra parameter to the widget.

This is what you need to do:

Step 1.
Make changes in your widget. 
Here is a quick step by step on what you need to do.  
https://help.releasepad.io/article/6-how-to-enable-option-to-know-who-views-your-posts

Step 2.
Find the posts you would like to know more about and click "Who has seen my post?".
It's important to note that this information will be available only for the post views after performing step #1

Step 3.
See your data.

The notifications bubble indicator on widget was being reseted after a couple of days.  What this meant for end user were false alerts about new changes.

This has been fixed :-)

In the widget and public page, posts were displaying the creation date instead of the publish date.  

This has been fixed and pushed.  

Thanks Diana for noticing this :-)

In some special conditions, the words of some posts were overflowing to the left, creating an unpleasant experience for your users.

This has been fixed.

Improved the responsiveness of ReleasePad for mobile phones.The experience has been improved so that it loads faster and screens are rendered correctly based on device.

This morning we had some intermittency on our service.  This was related to a change that Amazon AWS did on Cloudfront.We got in touch with support and managed to solve the issue.

In some special cases there were some css conflicts between the widget and the hosting page, particularly with headings (H1, H2, H3, ...).

This issue has been fixed and pushed.

Pushed a change that fixes the ordering of the posts.  Instead of using the creation date it now uses the publication date.

We were having some issues with the current way of storing data for the user facing widget (the one you use on your product) related to local storage.  Some logout implementations usually delete all local storage, therefore erasing all the widget data.  This caused that each time a user logged out and the logged in it would appear as if it hasn't seen any of the updates, therefore creating confussion.

We switched to cookies to fix this issue. 

For privacy matters it only stores the id from last seen post.

We updated our CDN provider for a faster one and with edge locations all around the world.  This means that when a user loads the widget it will be sent form its closest physical location, therefore reducing loading times and latency ??