Overview
Filters help you narrow the visitor table. Saved views help your team reopen the same slice of data. Segments let you reuse those rules in automations like webhooks and integrations.
Common filter areas
Leadpipe groups filters around the decisions your team needs to make:Professional & CompanyLocationAcquisitionIntent & Engagement
Include or Exclude matching traffic. That makes the panel useful both for finding good-fit visitors and removing noise.
Recommended workflow
Start with one question
Build the view around a concrete question, such as who viewed pricing recently or which visitors came from a specific channel.
Apply only the filters you need
Keep the first version narrow and understandable. It is easier to refine a focused view than untangle an overloaded one.
Save the view
Save useful filters as a view so you and your team can return to the same working set quickly.
Working with saved views and segments
Once you save a view or segment, you can switch between them from the saved filter area without rebuilding the logic each time. That makes it easier to:- review the same audience every day
- compare different audience slices quickly
- reuse one saved segment across webhooks, notifications, or integrations
Views vs. segments
| Tool | Best for |
|---|---|
| Saved view | Reopening a useful table configuration inside Leadpipe |
| Segment | Reusing a rule set across automations and destinations |
- a saved view is for humans working inside Leadpipe
- a segment is for workflows that need the same rules again later
Good first segments
- Recent pricing page visitors
- High-intent visitors from paid or social sources
- Visitors from target industries or company sizes
- Visitors from one specific pixel or domain