Zipy
  • Welcome to Zipy ai
  • Getting Started
    • Install Zipy
    • Installing with Google Tag Manager
    • Supported frameworks
    • Security Overview
    • Sensitive User Data
    • SOC2 Type II
  • Zipy For Mobile
    • React Native Setup
      • Install React Native
      • Input Masking
      • Session Replay
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Fetch and XHR Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
    • Flutter Setup
      • Install Flutter
      • Session Replay
      • Input Masking & Custom Masking
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Http Network Calls
      • Dio Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
      • Session Recording Control
      • Data Sanitization
  • iOS Setup
    • Install in an iOS app
    • Identify Users
    • Screen Tracking & Tagging
    • Custom Logging
    • Session URL Retrieval
    • Session Recording Control
    • Input Masking & Custom Masking
  • Chrome Extension
    • Zipy Plug and Play Support
  • Configure
    • Zipy Recording Control
    • Release Version
    • Identifying Users
    • Adding Custom Identifiers
    • Anonymize Users
    • Source Maps
    • Blocking PII data
    • Ignoring Errors/Noise
    • npm Update
    • Support Integration
    • Session Stitching (rootDomain)
  • Product Features
    • Custom Events
    • Session Replay
    • Errors
    • Analytics
    • Time Filters
    • Multiple Filters
    • Clicked Element Filters
    • Manage Teams
    • Stack Trace
    • Console Logs
    • Network Requests
    • Network Headers and Payload
    • Custom Logs
    • Live Users
    • Alerts
      • Slack Alerts
      • Email Alerts
      • Live Alerts
      • Custom Alerts
    • Auto Resolve Errors
    • Zipy Labels Plugin
    • iFrame Support
    • API Performance
    • Heatmaps
    • Page Performance
    • Seen/Unseen Sessions
    • Public Session URL
  • FAQs
    • Install Zipy
    • Session Replay Definition
    • Error Tracking
    • Error Classification
    • Environment Support
    • Impact on your App
    • Performance Impact
    • Mobile Support
    • Network Data Capture
    • API Performance Diagnostic Help
      • High DNS Time
      • High SSL Connection Time
      • High Connection Setup Time
      • Large API Response Size
      • High Response Time
      • Compression Not Enabled
      • Server side API Failures
      • Client side API Failures
      • Insecure Connections
  • Troubleshooting
    • Errors in npm
    • Network header missing in Zipy
    • Can't see user data in sessions
    • No recordings or errors visible
    • No network timing split available
  • Product Videos
    • Ask AI
    • Getting Started
    • Session Replay
    • Multiple Project Creation
    • Team Management
    • Alerting on Slack
    • Time Filters and Daily Alerts
    • Custom Identifiers
    • Ignore Errors
    • Identify Users
    • Dashboard
    • Resolve Errors
    • New Error Digest
    • Jira and Slack
    • Online/Offline Network Status
    • Zipy on Zipy
      • Zipy Product Roadmap
  • Whats new
    • Product Updates
  • Legal & Policy
    • Terms of Service
    • Privacy Policy
    • Fulfillment Policy
    • Cookie Policy
    • Acceptable Usage Policy
    • Zipy Sub Processor List
  • Integration
    • Azure DevOps
    • Factors
    • RB2B
    • Webflow
    • WordPress
    • Amplitude
    • Coralogix
    • DevRev
    • Drift
    • Errorception
    • Freshchat
    • Google Analytics
    • Heap
    • HelpScout
    • Honeybadger
    • Hubspot
    • Intercom
    • Mixpanel
    • New Relic
    • Pendo
    • Raygun
    • Rollbar
    • Segment
    • Sentry
    • Shopify
    • Sumo Logic
    • TrackJS
    • Zendesk
Powered by GitBook
On this page
  • Clicked Element Text Filter
  • CSS Selector Filter
  • Best Practices
  1. Product Features

Clicked Element Filters

PreviousMultiple FiltersNextManage Teams

Last updated 5 months ago

Clicked Element Filters allow you to analyze user behavior by filtering session data based on specific elements on your website or application.

By applying this filter, you can:

  • Understand user intent: Gain insights into why users click or do not click certain elements and understand their navigation patterns.

  • Troubleshoot issues: Identify broken or unresponsive elements that users frequently attempt to interact with.

  • Perform A/B testing: Compare the number of users that clicked on a button vs another to understand what works better with your users and make design decisions accordingly

You can use the text of a clicked element or its ID or CSS selector to filter the data.

Clicked Element Text Filter

How to Use the Clicked Element Filter

  1. Select "Clicked Element Text" from the filters

  1. Select the operator as per your requirement

  1. Specify the element/ select the element from Dropdown

Input the unique identifier of the element (e.g., button text, link text...).

  1. Additionally, you can add a URL filter (Optional)

If not specified all pages where the particular element was clicked, are considered.

Use Cases for Clicked Element Filter

  • Monitor clicks on specific call-to-action buttons.

  • Analyze interactions with navigation menus.

  • Track clicks on promotional banners or key features.


CSS Selector Filter

CSS Selector Filter provides an alternate way to filter click interactions based on CSS selectors or click element IDs. This is particularly useful when targeting elements dynamically or when identifiers are not unique.

How to Use the CSS Selector

  1. Select "Clicked Element Text" from the filters

  1. Select the operator as per your requirement

  1. Select the CSS selector from the dropdown. Preferably do a "contains" on the element ID because the CSS selector that Zipy captures in real time might vary from what appears on your live site.

  1. Additionally, you can add a URL filter (Optional)

If not specified allwhere the CSS Selector element was clicked, are considered. pages

Use Cases for CSS Selector Filtering

  • Debugging issues with dynamic elements.

  • Analyzing interactions on elements styled with specific classes or IDs.

Best Practices

  • Use Specific Selectors: Narrow down your focus by providing unique identifiers or detailed selector patterns to avoid noise in your data.

  • Combine Filters: Pair Clicked Element or CSS Selector filters with other session filters like user details, location, or device for deeper insights.