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
  • Example Use Case
  • The two ways to track events
  • Using JavaScript
  • In Console, by watching for visits to certain URLs
  • Recommended Events or High Value Actions To Consider Collecting

Was this helpful?

  1. Implementing Pulse Insights (Dev)
  2. Implementing on Web and Mobile Web

Tracking Events (aka High Value Actions)

Tracking Events enables you to inform Pulse Insights that an important event occurred, typically related to a website goal or action, so that you can later correlate survey responses with it.

Tracking events is optional, but highly recommended because it unlocks the ability to quantify the impact of what is typically siloed qualitative data.

Example Use Case

By informing Pulse Insights that a purchase event occurred, you can correlate survey responses with a purchase event. This helps you understand how different survey responses affect the probability of a purchase. For example, you could learn the "cost" of missing information on your product pages in terms of lost sales.

The two ways to track events

Using JavaScript

On any page that has the Pulse Insights code snippet, you can push event data like so:

pi('track_event', 'Purchase', {plan: "Gold", value: 50.00});

The two key benefits of this method are that you can dynamically populate data (like the purchase plan and price in the example above) to aid in custom analysis, and that you needn't rely on an event being simply a visit to a URL.

In Console, by watching for visits to certain URLs

In Console, you can configure visits to a particular URL to create an Event. This method is described in the Console Configuration section.

Recommended Events or High Value Actions To Consider Collecting

Event

Conversion

Add to cart

Key feature enrollments

Lead submissions

Cancellation

Support ticket creation

Just a few events goes a long way. Think of the top 2-3 things that indicate success or a problem on your website and start there.

PreviousClient KeyNextPresenting a specific survey

Last updated 2 years ago

Was this helpful?