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
  • Time Delay
  • Scroll Delay
  • Exit Intent
  • Upon Element Click
  • Content in View
  • Text in View

Was this helpful?

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

On Page Behavior

PreviousPrevious ResponsesNextCRM Targeting

Last updated 5 months ago

Was this helpful?

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

It is recommended that you only use one on page behavior trigger.

If you’ve chosen an inline widget-type, you do not need to use On Page Behavior targeting because your survey will show on a specific part of the page.

Nerd Alert: On-page targeting works differently than other targeting categories under the hood. The impression is served before the on-page condition is met. If and when the on-page behavior is met (e.g., 50% scroll), it is rendered in the browser. If it is viewed by the user, it is also marked as a Viewed Impression.

Consider this distinction when setting account-level impression frequency cap values, which are evaluated based on Served Impressions. Users can potentially meet the impression cap from impressions that aren't Viewed.

For more information on impression frequency capping, see Global Targeting documentation .

Time Delay

You can set a timed delay before your survey shows.

To set a time delay, check the checkbox for "Delay: Show after [ ] seconds" and enter a number (in seconds) in the input field.

We recommend 5 seconds or less. On average visitors, spend about 5 seconds on a webpage, so we recommend keeping the time low.

Consider how your widget interacts with the user’s experience. For example, if you’ve chosen an inline format, you probably do not need to delay showing the survey. If you’ve chosen an overlay, you may want to give the visitor a few seconds to absorb your page’s content before triggering your survey.

Scroll Delay

You can set a delay based on how far down the webpage a user scrolls.

Simply check the checkbox for "Scroll: show after user scrolls percent of page length" and enter a number percentage.

We recommend using between 10 - 20% scroll to trigger your survey, unless you are hoping to trigger near a specific piece of content (in which case, you may want to consider triggers instead). For example, perhaps you want to make sure someone read a piece of content that is about 20% down the page. Then we recommend setting scroll percentage at roughly 30%. You might consider how your widget interacts with the user’s experience. Inline widget types shouldn't have a scroll delay trigger since it will appear on a specific part of the page.

Exit Intent

Use Exit Intent targeting to rigger survey when user shows likely exit behavior (e.g. moving the mouse to exit the page).

Check the box for "Exit intent: show upon likely exit behavior"

This targeting is only available for desktop only.

Upon Element Click

Use this to show your 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 in View

show the survey when a particular element contains (or does not contain) particular text.

Content In View
here