Technical Documentation

Pulse Insights is an Agile Learning platform designed to deliver actionable insights to your organization that inform web and mobile experience optimization. Pulse Insights generates high response rates and fast learnings by asking targeted groups of users quick questions inline to their experience.

Installing Pulse Insights

In order for surveys to display, place your designated Pulse Insights code snippet (which contains your unique Pulse Insights ID) on all pages that will collect feedback just above the closing body. We recommend placing the code snippet on all pages of your entire site(s). The Pulse Insights code snippet also works well when deployed by a tag management system.

Example

Note: The code snippet above is used for example purposes only. You can also find your unique code snippet under Pulse Insights > Setup > Get Code Snippet, or in your Integration Guide provided to you by your account team.

QA Testing

Pulse Insights offers a method to QA surveys before they go live to end users so that you can confirm they look great across browsers & devices.

Test/Staging Environments: You can use the same Pulse Insights code snippet across multiple environments (Development, Staging, Production). Place your designated code snippet on the relevant pages of your test or staging site and use our Live Preview feature in the Pulse Insights Console.
Soft launch on Production Site: You can also use the Live Preview feature to privately QA surveys in production environments for situations where Test environments aren’t accessible.

For more details on Live Preview mode, see our user guide here.

Implementation FAQ

Which pages should I add the code snippet?

We recommend placing your snippet on all pages of your site(s). If you use a tag management system, you can deploy this tag on ‘all pages.’

If you’re placing the tag directly onto the page, we recommend placing it in a template such that all current and new pages will have the tag.

Where should I place the code snippet?

We recommend placing your Pulse Insights Code Snippet just above the closing body tag </body> in the page or configuring to fire after the page has loaded.

Can I use a tag management system or container tag to deploy Pulse Insights?

Yes. Pulse Insights is compatible with tag management systems.

However, it should not be placed inside of a Doubleclick Floodlight Tag, as Pulse Insights needs access to the parent page and Floodlight tags are inside an invisible iframe.

Do I use the same code snippet across secure/non-secure pages?

Yes. The code snippet works across both http and https pages. There are no special configuration settings to enable HTTPS calls to render properly.

Will the Pulse Insights tag slow down my site?

The code snippet loads asynchronously and won’t block the rest of the page from loading while it loads and executes. Additionally, there is redundancy and SLAs to ensure high uptime. The Pulse Insights JavaScript is loaded from a CDN so it is highly available and loads from a server close to the end user.

What if I have multiple domains, subdomains, or environments?

You can use the same code snippet across all domains, subdomains and environments on which you’d like to serve surveys and collect user feedback.

What if my site is a Single Page Application (SPA)?

We recommend adding pi(‘pushBeforeGet’, true); to your code snippet. This command will push the state before making the serve call for surveys and will ensure that the serving logic is using the latest URL for survey targeting.

Example:

Pulse Insights Console: User Guide

The Pulse Insights Console - this is where you can create, edit and view surveys, view survey results, and more. You should receive an email invitation to the console with a link to finish setting up your account. On your first login, you will be prompted to create a password. If you forget your password you can click the “Reset Password” link.

Once you are logged in you can click on your name in the top right to open a dropdown menu, click on “Edit Account” to edit your name, email address, company name and to change your password.

Dashboard

Pulse Insights gives you an at-a-glance view of your surveys from your Survey Dashboard. The dashboard is the first thing you see when you log in and you can navigate back to this view at any time by clicking on “Surveys” in the top right navigation bar, or by clicking on the Pulse Insights logo on the top left of the navigation bar.

The dashboard includes an index table of all of your surveys. Each row shows the survey’s:

  • Survey Name
  • Status:
  • Draft: this is the default state when creating a survey, the status before a survey goes live. A survey is not eligible to fire while in this status.   
  • Live: the survey is eligible to be shown to end-users (depending on targeting criteria, such as if the current date is between the established start and end dates). 
  • Paused: means it is temporarily not firing for end users, but is expected to be turned back live
  • Complete: means the survey has reached either its submission goal or end date
  • Archived: is complete and not expected to be turned back live. Archived surveys are not actively being managed or analyzed, but reporting data is preserved. Archived surveys are not shown in the dashboard by default, but you can view them by clicking on the “Show n archived survey(s)” link in the bottom right. 
  • Metrics such as:
  • Impressions: the number of times the survey was shown
  • Submissions: the number of times at least one question has been answered
  • Submission Rate: the ratio of submissions to impressions
  • Goal: the submission target number and the % of that goal reached (total submissions/submission goal). 
  • Date and time of the last submission
  • Date of the last edit to the survey
  • Name of editor who made the last change to the survey

The survey index shows metrics for the last 30 days by default, but you can also click to view all results, the last 7 days, results from yesterday, from today, or choose a custom date range. 

You can also sort the table by clicking on the column header names. 

From the dashboard you can:

  • Create a new survey by clicking the “New Survey” button in the top right.
  • View or edit an existing survey by hovering over the survey row to reveal the “Edit” button.
  • View survey results by hovering over the survey row to reveal the “Results” button.
  • Create a survey group by hovering over the survey row to reveal the “Create Group” button.
  • Delete a survey by hovering over the survey row to reveal the “Delete” button.
  • Duplicate a survey by hovering over the survey row to reveal the “Duplicate” button.
  • Create and Manage survey tags

You can use the search bar in the top left to search for a survey by name or by tag. You can also manage your tags here. 

Setup

There is a “Setup” dropdown in the top navigation. From here you can:

  • Get Code Snippet This is your unique code snippet for your Pulse Insights implementation. See implementation documentation here.
  • Data and IntegrationsEnable and manage survey callback code snippets: impression callback, viewed impression callback, Onanswer callback, Onclose callback and Oncomplete callback. See more information here.
  • ThemesYou can create themes to customize colors, fonts, and backgrounds via JSON “themes” so the formatting matches your brand. To create an account-level theme, click on “Setup” in the top menu bar and select “Themes”. Then click the “New Theme” button in the top right corner. Name your theme, choose between CSS or Native JSON and enter your code within the text editor. To save, click the “Update” button in the bottom right. The Themes page will show all the themes you have associated with the account: the name of the theme, date and time when it was last edited, name of the person it was last edited by, and a list of all of the surveys that are using the theme. If you hover the cursor over the row, you will see the options to View, Edit, or Delete the theme.
  • Global Targeting
  • You can enable user-level frequency capping to restrict the number of times a single individual is shown a survey. You can set the maximum number of impressions and the period for which the user won’t exceed the max number. Check the box and then enter the number of maximum impressions to show and the number of days, hours or minutes. At the end of the period, the counter resets and the user will be eligible to see survey impressions again. 
  • You can also create a list of IP addresses to block on your account. This feature is typically used if you don’t want internal employees of your company answering surveys. Pulse Insights will prevent Live surveys from displaying on those IPs for any survey in Live status. Draft surveys can still display while in Preview Mode so you can still QA surveys.


  • User Management - Manage the users who have access to your Pulse Insights account, invite users, and assign access level (full access or reporting only). While Reporting only access only gives a user the ability to view survey results, Full access users can:
  • Manage users
  • Edit survey questions, formatting, or metadata 
  • Create or delete surveys
  • Manage integrations
  • Activity Log: This page shows a running log of all account changes, the time and date of the change, and the user who made the change.  
  • Support - If you need help, please contact support@pulseinsights.com

Creating a Survey

Clicking on “New Survey” in the dashboard will bring you to the survey creation flow. The process to create a survey consists of three key steps

1) Defining the basics like Survey Name and Submission Goal (General)

2) Defining the questions and survey formatting

3) Defining targeting conditions that define when survey will render to end users

Step 1: The Basics

Start by giving your survey a name. We suggest structuring your naming conventions so that it remains easy to find surveys as your learning plan grows.

There is a dropdown to choose the status of your survey. “Draft” is the default state for new surveys, but you can also change to the following statuses:

  • Draft: the survey is not currently firing; used before a survey launches. The survey must be in Draft status for Live Preview mode
  • Live: the survey is firing and eligible for end users
  • Paused: the survey is temporarily not firing for end users, but is expected to be turned back live in the future
  • Complete: survey has reached either its submissions goal or the scheduled end date
  • Archived: survey is complete and not actively being looked at 

Next, enter a number value in “Survey Goals” input box. This is the number of responses you would like to collect to feel confident that you have a representative set of answers to your question. Once the survey goal is met, then the survey will stop triggering. The goal is set to 5,000 by default. 

You can optionally add tags to your survey for organizational purposes. You can create and manage tags via the survey dashboard in the search bar. You can add multiple tags to a survey. 


Step 2: Defining Questions and Formatting

The next step is to define survey questions to ask, to establish follow-up question logic, and to configure how the survey is formatted for end users.

The page is divided into question definition (left) and formatting options (right).



Invitation (optional)

You can optionally add an invitation to your survey, which enables users to opt-in to take a brief survey. Since Pulse Insights Surveys are often just one question long and used in-line, an invitation to take a survey is typically not necessary and is not used by default. You can add an invitation by clicking the “+” on the “Add Invitation” card and filling out the required fields: the invitation text and the opt-in button text. 

You can also click on the “Options” arrow to expand additional configurations. You can optionally hide the opt-in button. 

Example Invitation: 


Add question, question types

Click on the “+” on the “Add Question” card and select a question type to add a question to your survey. 

Pulse Insights supports the following question types: 

Single Choice

A single choice question enables the user to select one appropriate answer from a list of options.

Example:


To configure single choice questions, first type out the question text, then you can add response options by clicking the “Add Response” button. You can remove response options by clicking the X on the right of each line.

You can also add images to your responses, such as a thumbs up/down. Click on the image icon on the right of each answer. This will open a modal where you can select an image to use, or upload a new image file. You can then configure if you would like to display just the image, or the image and text (and where to position the text in relation to the image: beneath, on top, to the right or left of the image). Next, you can enter the size you would like the image to render on desktop, table and mobile (in px or as a %). You can also add fallback text, which will be shown if the image cannot load.   



The Randomize Order of Responses 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. There are two settings:

  • Randomize all responses
  • Randomize all except the last — this is useful if you have an ‘Other’ option that you want to remain last


In the “Option” menu, choose a button style for your responses. You can choose from 3 styles: 

Radio Button:

Example:

You can also configure how many radio buttons you would like to appear on one line on Desktop and Mobile views.


Standard Button:

Example:

You can also configure the button width (fixed or variable), the number of buttons per row, and the button distribution (Left/Center/Right/Space Between/Space Around/Space Evenly) for desktop and mobile views. 

You also have the option to add additional text before and/or after the question. Before and after answers?

Dropdown Menu:

Example:


For the dropdown menu button style, you can configure the Default Label, which is what the user will see before selecting a valid response. The default label text is “Select an option”. 

Multi Choice

Multi-Choice questions enable the user to select one or more responses at a time. 

Similar to the setup for Single Choice questions, to configure Multi Choice questions, first type out the question text, then you can add response options by clicking the “Add Response” button. You can remove response options by clicking the X on the right of each line. For Multi Choice questions, you can set the maximum number of checkboxes the user can select. If you enable this option, you can enter the number of maximum responses a user can select (e.g. Select all that apply, up to 3). 

Under “Options” you can configure the number of choices per row for desktop and mobile views. 

Free Text

Free text questions allow you to collect data from users in their own words. It is helpful if you want to hear the nuance of language choices or if you are unsure of what types of things users might say so can’t yet devise a question with a fixed set of possible answers. Free text questions tend to have a lower response rate because you’re asking more of the user.

Example:

For Free Text questions, type your open ended question for the “Question” value. Hint Text is the text that will display in the text input box before the user starts typing his or her answer. You can also change the button text in the “Submit Label” field (the Submit Label is “Submit” by default). You can also configure error messages in the Error Text field. For example, you can mask personal data, such as phone number and email address (See Account Settings section) . The error message will display when there is a value detected that has masking enabled in the Account Settings.

By default, the text input box will have a height of 1 line and a maximum length of 141 characters. You can change these values in the “Options” section.


Custom Content

Start by naming the card. Survey participants will not see this name, this is just for organizational purposes. Next, click on “Manage Content”. This will open up a page where you can edit your custom content card.  Custom Content supports executing JavaScript, which can be configured using the simple WYSIWYG editing or advanced HTML editing, complete with code beautification and line numbers. You can also upload images, which are hosted on our CDN, Cloudfront.

WYSIWYG editor:

Code view:


This is a powerful and useful tool, but with great power comes great responsibility. Improper usage could impact the entire webpage, so use caution and follow proper QA processes before launching code into a production environment

There are several options available for the Custom Content card including:

  • Enabling a full screen take over, with configuration for a background color and opacity.
  • Auto close after n seconds
  • Auto redirect to a page after n seconds



Net Promoter Score (NPS)

Pulse Insights also supports NPS questions (0-10 rating of the user’s likelihood to recommend a company, a product, or a service to a friend or colleague). 


This question type is preconfigured with the NPS question and the 0-10 options for rating. 



You can also customize how many answer options show up per row on desktop and mobile. (e.g. all 11 answer options for desktop, and split into 2 rows with up to 6 answers per row on mobile). 

You can also add additional text before or after the question, and before or after answers. This comes in handy when you want to label the range (e.g. 0 is “very unlikely” and 10 is “very likely”). 



Branching Questions

You can define the follow-up question by dragging and dropping from any question or response to any other follow-up question as shown above. In this case, if the user indicates that the purpose of their visit was not represented in the list of available options and answers as “other”, then you can follow up with a Free Text question where the user has an opportunity to elaborate.  

Simply drag from the endpoint of one question or answer and connect the arrow to the question you would like to ask next. If there isn’t a branching line drawn, the default next step is the “Thank You” message.

Thank You Message

A Thank You Message is displayed when a user completes a survey submission. It automatically closes after a few seconds so the end user can get back to business.

You can also optionally show the survey results to the end user, which turns a survey into a poll. Simply check the ‘show survey results’ checkbox on the Thank You card.

Widget Type

On the “Questions & Formatting” page, you can also choose how you want your survey to be displayed. There are 5 options, called “widget types”. Each widget type has different placement configurations. The 5 widget types are:

The Widget Type panel consists of 3 components: picking the widget type, selecting a theme (optional), and configuring the placement of the widget type. To pick the widget type, simply click on the widget type you prefer in the “Type” section of the “Widget Type” panel. A green check mark will appear on your selected widget.

 For each widget type, there is an option to display all of the questions at once (which will show all of the questions, even the ones that are set to display only as a follow up to a particular answer). There is also an option to randomize the question order, however if you enable this feature, then you should not use the question branching feature, since branching logic is used to show questions in a particular sequence. 


Themes:

You can also select a theme for your widget. Any theme associated with your account will show up in the dropdown menu. See the “Theme” section in “Setup” for more information on how to create and manage themes. You can select a CSS theme and a theme for SDK implementations.


Docked Widget

The docked widget displays the survey along the bottom of the browser on top of page content. Use the % option to shift the survey relative to the browser width from the left or right browser edge. Use the px to shift the survey a fixed number of pixels from the left or right browser edge.


Inline

Inline displays the survey within the content of the page (not on top of the page content like all of the other widget types). 

You can target CSS Selectors for desktop, mobile and SDK. There is an option to place the survey at the beginning or end of div content. Pulse Insights will suppress survey rendering if the specified div is not found on the page. Since the page structure isn’t necessarily known at the time Pulse Insights selects an eligible survey, the CSS Selector defined in the survey is NOT considered targeting criteria for the purposes of eligibility.

Additionally, the survey can optionally be offset from the div in either % or px by using the top, bottom, left, and right offset options.

For SDK implementations, you can set the height of the widget as a percentage.


Top Bar

The Top Bar widget type displays the survey docked along the top of the browser using the full width of the page. It can display on top of the page or can optionally push the page content down to accommodate the survey. However, it cannot push down fixed position content.

For SDK implementations, you can set the widget height as a percentage.


Bottom Bar

The Bottom bar widget displays the survey docked along the bottom of the browser using the full width of the page.

For SDK implementations, you can set the widget height as a percentage.


Full Screen

The Full Screen widget displays in an overlay over the entire page content.

You can set the margin of the widget as a percentage (%) of the full screen. 


Widget Details

After you have configured the options in the Widget Type panel, you can click on the right arrow to configure the Widget Details. Here you can enter the desired width of the Docked Widget (in pixels), choose a widget background color by entering a hex value or by selecting a color with the color picker, or choose a widget background image by uploading an image file or by entering an image URL. 


Question Formatting

The next formatting panel is Question Formatting where you can customize the font color of the question text and answer text. You can enter a hex value or select a color from the color picker. 


Advanced Formatting

The Advanced Formatting pane enables full control of survey styling by adding custom CSS.

Survey-level advanced formatting is useful in conjunction with our Themes feature. If you’re using a theme but need to adjust just a few parameters to make the survey look right for this context (say you need to remove a close button for a theme that usually includes one), you can apply the changes here without having to create and manage a whole new theme.

You can click on the “See a list of selectors used in surveys” link to pull up the list (below) of key CSS selectors, or you can use browser developer tools to get the full inventory and style as needed.


Save all your changes, and click “Next” to move on to the next step, targeting!

Step 3: Targeting Conditions

For account wide targeting, please see “Global Targeting” in the “Setup” section. 

The configurations in “Targeting Conditions” determine under which circumstances the survey is eligible to render.



Device Targeting:

Click on the device to enable surveys for the device type. Surveys can show on desktops, tablets, mobile devices, in iOS and Android applications and in emails. 

Note: some types (such as iOS, Android and Email) may have additional technical implementations. 

Dates:

You can optionally set start dates/times and end start dates/times and the survey will only display to end users if the current date is between the established start and end dates. If no start date is specified, then the survey will be eligible to render once the status is turned to “Live”. If no end date is specified, then the survey will continue to be eligible until the submission goal is met, or if the status is changed to any status other than “Live”.  

Display Survey If:

Here you can determine which URLs the survey will be eligible to display on. Select from the dropdown one of the following options:

  • URL Contains - the default and most frequently used option
  • Regex Matches - Regular Expressions (Regex) is available to solve for advanced use cases for both browser-based and native application based use cases
  • URL is - targets a specific URL
  • View Name Contains - mostly used for native mobile apps; e.g., to target the Home page of the application
  • Regex View Name Matches - Regular Expressions (Regex) is available to solve for advanced use cases for both browser-based and native application based use cases
  • Event Name Contains - Using event names allows you to call a specific survey (or surveys, if A/B testing) with matching “event name contains” targeting to a specific page or after a particular user action (e.g. clicking on a button).

Next, enter the URL of a page, View name, or Event name in the text field.

Click on “Add Another” to add another URL/View Name/Event Name to the whitelist.

URL Contains Examples:

  • URL Contains pricing would display the survey on pulseinsights.com/pricing and pulseinsights.com/pricing/request
  • URL Contains pulseinsights.com would display the survey on all pages of PulseInsights.com
  • URL Contains console.pulseinsights.com would display the survey on all pages of the console subdomain
  • URL Contains utm_source=sem would display the survey for campaigns tagged with sem

Regex Matches Example:

  • Regex Matches .* would display the survey on all pages where the Pulse Insights code snippet is present

Suppress If:

While “Display Survey If” is a whitelist of URLs, View Names and/or Event Names, “Suppress If” is a blacklist. If a URL/View Name/Event Name matches the criteria established in this section, then the survey will NOT be eligible to render. The Suppress If fields work together with the Display If fields to determine which URLs the survey will fire on. 

The same options are available for suppressing as defined in the previous Display If section.

Example:

  • Display If URL Contains pulseinsights.com and Suppress If URL Contains thank-you would display the survey on all pages of PulseInsights.com except those that contain thank-you in the URL.

Click on “Add Another” to add another URL/View Name/Event Name to the suppression list. 

Previous Response:

You can ask follow-up questions to users who have given a specific answer to a survey in the past. This is a great way to dig deeper into the mindsets of your users and gather targeted feedback over time.

Simply choose from the dropdown list of other surveys and select the previous answer you’d like to target your new survey to. 


User Behavior: 

You can target users based on their session depth (number of pageviews in the current session), and whether they are a first time or repeat visitor. Surveys are targeted to “All visitors” by default. 


Page Behavior:

There are several page behaviors that you can target to trigger a survey to show, such as: 

  • Time on Page: trigger survey to show after n seconds
  • Scroll: show survey after user scrolls n% of the page length
  • Exit Behavior: trigger survey when user shows likely exit behavior (e.g. moving the mouse to exit the page)
  • Click: show survey after user clicks on a particular element on the page (this is configured using CSS selectors)
  • Content in View: show the survey after a particular element (CSS selector) scrolls into the viewport
  • Text on Page: show the survey when a particular element contains (or does not contain) particular text.


Custom Data Attributes:

Custom data attribute targeting enables targeting surveys based values previously passed to Pulse Insights so you can ask questions only to a hyper-targeted segment of users. 

For example, if you pass loyalty points balance, you can target a question to users who have over, say, 50,000 points.

Numerous options are available:

  • ‘Equals’ is an exact match. E.g., ‘customerType equals member’ only matches users with that exact value, ‘member’, defined for ‘customerType’ attribute.
  • ‘Does Not Equal’ matches users that do not match the value. E.g., the targeting ‘customerType does not equal member’ will match users with the values defined that do not exactly match ‘member’, such as ‘trial user’ or ‘nonmember’
  • ‘Contains’ is a partial match. e.g., ‘locale contains en’ matches users with locale of ‘us-en’ and ‘uk-en’.
  • ‘Does Not Contain’ will match any user whose defined value does not include the targeted value. E.g., ‘customerType does not contain member’ will match users with the values defined that does not contain ‘member’, such as ‘trial user’, but would not match ‘non_member’, since that value contains ‘member’. 
  • ‘Exists’ means that some value is defined. E.g., ‘loyaltyStatus exists’ would match users that have any value defined – say silver, gold, or platinum.
  • ‘Does Not Exist’ means that the value is not defined. E.g., ‘loyaltyStatus does not exist’ would match users that do not have any value defined for that attribute. 
  • ‘Is Greater/Less Than’ evaluates the value defined and will match users with a value bigger/smaller than the targeted value. E.g., if ‘pointsBalance is greater than than 50000’ is the target, then a user with a pointsBalance of 50001 will be eligible to see the survey, but a user with a points value of 50000 will not be shown the survey. If the value is stored as a string, Pulse Insights will still attempt to evaluate it as a number.
  • ‘Is Greater/Less Than or Equal to’ evaluates the value defined and will match users with a value bigger/smaller OR matching exactly than the targeted value. E.g., if ‘pointsBalance is greater than than 50000’ is the target, then a user with pointsBalance of 50000, or a user with a pointsValue of 50001 will both be eligible to see the survey. 

You can add multiple user attribute targeting rules by clicking on the “Add Another” button. To remove a rule, click on the X to the right of the row. 

  • All of: If you have multiple rules and you’d like your target audience to match each rule, then use the All of, which builds a block of condition statements joined by AND. E.g. a user must have a pointsBalance equal to 50000 AND have a defined customer Segment (customerSegment exists). The user must match every set of conditions you add to “All of” in order to be eligible for the survey.
  • Any one of: If you have multiple rules and you’d like your target audience to match any one of the conditions, then use the “Any one of”, which builds a block of condition statements joined by OR. E.g. a user must have a loyaltyStatus of gold OR have a pointsValue less than 1000000 OR an undefined customerSegment (customerSegment does not exist). The user must match at least one, but not ALL of the set of conditions you add to “Any one of” in order to be eligible for the survey.

Client Key Required: A Client Key is your anonymous userID that you pass to Pulse Insights to uniquely identify the user, E.g. customer ID, order ID, custom ID. Enable “Client Key Required” if you’d only like to show the survey if the user has a defined client key.


Geo Targeting: 

You can target surveys based on inferred geography from the user’s IP address. Geotargeting is available at the country, US state, and DMA level.

You can add additional geotargeting rules by clicking on the “Add Another” button. You can remove a rule by clicking on the X.


Advanced:

  • Sample Rate: Determines what percentage of impressions that match the eligibility conditions receive the survey; Enter a number between 1 and 100%.
  • Behavior on Close: This option will prevent this particular survey from rendering again if a user actively closes it. This affects only the individual user that closed the survey. Other surveys will continue to render based on their targeting criteria.
  • Ignore Frequency Cap: Account-level frequency caps are set in Global targeting (see Setup section). A particular survey can ignore the established frequency cap by enabling the “Ignore Frequency Cap” setting. 
  • Multiple Submissions: This setting enables the survey to re-fire every n minutes/hours/days (choose from dropdown) after a user submits the survey (answers a question).


Mobile App Targeting:

When you enable iOS or Android native app targeting, then you can create targeting conditions for mobile behavior, such as requiring that the user has launched the app at least n times, and/or that at least n days have elapsed since the user installed the app.

Be sure to click “Save” to save your targeting configurations!

Live Preview Mode

You can access Live Preview in our Console by clicking the “Live Preview” button in the top-right of the Edit Survey pages.

Upon clicking Live Preview, you’ll be asked for the URL you’d like to view. 

You can also turn Live Preview mode on by appending ?pi_live_preview=true to any URL that contains the Pulse Insights code snippet.

You can turn off Live Preview Mode by appending ?pi_live_preview=false to the URL.

While in Live Preview mode, the survey displays surveys with a status of “Draft” for your browser, but other live users on your site will not be able to see the survey while in Draft mode. 

In Live Preview Mode, answers are not stored in your reporting, so you don’t need to manually remove any test responses. Non-production data is not sent to your other systems because custom data callback code does not execute in Live Preview mode. 

To view a survey in Live preview mode, two requirements must be met:

  1. The Pulse Insights code snippet must be present on the page.
  2. The survey in question must be configured to display on that page. The survey’s URL targeting must include the page that is being tested.

Your browser will remain in live preview mode until the browser is closed. We recommend previewing in an incognito window.

Change Survey Status

To set a survey live, go to the “General” Tab of the survey and click the Status dropdown menu. Select “Live”, then save your changes. The survey will now be eligible for impressions.

Using the status dropdown menu, you can also change to the following statuses:

  • Draft: the survey is not currently firing; used before a survey launches. The survey must be in Draft status for Live Preview mode
  • Live: the survey is firing and eligible for end users
  • Paused: the survey is temporarily not firing for end users, but is expected to be turned back live in the future
  • Complete: survey has reached either its submissions goal or the scheduled end date
  • Archived: survey is complete and not actively being looked at 

You can also toggle the status within the main Dashboard page. Simply hover over the status to change from:

  • Draft mode → Live 
  • Paused → Live
  • Complete → Live
  • Live → Paused
  • A survey with an Expired status (past the scheduled end date) will show a link to “Change Date”. Clicking “Change Date” will bring you to the survey’s Targeting Conditions page where you can extend the scheduled end date to a future date. 


Create Survey Group

Survey Groups allow you to create multiple similar surveys and organize them together. For example, if you want to create the same survey (with similar questions and branching) in other markets in a localized language, or if you’d like to run an A/B test and easily keep track and compare results, you can group all of the survey “variants” in a Survey Group. You can see results of each survey instance individually, and also see the aggregated results for the survey group.  

To create a Survey Group, you first need to create a base survey. Create a survey as you normally would (see instructions above). After creating a survey, you can create a survey group from the main dashboard page. The survey you originally created will be your “base” survey and will serve as the template for the other surveys you create in the group.

When you click “Create Group”, you will be prompted to name your survey group. 

Once you click “Create”, then your new group will be created and you will be brought to the Bulk Editor where you can create additional variants of the base survey. 

Bulk Editor

For an existing survey group, you can access the Bulk Editor via the Survey dashboard by hovering over the group name to reveal the options (Results | Bulk Editor) and clicking on Bulk Editor. 

The Bulk Editor presents the survey attributes in a spreadsheet-like format, so that it is easier to make consistent changes across all surveys in the survey group. 

This view lists survey information, such as:

  • General (survey name, status, goal)
  • Widget type
  • Targeting conditions
  • Question type
  • Question and answer copy
  • Thank you message copy 


The first column consists of the row headlines (with short names/labels that are editable by double clicking on the value) and the base survey (the original survey you created and created a survey group from). The base survey column and the top row of survey names will be locked in view as you scroll (up/down/left/right) and edit, so that you can easily reference the base survey and survey names while you are making edits. 

To create a new survey variant: click on the “+” button next to the base survey name. An exact copy of the survey will be created and its attributes will be listed in the next column of the spreadsheet-view. 

To edit copy: double click on the text input field, type the new copy, then hit the Enter key.

To edit options (such as status, widget type, theme, etc): click on the dropdown menu and select another option.

Translations: Enter the language code (see here for ISO Language Codes) in the appropriate text field in the “General” section. When you enter your translated copy, hover over the globe icon to reveal a tooltip with the approximate English translation. This tool comes in handy when you are creating survey variants in different languages.


To add questions: Scroll down to the bottom of the page and click on the “Add Question” button on the bottom left. This will trigger the “Add Question” modal where you can pick the question type and define the question copy and short name label. You can also configure additional options, which vary depending on the question type.


To branch/ask a followup question: Double click on the short name question or answer in the first column. A modal will pop up where you can choose a followup question from the dropdown menu. In this modal, you can also change the base value and the short name. Then hit “Update”

To add an answer: Click on the “+add answer” button in the first column. This will add an answer for all survey variants. 

To delete a question: Double click on the question in the first column to trigger the “Edit Question” modal. Click “Destroy” to delete the question for all surveys.

To edit a question: You can also edit the base question copy and short name in the “Edit Question” modal, which you can open by double clicking the question in the first column. To ask a follow up question, select a question from the dropdown menu. Note, you will have to create the followup question before it will be included in the dropdown menu.

To delete an answer: Double click on the short name answer in the first column to pull up the “Edit Possible Answer” modal. Click on the “Destroy” button to delete the answer for the base survey for all the survey variants. 


Viewing Survey Results

You can view survey results in a variety of ways:

In the Console

To view the results of a survey in the Console, hover over the survey name in the dashboard view, then click “Results”. The Results page shows aggregate survey metrics at the top of the page and results broken down by question. The Results page shows metrics from the last 30 days by default, but you can also click to view all results, the last 7 days, results from yesterday, from today, or choose a custom date range. 

Aggregate survey metrics includes:

  • Survey Impressions: how many times the survey was returned to be displayed on a page
  • Viewed Impressions (if enabled): viewed impressions differ from regular impressions - this metric is how many times a survey was returned and seen by a user. For surveys with display triggers (such as Page Behavior targeting - display after n seconds on page, after user scrolls n% of page, after user clicks on a certain element, etc.), sometimes a survey is returned and eligible to show (an impression), but the user does not complete the action required to trigger the survey. The viewed impressions metric takes into consideration whether or not the user has completed the action necessary (e.g. scroll, click, exit behavior, etc.) to actually see the survey. 
  • Submissions: how many times at least one question from the survey was answered
  • Submission Rate: is impressions / submissions. When viewed impressions are enabled, then viewed impressions are used in the submission rate calculation. Otherwise, regular impressions are used in the calculation.
  • Days Active: the number of calendar days the survey has been live and collecting data. Changing the status resets this calculation. 

On each of these summary stats, you can see sparklines that show the trend of these metrics over time.

Below the aggregate metrics, you can view results by question into total responses and share (%). You can click the number of responses in the top right to sort answers by descending order instead of the order defined in the console.

You can filter reporting by what people have answered to a specific question by clicking the any bar. All other questions will then update to reflect results for those who gave that answer. 

The data for free text responses is displayed as a word cloud so that you can quickly digest large numbers of responses and grasp frequency of usage. Similar words are automatically combined to give more relevant responses. You can see verbatim responses by clicking any word in the word cloud. For a more in depth analysis, click on the “Text Responses” link in the bottom left. Clicking this link displays individual responses in a table format where you can see the date & time, completion URL, device type, response, translation (when applicable and language code is established upon survey creation), tags and sentiment score.

The data table is sortable in real-time by clicking a column header.

You can also filter results in real-time by typing in the filter field at the top of each column.

To filter responses simply type in the filter field at the top of the column you would like to filter.

The data table also enables you to group responses so you can view the data in ways that highlight similarities, differences, and insights. For example, you can group the responses based on

  • How the user answered some other question.
  • The URL the user answered the survey on (only for browser-based responses; native mobile and API responses won’t have a submission URL)
  • The device type (phone, tablet, and desktop)



You can also tag free text responses. When you have thousands of free text responses, it’s not easy to distill it into digestible learnings. And even if you could do that, it’s not easy to retain perspective about how common certain themes are. This is where our response tagging comes in.

To apply one or more tags to a response:

  1. Filter by relevant keyword by typing in the filter field at the top of “Tags” column
  2. Using the checkbox in the leftmost column, select all responses as a starting point; but unchecking any responses that don’t fit 
  3. Apply the tag by choosing an option in the “Select tag to add” dropdown menu. To create a new tag, click “Manage Tags” in the dropdown menu. Then click “New Tag” and you can name your new tag and apply a tag color.  
  4. You can remove a tag by clicking the “X” on the tag



We’ve found that even large datasets with thousands of responses can be fully tagged quickly. 
The general results page will show a chart that graphs the frequency of occurrence of each tag in descending order, thus helping you digest what people think even though they submitted nuanced and complex open-ended responses. You can also change to view the Word Cloud and Text Responses table views by clicking on the corresponding links in the bottom left.

Export Results

On the main Results page, click on the “Export” link to generate an XLSX file, then click “Download” to download the file, which includes the following report sheets:

Survey Metadata: Survey name, author, reporting date range, date of report generation 

Aggregate results by day: the following metrics aggregated by day:

- Impressions

- Viewed Impressions (if enabled)

- Submissions

- Submission Rate

Questions tab - Response Summary Report: number of submissions per question and per response. This breakdown also shows the percentage (or share) that a particular response has in comparison to total responses

There are two variations of raw data: 

- Devices tab - one row per device 

- Individual Rows - one row per response (Individual Rows tab)

  • Date/Time stamp
  • IP address
  • Survey ID
  • Question & Response
  • Questions & Response IDs
  • Device ID (UDID)
  • Previous Surveys Answered
  • Browser
  • Operating System
  • Device Type (mobile, desktop, or tablet)
  • Visit count — the number of visits observed
  • Pageview count — the number of pageviews in current session at the time of submission
  • Context Data (aka Custom Data) — data describing the current context: e.g., data about the current page or activity
  • Device Custom Data — data describing the device and user
  • Client Key — your anonymous userID that you pass to Pulse Insights to uniquely identify the user

Scheduled Reporting Sent to Email

You can also send survey results right to your email inbox. Simply click on the account name and choose “Scheduled Reports” from the dropdown menu. Click on the “New Report” button. 

Give your report a name, select which surveys you would like to include, select your desired frequency from the dropdown (Daily, Weekly, Biweekly or Monthly), select the start & end dates (optional), and the recipient(s). You can add email addresses that are not associated with the account (and thus not listed by default) by clicking on “New Email” and typing the email address in the text field. Click “Save”. 

Please note: only live surveys with submissions during the period will be sent.

Integrating Survey Responses With Other Services

Pulse Insights was built to easily integrate into other services. For example:

  • You might want to push survey responses into Google Analytics or Adobe Analytics so you can add the missing context to traditional web analytics data
  • If the survey is targeted to your customers, you might want to push results into your CRM system
  • You may want to place the current user into a DMP segment or A/B Test segment based on what they answer
  • Similarly, you might want to push preferences into your Personalization profile

Under Setup, you’ll find the Data & Integrations page with the following callback code snippets: 

  • On impression callback - executed when the survey has an impression
  • Viewed impression callback (if feature is enabled for your account) - executed as soon as the survey is viewed by the user
  • Onanswer callback - executed after each answer submission (after submitting but right before the /answer HTTP call).
  • Onclose callback - executed when the survey is closed before all of its questions have been answered
  • Oncomplete callback - executed after the survey submission

Because CRM setups tend to vary from client to client, CRM integrations are configured and managed by Pulse Insights Tech Ops. Get in touch with your account team if you need to add or make changes to your CRM integration.

Pulse Insights supports the following integration methods:

  • Real-time API call upon question submissions
  • Hourly/daily feed placed on client’s or Pulse Insights’ sftp server
  • JavaScript callouts on question submissions

Additional Capabilities

Display specific survey

Custom Data capture

Progressive Profiling

Dynamic email

Automations

Account Options: Don't allow personal data

Polls and surveys in email

People vs. device-based  surveys

Link Devices

Client Key decisions