SleekView Charts for Drift
SleekView Charts builds a dashboard out of the parts of Drift the WordPress install actually owns: where the widget script loads, which pages capture leads, and what webhook event records get written into wp_options or a custom log table.
♾️ Lifetime License available
Conversation analytics live in Drift. Embed health lives in WordPress.
Drift's reporting on conversations, playbooks and pipeline sits in the Drift dashboard, and SleekView Charts does not replace it. What the Drift dashboard cannot show is the WordPress half of the integration: which pages have the widget script loaded, which posts have it explicitly suppressed, how many lead-capture form submissions sent contacts into Drift over the last month, and whether the webhook endpoint the Drift plugin exposes is still receiving events.
SleekView Charts reads the WordPress-side data directly. The Drift plugin settings live in wp_options. Page-level overrides typically live in postmeta or in conditional logic stored on the settings page. Webhook event records, when the plugin or a companion CRM logs them, live in either a custom table or post-type rows. Lead capture form submissions that route to Drift live wherever the form plugin stores them (Gravity, WPForms, CF7 to a DB, etc.).
The chart cards below treat those WordPress-side artefacts as the primary dataset. They will not tell you how many qualified opportunities Drift created. They will tell you whether the widget is actually loading on the pages a campaign assumed it was loading on, and whether the capture flow into Drift is healthy.
Workflow
Turn Drift's WordPress footprint into a dashboard
Point SleekView at the relevant tables
Compose the chart cards
Save and scope the dashboard
Share or export
Sample dashboard
Charts you can build from Drift data
Pages with Drift loaded
Count
Embed status by post type
Count
group by post_type
Lead captures per form
Count
group by form_id
Webhook events received per day
Count
group by received_at
Comparison
Default Drift admin vs SleekView Charts
Default Drift admin
- Drift reports cover conversations, not WordPress embed coverage
- No view of which post types or templates currently load the widget
- Lead-capture form health on the WP side stays invisible in Drift
- Webhook event records into WordPress have no built-in dashboard
- No way to share a read-only embed-and-capture snapshot with the WP team
SleekView Charts
- KPI card for pages currently loading the Drift widget
- Pie of embed status across post, page and custom post types
- Bar of lead captures routed to Drift, grouped by source form
- Area trend of webhook events received by WordPress over time
- Same dataset behind the table and chart views, with shared filters
Features
What SleekView Charts gives you for Drift
Embed health, visible at a glance
Render the WordPress-side Drift footprint as Number, Pie, Bar and Area cards. Marketing leads see whether the widget is actually loading where a campaign assumed it was.
Filters span table and chart
Filter to a single landing-page cluster or to webhook events of a specific type, and both the chart cards and the table view stay in sync on the same underlying rows.
Share a read-only snapshot
Send stakeholders a URL of the embed-and-capture dashboard or export the filtered set to CSV. RevOps gets a WordPress-side audit to pair with the Drift reports they already use.
Audience
Who builds Drift charts dashboards with SleekView
Demand gen leads
Confirm the Drift 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 pie to catch widget loads on templates that should not have Drift (docs, members areas, checkout), and prune the exclusions before support tickets show up.
Integration owners
Watch the webhook events area chart. A flatline catches a broken integration days before the Drift dashboard shows a quiet handoff queue.
The bigger picture
Why Drift's WordPress half needs its own dashboard
Drift sells its own reporting hard, and for conversation, pipeline and playbook performance, that reporting is the right tool. The honest gap is the WordPress side of the integration: which pages actually load the widget today, whether form-to-Drift capture is still routing, and whether webhook events from Drift back into WordPress are still arriving. None of that lives in the Drift dashboard, and the WordPress admin does not render any of it as a quantity either.
SleekView Charts treats the existing WordPress data, plugin settings, form submission rows, webhook log entries, as a dataset and builds a small dashboard against it. Embed coverage as a KPI. Post-type split as a pie.
Captures per form as a bar. Webhook arrivals as a time series. The Drift dashboard stays the source of truth for what Drift does.
SleekView covers what WordPress holds.
Questions
Common questions about SleekView Charts for Drift
No. Drift conversations, playbook performance and pipeline data live in the Drift dashboard, which is the right place for that view. SleekView Charts only renders the WordPress-side surface: widget embed coverage, form-to-Drift submissions stored locally, and any webhook event log 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 to render these specific charts.
SleekView resolves the plugin's enable rules (post types, conditions, manual overrides in postmeta) into a per-URL flag column. Group by that column in a Number or Pie card to see total Drift-enabled pages and the split across post types in one card each.
Yes. Each form plugin (Gravity Forms, WPForms, Contact Form 7 with a database extension, Forminator) stores submissions in its own table. Add each table as a dataset and group by form_id or a normalised source column for a single Bar card across them.
Then the webhook-events Area card simply has no data. The other three cards (embed total, post-type pie, captures per form) still work entirely from settings and form rows. Adding a small custom-table logger is the usual next step if webhook visibility matters.
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 dashboards stay quick even on installs with high traffic.
Yes. Every SleekView dashboard is gated by WordPress capability, so a Drift embed dashboard can be visible to marketing and RevOps roles while developers see a separate, more technical view with raw event logs 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 the Drift premium plan to render the WordPress-side charts.
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