SleekView for Divi Overlays: overlay CPT as tables
Divi Overlays stores popups and modals as a custom post type with trigger and display settings in postmeta. SleekView surfaces every overlay with its triggers as a queryable workspace.
♾️ Lifetime License available
Every Divi Overlay in one grid
Divi Overlays stores each overlay as a Divi-builder custom post type, with the layout JSON in wp_postmeta (Divi uses keys like _et_pb_use_builder and the underlying Divi shortcode in post_content). Trigger settings (entry, exit-intent, click, scroll percentage) and target conditions also live in postmeta. The default Divi Overlays admin lists overlays in one screen but doesn't expose their triggers or targets as filterable columns.
SleekView reads the overlay CPT plus the relevant postmeta keys, joining them into one table. Filter by trigger type to find every exit-intent overlay. Filter by target page to find overlays attached to a specific URL. Sort by last edited to surface stale overlays nobody refreshed for the latest campaign.
Inline edits to overlay status, title, and author run through standard wp_update_post calls. The Divi shortcode layout in post_content stays the Divi Builder's responsibility. CSV export of any filtered slice gives the team a clean inventory of every overlay on the site.
Workflow
From scattered overlays to one campaign inventory
Index the overlay CPT
Surface trigger and target
Save audit views
Inline edit and export
Sample columns
A typical Divi Overlays inventory
wp_posts (Divi Overlays CPT) + wp_postmeta (trigger and target settings, Divi builder metadata)
| Title | Status | Trigger | Target | Last edited | Author |
|---|---|---|---|---|---|
| Newsletter signup | Active | Exit intent | / | May 02 | Lena R. |
| Spring sale popup | Active | Scroll 50% | /shop | Apr 29 | Mira S. |
| Onboarding overlay | Draft | Time delay | /getting-started | Apr 30 | Den J. |
| Black Friday popup | Expired | Entry | /black-friday | Nov 24 | Lena R. |
Comparison
Default Divi Overlays admin vs SleekView
Default Divi Overlays admin
- Default overlay list shows title and status but not trigger or target
- No filter to find every exit-intent or scroll-triggered overlay
- Last edited and author columns are absent
- Bulk status changes mean opening each overlay
- Orphan overlays (no current campaign) are hard to surface
SleekView
- Trigger and target as filter chips on the overlay grid
- Saved views per trigger type (exit intent, scroll, click, time)
- Inline edit overlay status, title, and author
- Filter by last edited to find stale or seasonal overlays still active
- CSV export of any filtered slice for client or internal reports
Features
What SleekView gives you for Divi Overlays
Trigger-aware filters
Find every exit-intent overlay or every scroll-triggered overlay with a saved view. Trigger and target become first-class filter chips instead of hidden postmeta.
Seasonal cleanup
Filter by last edited to surface overlays tied to last year's Black Friday or last quarter's launch that are still live. Quarterly housekeeping pays for itself in conversion accuracy.
Inline edits
Toggle status, edit title or author from the row. The Divi Builder shortcode layout stays untouched; only the surrounding overlay metadata changes.
Audience
Who uses SleekView for Divi Overlays
Marketing teams
Coordinate which overlays are live for which campaign across the site. Trigger and target filters replace a separate spreadsheet of popup placements.
Agencies
Audit client sites for stale overlays before quarterly check-ins. Per-client saved views turn handover reports into a one-click export.
Site owners
Spot overlays that should have expired with last quarter's campaign. Bulk-archive them inline instead of opening each overlay separately.
The bigger picture
Why overlay inventories drift on Divi sites
Divi Overlays make popup and modal management much easier than hand-coded alternatives, which is why marketing teams adopt them eagerly. The same ease of creation produces a long tail of overlays nobody remembers. A Black Friday popup still triggering in March.
A scroll-percentage overlay tied to a page that got rewritten. An exit-intent popup pointing at a discount that ended last quarter. The default Divi Overlays list shows titles and statuses but doesn't expose the triggers or targets as filterable columns, so finding the offending overlay means opening each one.
A queryable inventory turns that audit into a saved view. Filter by trigger type to review every exit-intent overlay. Filter by target URL to find every overlay attached to the page about to be retired.
Sort by last edited to surface seasonal overlays that should have expired. Marketing teams use it for quarterly campaign reviews; agencies use it as a recurring deliverable in client retainers.
Questions
Common questions about SleekView for Divi Overlays
Each overlay is a Divi-builder custom post type. The layout lives in post_content as Divi shortcode plus _et_pb_use_builder metadata. Triggers and targets live in postmeta keys specific to Divi Overlays. SleekView reads all of it directly.
Yes. Trigger settings live in postmeta and become a filter chip. Save a view per trigger type (exit intent, scroll percentage, click, time delay) so the next audit takes one click.
 
No. The Divi shortcode layout stays the Divi Builder's responsibility. Inline edits in SleekView touch overlay metadata (status, title, author, trigger settings if exposed as columns) through wp_update_post and update_post_meta.
Yes. Target postmeta becomes a filter chip. Filter by URL or URL pattern to find every overlay attached to /pricing or to anything under /blog/, which is essential before changing a popular page's slug.
Yes. Every saved view exports to CSV with the columns on screen. Use the export as a client deliverable in agency handovers or as a marketing-team status report.
 No. SleekView reads overlay metadata and only edits surrounding fields. The Divi Builder opens and saves the layout exactly as before. Existing Divi or Divi Overlays hooks fire normally during inline edits.
 Yes. Filter to overlays whose target points to a URL that returns 404 or to a draft page. That's a common pre-redesign audit deliverable and prevents campaigns from triggering on dead pages.
 Yes. SleekView is read-mostly. Inline edits use the standard WordPress update path, so any Divi Overlays hooks fire normally. The grid never writes directly to the Divi shortcode content.
 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 checkoutBrowse more
- Woocommerce Purchase Orders
- Woocommerce Product Filter
- Woocommerce Packlink Pro
- Woocommerce Pdf Invoice Pro
- Woocommerce Min Max Quantities
- Woocommerce Advanced Shipment Tracking
- Woocommerce Gift Cards
- Woocommerce Product Feed Pro
- Woocommerce Attribute Swatches
- Woocommerce Stock Notifier
- Woocommerce Eu Vat Assistant
- Woocommerce Product Csv Import
- Woocommerce Product Table
- Woocommerce Grouped Products Pro
- Woocommerce Authorize Net Cim