SleekView for Drift
SleekView reads the Drift plugin's wp_options, per-page postmeta, the form plugin's submissions table and any local webhook log table. Embed status, captured leads and webhook events line up as columns you can sort and filter.
♾️ Lifetime License available
Drift settings list rows. Drift reporting lives elsewhere.
The Drift plugin admin screen is a settings page. It tells you the app ID, the include rules and the exclusion list, but it never shows you the URLs those rules resolve to, and it never sits next to the form submissions or webhook event rows the integration produces. To see all three together today, you open three different screens.
SleekView reads the WordPress-side data as a single dataset. The Drift plugin settings come from wp_options. Per-page overrides come from postmeta. Lead-capture submissions live in the form plugin's submissions table (Gravity Forms, WPForms, Fluent Forms, Contact Form 7 with a DB extension). Webhook event records, when the site logs them, sit in a custom table. SleekView joins them into one row per page, one row per submission or one row per webhook event, depending on the view.
The Drift dashboard still owns conversation analytics, playbook performance and pipeline data. SleekView covers the WordPress half: where the widget actually loads, which forms feed the SDR queue and whether the webhook endpoint is still receiving events.
Workflow
Turn the Drift plugin's footprint into a table
Pick the source rows
Compose your column set
Save and scope the view
Edit inline and export
Sample columns
A typical Drift capture and webhook view
wp_options (drift_*) + form plugin submissions + webhook log table
| Source URL | Embed | Form | Captured email | Last webhook | Received |
|---|---|---|---|---|---|
| /pricing/ | Loaded | Demo request | ana@northwind.io | conversation.started | Apr 24 14:02 |
| /contact/ | Loaded | Contact form | tom@studio.dev | conversation.replied | Apr 24 11:47 |
| /docs/install/ | Excluded | — | — | — | — |
| /blog/intercom-vs-drift/ | Loaded | Newsletter | ria@design.co | lead.captured | Apr 23 18:21 |
| /members/ | Suppressed | — | — | webhook.failed | Apr 23 09:08 |
Comparison
Default Drift plugin admin vs SleekView
Default Drift plugin admin
- Settings page lists rules, never resolves them into a per-URL row
- No view of which posts and pages currently load the widget
- Lead-capture form submissions live in a separate form plugin screen
- Local webhook event records sit in a table nobody opens
- No way to share or export an audit of embed coverage and capture flow
SleekView
- Per-URL rows resolved from Drift's include and exclusion rules
- Inline embed status (Loaded, Excluded, Suppressed) on every row
- Joined columns for the latest capture submission per page
- Joined columns for the latest webhook event per page
- Save filtered views per role (marketing, RevOps, integration owner)
Features
What SleekView gives you for Drift
Custom column sets per view
Build a marketing view with URL, embed status and last capture. Build an integration view with webhook event, status code and received_at. Each role gets the columns it actually uses.
Inline edits on overrides
Flip an exclusion flag on a single post, mark a webhook event row as triaged or update a capture-submission note without bouncing through three admin screens.
Compose precise filters
Combine embed status, post type, form_id, exclusion reason and webhook event_type. Save the filter as a named view your team reuses every week.
Audience
Who uses SleekView for Drift
Demand gen leads
Confirm the widget loads on every campaign landing page and that capture forms feeding the SDR queue are still firing, without screen-scraping the live site.
Web ops
Use the embed-status column to catch widget loads on templates that should not have Drift (docs, members areas, checkout) and prune the exclusions before tickets show up.
Integration owners
Filter the table to webhook.failed and conversation.started rows. Catch a broken endpoint days before the Drift dashboard shows a quiet handoff queue.
The bigger picture
Why Drift's WordPress half needs a real table
Drift's own UI is excellent for conversations, pipeline and playbook performance, and SleekView is not trying to compete with it there. The WordPress side of the integration is where reporting tends to stop. Embed coverage lives behind a settings toggle.
Lead-capture submissions live inside whichever form plugin a particular page uses. Webhook event records, when stored at all, sit in a custom table nobody opens. SleekView treats those three sources as a single dataset and renders them as one row per URL, submission or event.
Marketing sees where the widget actually loads. RevOps sees which forms still feed the queue. Integration owners see whether webhook delivery is alive.
Same database, completely different governance posture, no replacement for Drift's own reports.
Questions
Common questions about SleekView for Drift
No. Conversations, playbook performance and pipeline data stay in the Drift dashboard, which is the right tool for those views. SleekView only renders the WordPress-side surface: per-URL embed status, captured lead submissions stored locally and any webhook event records the site writes.
WordPress-native rows: the Drift plugin's wp_options entries, postmeta for any per-page overrides, the form plugin's submissions table for captures routed to Drift and a webhook log table when the site stores incoming Drift events. No Drift API call is required for these views.
SleekView resolves the plugin's enable rules (post types, conditions, manual overrides in postmeta) into a per-URL flag column. Sort or filter on that column to find every page that should be loading the widget today but is not, or every page that should not be loading it and is.
Yes. Each form plugin (Gravity Forms, WPForms, Contact Form 7 with a database extension, Forminator, Fluent Forms) stores submissions in its own table. Add each table as a dataset and the view normalises form_id, submitted_email and submitted_at into shared columns.
Yes. SleekView writes through the plugin's CRUD layer where one exists, so any filters the Drift plugin (or a companion CRM) registers on option updates or postmeta saves still fire. Bulk operations iterate the same path so side effects match a manual edit.
Queries hit standard WordPress indexes on options, postmeta and the form plugin's submissions table. Filters and sorts use indexed columns where possible, and expensive resolutions like per-URL embed flags are cached per page-load, so default views stay quick even on installs with high traffic.
Yes. Every SleekView view is gated by WordPress capability, so a marketing-facing Drift audit can be visible to marketing and RevOps roles while developers see a separate, more technical view with raw webhook events and override meta.
Yes. The plugin that embeds the Drift JavaScript widget stores its settings as standard WordPress options. SleekView reads those options, plus any related form submission and webhook log rows, without needing a paid Drift plan to render the WordPress-side tables.
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