Pendo Web Agent

Version 1.1.61

Fixed Handling events on IMG tags where embedded images were used instead of URLs

Version 1.1.60

We have pushed version 1.1.60 of the Pendo agent live to the world.  Per the previous blog post, this contained a lot of cleanup, as well as some support for new features.

Version 1.1.61

Happy 2015! We have a new version of the agent coming out this week, and with it, our release candidate. Feel free to play with it at

Changed Now Lightbox guides can optionally use HTML elements on the page to decide whether or not they should be shown. Just like tooltips. They still look the same way. (The in-app support for this feature has not been released yet).

Changed We’ve added css classes to the tooltip Guide’s arrow that correspond to the direction of the arrow. This will allow you to specify css selectors in your css files to add different styles to the pendo guides. As a reminder, here is a list of supported CSS to style the guides.

Fixed Large amounts of refactoring and various fixes for reliability and guide rendering consistency.

Welcome to the Pendo Platform Developer Announcements blog

It’s a new year, and with the new year, comes a couple changes from Pendo.   Starting immediately, we are going to start pre-announcing any changes to the pendo “agent” – the js library that you load into your application that runs all of Pendo.  These announcements will happen on this blog, so we highly recommend someone from your team signs up for email alerts (see the box on the right) or the RSS feed for this blog.

When we are ready with a new agent change, we will announce it here, and release a release candidate version.  You can use that release candidate version to test things out on your end.  Note -we have every intention of making our agents fully backwards compatible, and we of course do thorough testing before we release, but we wanted to give our customers the chance to do testing on their side as well if they so wish.

The most recent release candidate will always be found here: You may want to use the release candidate in your internal/test instances of your product as a general practice.

Here is a support article stating the supported API for the agent.

When we announce a new release candidate, we will give a minimum of 2 days before pushing out the new version everywhere (except in cases where there is a critical bug that needs to be fixed immediately).  If you see any issues with the release candidate, please notify us immediately at [email protected]..

Testing with the release candidate on your end is completely optional.  When we push out new versions, you should not need to make any changes on your end.  For those customers that want more thorough testing on their own end though, they now have that ability.