SleekView for Elementor Popups: triggers, conditions & conversions as tables
Read Elementor Popup templates, their triggers, display conditions, and conversion counters from Elementor's tables and meta. Sort by impressions, filter by trigger type, and toggle a popup live without opening the Elementor editor.
♾️ Lifetime License available
Stop opening each popup template just to read its triggers
Elementor Popups are stored as elementor_library posts with a _elementor_template_type meta of popup. Their triggers, display conditions, and advanced rules live in postmeta on each template, while impression and conversion counts are tracked separately. Elementor's own admin shows popups in a list with name, status, and a few buttons; the actual configuration is hidden inside the editor. SleekView reads the underlying meta directly so the trigger, conditions, and stats sit on the table — no need to open the editor to know how a popup is set up.
The conversion picture is even more useful. Elementor tracks how many times a popup was shown, how many converted (form submissions, button clicks where the user marked them as conversions), and updates those counters per popup. SleekView surfaces them as columns, sortable so the lowest-converting popup of the month is one click away from a content review.
Inline edits write through Elementor's own meta API, so toggling published/draft, changing a trigger type, or activating a condition writes back the same way the editor would. The popup behaviour on the front-end reflects the change without a manual flush, and any caching plugin sees the post update like any other published change.
Workflow
How SleekView reads your Elementor Popups
Pick the source
elementor_library with template-type meta popup, joined to postmeta for triggers, conditions, and counters. SleekView lists the relevant meta keys actually present on your install.
Compose your column set
Save and scope the view
Act inline through Elementor's API
Sample columns
A typical Elementor Popups view
posts filtered by post type and template-type meta, then joins triggers, conditions, and counters from postmeta.
wp_posts (elementor_library) + wp_postmeta (_elementor_*)
| Popup | Trigger | Condition | Status | Impressions | Conversions |
|---|---|---|---|---|---|
| Spring sale 15% off | Time on page 30s | Shop pages | Active | 12,418 | 486 |
| Newsletter — exit intent | Exit intent | Blog | Active | 8,902 | 312 |
| Pricing FAQ assist | Scroll 50% | Single: pricing | Active | 3,140 | 84 |
| Holiday banner v2 | Page load | Site-wide (logged out) | Draft | 0 | 0 |
| Studio booking nudge | Click selector | Single: services | Active | 612 | 41 |
Comparison
Default Elementor Popups screen vs SleekView
Default Elementor admin
- Triggers and conditions live inside the editor, not on the list
- No sortable column for impressions or conversions
- No filter by trigger type or condition target
- Bulk status changes are limited; no row-level toggle
- No saved per-role views (e.g. content vs ops perspectives)
SleekView
- Trigger, condition, and conversion data on the list — no editor needed
- Inline-toggle active/draft status per popup
- Custom columns for trigger type, condition, impressions, conversions
- Save filtered views like "Active popups under 1% CTR" or "Exit-intent only"
- Switch between table and kanban views grouped by trigger
Features
What SleekView gives you for Elementor Popups
Popup state visible at the row level
Trigger, condition, status, impressions, conversions — all sourced from elementor_library posts and their meta. Build separate views for content review, conversion tuning, and a release queue without re-opening templates.
Toggle live without the editor
Flip a popup from active to draft inline when content is wrong or stale. Writes go through Elementor's meta and post-status APIs so the change is reflected on the front-end and in any related caches.
Filter by what content teams actually ask
Combine trigger type, condition target, status, and conversion-rate columns. Save "Active popups with under 1% conversion rate over 1k impressions" as a named view for the monthly review.
Audience
Who uses SleekView for Elementor Popups
Marketing review
Monthly view of active popups sorted by conversion rate. Spot the underperformer without opening templates one by one. Toggle a stale promo to draft inline before it loses more impressions.
Site editors
Filter by condition target — "single: pricing" or "shop" — to see exactly what fires on a page that's getting a content rewrite. Avoid surprising a campaign by editing a page that hosts a live popup.
Agency client deliveries
Capability-gated view for client roles — they see popup names, status, and conversion counts, but not the editor. Useful for monthly status meetings without granting Elementor design access.
The bigger picture
Why a popup table beats opening every template
Elementor's popup builder produces real conversion impact, but its admin treats each popup as an opaque template. The list shows name and status; everything else — trigger type, target conditions, impressions, conversion counts — is hidden inside the editor or scattered across post-meta keys. That works while you're designing one popup.
It does not work for a site running fifteen popups across product pages, blog content, and exit-intent capture, with monthly content reviews and quarterly performance audits. Answering "which popup is firing on the pricing page" or "what's the conversion rate of our exit-intent newsletter" means opening templates one by one or pulling impressions from a separate analytics report. SleekView surfaces the meta and counters as actual columns.
A marketing lead opens "Active popups sorted by conversion rate" and acts on the bottom rows. An editor filters by condition target before rewriting a page. A client role sees only conversion summaries, capability-gated.
Same Elementor data, dramatically less digging to know what's running and how it's doing.
Questions
Common questions about SleekView for Elementor Popups
No. The editor is still where you design popups, set triggers, and configure conditions. SleekView is a list-and-edit surface over the meta and counters Elementor stores. Configuration lives in the editor; ops, review, and reporting live in SleekView. Toggling status inline is the main inline-edit case — anything richer routes back to the editor.
Each popup template stores its triggers, display conditions, and advanced rules in postmeta on the template post (the keys begin with _elementor_ and are JSON-encoded). SleekView reads those keys, parses the relevant fields, and exposes them as table columns. Edits write through Elementor's update_post_meta path.
Yes. Elementor stores impression and conversion counts per popup. SleekView lets you compute conversion rate as a derived column (conversions / impressions) at query time, so the rate updates automatically. Sort and filter by it like any other column for content reviews.
Toggling status uses WordPress's standard post-update flow, so any caching plugin listening for post updates invalidates the relevant pages. Elementor's own CSS file regeneration runs as it would for any template change. There's no manual flush required for the popup behaviour to reflect the new status on the front-end.
Popups are a Pro feature, so this view is mainly relevant for Pro installs. SleekView reads the same template post type Pro creates. Free Elementor doesn't expose popups, so the view simply has no rows on a free-tier site — there's nothing to break either way.
Conditions are richer than single fields — type plus target plus operator — so SleekView shows them as a related-table edit per popup rather than inline-editable cells across rows. Toggle status, change trigger type, and edit basic flags inline; deeper structural changes belong in the editor where the field-level UI is rich.
Yes. SleekView views are gated by WordPress capability. A content-strategy role can see popup name, status, condition target, impressions, and conversions without holding the edit_pages capability that opens the Elementor editor. Useful for review meetings where you don't want to risk an accidental design change.
No. SleekView is a wp-admin tool — it doesn't run on the front-end and doesn't intercept popup display logic. Elementor's runtime continues unchanged. Admin-side queries hit indexed columns on posts and postmeta; large sites should scope the default view to active popups to avoid scanning archived templates.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout