Pulse Insights Documentation
  • Pulse Insights Overview
    • 👋Welcome to Pulse Insights
  • Implementing Pulse Insights (Dev)
    • Implementing on Web and Mobile Web
      • Deploying your tag (code snippet)
      • Ingesting contextual data for targeting and analysis
      • Client Key
      • Tracking Events (aka High Value Actions)
      • Presenting a specific survey
      • Supporting Inline surveys
      • Callbacks
      • Privacy Features
        • Identifiers, cookies, and local storage
        • Data that Pulse Insights stores
      • QA Process and Preview Mode
        • JavaScript Object
      • Single Page Apps
      • Load Time & Availability
      • Bot blocking
      • Customer-initiated Feedback
    • Implementing in email
      • Dynamic Email
    • Implementing in Native Apps
      • Android
        • Android Release Notes
        • Android Demo App
      • iOS
        • iOS Release Notes
        • iOS Demo App
      • Demo App Help
  • Integrations
    • Integrations overview
      • Hubspot
      • Braze
      • Google Analytics
      • Data Lake
  • Configuring Pulse Insights (Console)
    • Account Setup
      • Authentication & SSO
      • Inviting Collaborators
      • Roles & permissions
    • Dashboard & Program Management
      • Survey Status
    • Editor
      • Question Types
        • Survey Invitation
        • Single Choice
          • Using Images
        • Multiple Choice
        • Free Text
        • Net Promoter Score
        • Slider
        • Custom Content (Next Best Action)
        • Thank You Message
          • Poll (Show Results)
      • General
      • Targeting
        • Devices & Channels
        • Sample Rate
        • URL & Events
        • Dates
        • Previous Responses
        • On Page Behavior
        • CRM Targeting
        • Geo Targeting
        • Goal
        • User Behavior
        • Advanced Settings
      • Formatting
        • Widget Types
          • Docked
          • Bottom Bar
          • Top Bar
          • Overlay
          • Inline
        • Themes
        • Question Display
        • Custom CSS (Survey-level)
        • Supported Markdown
      • Link Builder
      • Preview
      • Survey Groups (Localization)
    • Reporting
      • Results Page & Filtering
      • On Demand
        • Columns/Data Dictionary
      • Scheduled Reports
      • Free Text
        • AI Generated Summary
        • Responses & Tagging
      • Custom Content Reporting
      • Viewable Impressions
    • Account Level Settings
      • Get Code Snippet
      • Global Targeting
      • Data & Integrations (Callbacks)
      • Data Restrictions
      • Themes
      • Automations
        • High Value Actions (Events)
      • Activity Log
      • Configured by Pulse Insights
  • Best Practices
    • Best Practices
      • Copy
      • Design and Execution
      • Targeting
      • Widget Types
      • Sample Rate
      • Submission Rates
      • Special Features
      • Best Practices for Progressive Profiling
  • API
    • API reference
      • Surveys
        • Questions
        • Poll
      • Q
        • A
      • Direct serve
      • Serve
      • Results
      • Present results
      • Track event
      • Custom content link click
      • Submissions
        • All answers
        • Answer
        • Close
        • Viewed at
      • Devices
        • Set data
Powered by GitBook
On this page
  • Display If:
  • Suppress If:
  • When to target “Run of Site” vs targeting a specific page or pages.

Was this helpful?

  1. Configuring Pulse Insights (Console)
  2. Editor
  3. Targeting

URL & Events

PreviousSample RateNextDates

Last updated 1 year ago

Was this helpful?

In the URL & Events section, you can set up targeting rules to determine where on your site or app the survey should display, and where it should not display.

Display 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 New” to add another URL/View Name/Event Name to the whitelist.

Click the trash icon remove the targeting.

Display If rules are "OR" statements (not AND). If you have multiple display if rules, the survey is eligible to show on URLs that match any one of the set display if rules.

URL Contains Examples:

The survey with the targeting shown in Example 1 would display the survey on pulseinsights.com/pricing and pulseinsights.com/pricing/request.

The survey with the targeting shown in Example 2 would display the survey on all pages of pulseinsights.com.

The survey with the targeting shown in Example 3 would display on all pages of the console subdomain, but not on pulseinsights.com.

A survey with URL Contains: utm_source=sem (as shown in Example 4)would display the survey for campaigns tagged with "sem".

Regex Matches Example:

  • Regex Matches .* (as shown in the Regex Example above) would display the survey on all pages where the Pulse Insights code snippet is present.

Display If rules work in conjunction with the Pulse Insights tag. If the tag is not on a page, the survey will NOT be eligible to show, even if the Display If targeting rules are met.

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.

For example, if Display If URL Contains: pulseinsights.com AND Suppress If URL Contains: thank-you the survey would display on all pages of pulseinsights.com EXCEPT those that contain thank-you in the URL.

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

Click on the trash can icon to delete a Suppress If rule.

Similar to Display If rules, multiple rules within the Suppress If are OR rules. If the URL /Event Name/View Name matches any one of (not all of) the Suppress If rules, then the survey will NOT show.

When to target “Run of Site” vs targeting a specific page or pages.

Run of Site

  • You want to get a representative read of the site as a whole.

  • You want to compare results across all pages.

  • If it is important for many visitors to see the survey. ‍

  • To use an inline survey here, your tech team will need to create a container/div.

A Group of Pages

  • You’d like a representative read across a subset of pages

  • You want to compare results across all pages.

  • ‍To use an inline survey here, your tech team will need to create a container/div.

1 Specific Page

  • You want to understand the UX of a specific page

  • You want to know more about the content on one specific page or part of a page.

  • You want to know about one piece of content or design & would like to put a survey right next to that piece of content. ‍

  • Inline surveys must be targeted at one page at a time, and are best for asking about objects or content they are placed near.

Example 1
Example 2
Example 3
Example 4
Regex Example
Suppress If Example