Dynamic email lets you do a bunch of cool new things:
Clients can now set up more flexible triggers to get alerted in real-time if free text responses contain certain text.
To help with troubleshooting and security, we've added an audit log that captures virtually all changes by all users in the account.
Increasingly, our large clients have multiple accounts -- e.g., multiple brands or subsidiary companies. We've now made it easier to login to multiple accounts with a single username.
To improve privacy, we've added an option for accounts to not log, log all but the last octet, or log the full IP address. This option is set at the account-level.
We've made a bunch of infrastructure upgrades to ensure we stay fast and available as we continue to grow.
We've fixed some bugs related to grouping free text responses in reporting.
We've improved and enhanced client integrations under the hood.
We made a bunch of performance and security enhancements to prep us for the next stages of growth.
Now you can see which Page or View a user was on when they submitted a survey
Chrome is going to start barking for providers that don't have this, so we added it.
Previously on-close and on-complete were bundled. But it turns out that it's helpful to treat the two separately, so we've enabled them as independent callbacks in our platform.
Previously, our SDK supported a single fixed theme. On web, our clients have had the flexibility to make changes to how the surveys look via our console. Now clients can have similar control for App-based surveys & polls as well. Like on web, different surveys can have different formatting now too.
We've added some new columns to help build pivot tables easier.
Who doesn't love a little winter cleaning? We've fixed a bunch of bugs that have been on our wishlist for a while including how tagging free text shows up in the platform and some XLSX reporting bugs.
Staying on top of loads of data is difficult, so we've created performance alerts that tell us if big/unexpected changes happen so that we know right away and can react appropriately.
When you really need to slice and dice your data, a BI platform is the right tool for the job. We've made it easier to integrate with BI and have created a custom report framework to give you a starting place.
Request #1 for SDK has been to make 'inline mode' work on SDK more similarly to how it does on web. Now it does. Here's how it works:
Work at a company where they refuse to upgrade your computers from Windows 95? Well, we've made some enhancements so that the bar charts display better on older email clients too. And we threw in Dark Mode support for newer Macs while we were at it.
Ever get frustrated that Question 1 gets 2x as many responses as Q4 in a survey? Now you can randomize the order to even out the responses of each question.
We've upgraded our SDK to respect the timer-based targeting that already existed for Web.
We've made accessibility enhancements so that surveys work better with screen readers. These enhancements were rolled out platform wide, so you needn't do anything to take advantage of them.
For clients that don't want Evals in third party JS libraries, we've created and maintain a version that removes them. The only downside is that callbacks need to be deployed by the tag manager instead of Pulse Insights.
Bots load a lot of pageviews on your sites. If you don't detect them, it looks like real impressions in your reporting. Since we're not ready to bow down to our AI overlords, we have made enhancements to stop asking for their opinions.
Pulse Insights is fast, but if any particular response takes more than 1 second, Pulse Insights will automatically respond with a static response of 'no surveys to return' which will keep your websites and apps loading quickly.
You can now filter responses by date on the dashboard to make it easier to look across surveys for specific time periods.
We've improved how we handle single page apps.
We've made a bunch of under the hood enhancements so that pulling large datasets goes faster.
We've created a special-case question type--NPS. This enables faster creation of NPS questions and improved metadata for when you ingest this data for your internal dashboards.
Ever want to have something like "Please help us improve our website?" above your question? While we've done this for a while, it was a bit hacky. So now we do it for real. And while we were at it, we added some other goodies too:
Instead of presenting a specific survey, you can now present a category of surveys by passing Pulse Insights an Event and allowing one or more surveys to respond to those Events. This also has operationable benefits in that you needn't make any changes to your website or app code to update surveys vs. calling a specific survey by its ID.
Collect customer-initiated feedback from your sites, apps, and emails. This feature enables links in footers, navigation menus, and docked tabs.
Hear ye, Hear ye, you can now see our console. We've changed our color scheme to increase contrast and make things easier to see.
To make it easier to stay on top of free text responses, you can now setup Automations that trigger emails based on the content of responses. You can set up multiple rules and rules can have conditional logic that you configure via our Console.
We've switched from IBM Watson to Google NLP to get sentiment and entities. Results are available in the open-ended text data table and XLSX reporting.
It's now easier to target a survey or campaign to a single page.
You can now configure a survey or campaign to treat history state changes (quasi-pageviews) as new pages by checking the Single Page App checkbox. This should make it easier to deploy surveys and campaigns in SPAs.
Sometimes you need something to trigger even if a user has met his/her frequency cap. An example might be a thank-you message from an in-email survey. Now you can set individual surveys or campaigns to ignore the cap.
This is helpful if you only want to collect feedback from known/authenticated users so you can tie back responses to the user's CRM records.
New email templates let you stay on top of results without having to open attachments! Of course, the attachment is still there so you can dig deep into the data when needed.
Now you can customize the text of the start button on the invitation card. You can also show no button at all by selecting 'hide' in the options tray.
You'll find the toggle in the options tray of each card only when AAO is turned on.
Sometimes you just want to show all your questions at once...just lay it all on the table. Now you can. This is great for persistent feedback comment cards and/or modal overlays to capture feedback. Enjoy!
As enterprises have added more and more microsurveys over time, finding the one you need has sometimes gotten difficult. This should help.
You can label surveys in the Edit > General tab.
You can now upload images to use as answers. Use for thumbs up/down. Stars. Asking users if they prefer this or that. The capability supports using existing images or uploading new ones. Show just images or both images + text.
SDK now supports callbacks when a user answers a survey or poll. Also, you can check whether a given user has answered a survey.
Our iOS and Android SDKs now support polls and inline surveys that more closely mimic our web-based approach.
Upload custom images via our console to display along with the micro survey text.
We've made it easier to launch polls in your emails by creating link parameter that shows results.
We've added browser version to reporting and additional columns to the Devices sheet.
You can click the number of responses for each card in reporting to view results in descending order.
You can target users in particular locations--countries, states, and DMAs--in Pulse Insights now.
Making sense of large amounts of unstructured data is a classic problem. We've made it easy to categorize or classify open-ended comments. And now, we graph the frequency of occurrence of each comment category which helps you keep feedback in perspective.
SDKs are updated to support displaying poll results in native mobile apps.
We've made some updates so that Pulse Insights surveys work well with screen readers.
Happy to announce that it's now dead easy to analyze open-ended text responses in the platform. Lightning fast sorts and searches make it easy to zero in on the right responses.
In order to ensure any single person doesn't get over-surveyed, you can now create a maximum impressions per person for a time period of your choice.
Previously our XLSX export placed each response to a follow-up question on its own row in the XLSX. To aid in easier pivot table creation, we have added an additional tab that places follow-up questions to a survey by the same device/user as additional columns on the same row. This is in addition to the existing 'Individual Rows' sheet.
We have upgraded components of our platform to make the console run faster!
After being used for the past year in private beta, Progressive Profiling is now GA!
Display surveys based on advanced on-page user interactions including user scrolls, content coming into view, clicking certain page elements, likely exit behavior, and more.
You can now append the query string pi_present=[survey id] to force any live survey in the account to display. Previously this was done in the developer tools console only. This makes sending test links much easier.
For superadmins, you can now search and destroy certain answers. This is useful if test data makes it into production surveys.
For single page applications, Pulse Insights now automatically checks for eligible surveys on hash change. Previously client dev teams had to manually check.
We have implemented a number of security enhancements related to authentication, idle logout, and password resets - some customer-facing and some under the hood.
For updating CRM records based on user responses, Pulse Insights can now use client key to update CRM records with account-specific and question-specific logic.
Configured at the account-level, you can now suppress certain IP addresses from receiving surveys. This is helpful for avoiding company employees from seeing on-site or in-app surveys.
Account users will now get alerted when surveys reach their goal and stop displaying.
Pulse Insights can create client-specific daily feeds of user activity keyed off client key for CRM ingestion.
Get the same data exports you can download on-demand delivered via email at the time and frequency of your choice. Both platform users and external email addresses are eligible to receive exports.
You can now share CSS across surveys.
By popular request, exports can now be scheduled to arrive in your inbox. You can select all or specific surveys, start and end dates, send frequency, and recipient(s).
Our iOS SDK is now available. With our person-level identity services, survey targeting across web and native environments, APIs, Android SDK, and iOS SDK, you can now seamlessly collect customer feedback in virtually any digital channel.
Android SDK is available and iOS is coming soon!
You can now use the number of days since install and number of launches as triggers for native app surveys.
You can target or exclude surveys based on the view name. Now a single survey can collect feedback across mobile apps and browser-based environments. Like with URL targeting, both 'contains' and full regex are supported.
With our forthcoming native app SDKs, we've added a number of new targeting options:Include/exclude native apps from rendering a survey.
Sometimes the same survey is relevant to the same user after a period of time. For example, maybe a satisfaction question is relevant after 60 days. Now you can optionally allow surveys to retrigger post-submit.
Previously, it displayed as an overlay centered on the screen.
You can pass your client key (unique customer identifier) to Pulse Insights to deterministically link users' browsers and devices. Subsequently, Pulse Insights can _decision_ based on client key instead of cookie. Implications: if a person answered a question on her home computer, you wouldn't later ask on her work computer because she already answered it. Additionally, this opens up enhanced decisioning in email and other channels.
Now you can show visitors the results of a survey!
Reports and data exports will now load faster!
Lots of surveys in your account is a learning badge of honor. Now archived surveys are not visible by default but there's a handy link at the bottom of the dashboard to view the archives.
We added Survey ID in reporting to enable more advanced analysis in Business Intelligence tools such as Tableau and Domo. Also long inline targeting options above 255 characters are now supported. This is useful if a single inline survey is to be used across multiple page templates and thus multiple targets are required.
Faster console page loads!
Ever wanted to know how just some people answered a follow-up question? We now can filter any follow-up question based on how users respond to a question. Just click any bar chart and the reports update in real-time.
The arrows used to describe follow-up question flow are now present in reporting. This will provide more context about who received which questions while looking at reporting.
There's a new randomize option in town: randomize all options except the last. This is helpful if you have an 'Other' answer that you always want to be last.
We have added three new data points to your XLSX exports: number of user's previous visits, pageviews in current session, and device type (mobile, tablet, desktop).
Some sites have a different page layout for mobile devices than tablet/desktop. We've added an option to render inline surveys in a different part of the page for mobile devices.
For the times when one answer isn't enough, Pulse Insights now supports multi-select questions.
Ever want to help users in the moment based on how they respond to a survey? Now you can. Today we are launching an add-on to our Pulse Insights Micro Survey product that enables real-time optimization of your digital experiences. Take over the whole screen with beautiful bespoke content to guide your users.
In addition to executing callback code when a survey is fully complete or closed, we now have the option to execute onanswer callbacks each time a single question is answered. This is helpful if a survey has many follow-up questions or ends on a Custom Content Card instead of a standard Thank You message.
You can now specify whether to place a survey below or above a div when creating inline surveys. This makes it easier to get the survey exactly where you want it.
Ever wanted to ask a follow-up question at a later time to someone? Now you can target questions based on what someone has previously answered. You can use this in conjunction with all of our other targeting to ensure you're asking exactly the right people for feedback.
Now you can create a copy of a survey with a click of a button. All settings are copied over including formatting, targeting, and questions but the survey is left in Draft mode for further editing. e
You can now easily target surveys based on a user's device custom data. For example, maybe you want to only ask a question to users/devices who have over 50,000 loyalty program points. This feature works in conjunction with device/user-level custom data for the current user. The device/user custom data can be set on any prior visit or pageview and then it is available for survey targeting in any future pageview or session. Targeting options are flexible:
This feature will enable a whole new level of laser-targeted learning.
Sometimes you don't just want to target a survey to a particular URL, but rather want to target surveys based on a user's behavior. For example, maybe you want to ask a question of a user after viewing 4 pages on the site. Or maybe you only want to talk to first-time visitors. This is now possible in combination with previous survey targeting options.
"Inline" surveys that target a particular part of the page will no longer display if the target div isn't found. Previously the survey rendered at the bottom of the page.
It's now possible to set custom data that persists for the current device/user across surveys. For example, maybe you want to attach the current user's loyalty program point balance and internal customer segmentation. The custom data can then be used for:
If the custom data describes or adds context to the current survey impression or submission -- use custom data.If the custom data describes the user or device and is valid over time -- use device-level custom data.
We now offer the option to not show a particular survey again if a user closes it without answering. This affects only the user that closed the survey. Other surveys will continue to render according to their targeting criteria.
Maximum answers changed from 6 to 10. Enhanced Free Text widget formatting. Added support for advanced question-level formatting. Fixed XLSX export for large reports. Fixed bug related to percentages with date filtering.
Separate out collaborators that need reporting vs. those that can manage surveys (formatting, questions, integrations) and users.
Collect qualitative free-text feedback from users in your microsurveys. Just like single-answer responses, feedback can be integrated into other systems like web analytics, CRM, DMP, and A/B testing.
Need to use a Pulse Insights Microsurvey outside of a webpage? Maybe in an email or native application? Use the new Survey API to submit survey responses. See documentation for additional details.
Single-select questions now have an option to randomize order. Selecting this option will display the possible answers in random order when the survey widget is rendered for end users. This can prevent biases related to the order of the options.