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

Was this helpful?

  1. Configuring Pulse Insights (Console)
  2. Editor
  3. Formatting
  4. Widget Types

Inline

PreviousOverlayNextThemes

Last updated 1 year ago

Was this helpful?

The Inline widget type displays as an interactive object on your web page or app that disappears once the user answers or exits.

Available for Web or App implementations.

Inline surveys are great for asking about specific pieces of content on your page or if you hope not to disrupt the user’s experience. Users sometimes react negatively to popups, so if you have the volume, use inline surveys. For example, if you have 100,000 visitors a day and only need 500 submissions a day, use an inline or docked widget to keep the user experience seamless. Inline surveys work best when deployed on specific pages unless the site has a dedicated slot for Pulse surveys.

If you plan to show a survey in “inline” mode (within the content of the page, versus as an overlay on top of the page), then there are two available methods:

  1. Use Existing CSS Selectors -

  • Target - An html element, specified using CSS selectors

  • Location - Determines how the survey is positioned in relation to the target

  • Order within Target (if location is inside) - Positions the survey as the first or last element within the target

    • There is some overlap in the use cases for these different modes, but generally inserting inside a target is best used when you wish the survey to be contained visually / semantically inside a particular page element, whereas inserting as a sibling would be more useful if you need to place the survey at a particular index within a list of elements.

  1. Blank Divs - In certain cases (explained below), it's best to dedicate an html element to the survey. This may require working with the web team. Use a blank div if:

  • the survey is targeted to show across multiple pages and not all pages contain the same CSS selector

  • the structure of the page changes (e.g. different page content for customers vs. prospects)

Please see our for more details on supporting inline surveys.

technical documentation
Order within the target (if location is set to "Inside")