SleekView Charts for Drip
Drip owns customers in its cloud. WordPress owns the account ID, opt-in defaults, snippet attributes, and checkout text. Chart those columns across every store and stop touring 20 settings pages.
♾️ Lifetime License available
Drip's WP layer is thin, and that is exactly why it needs charts
The Drip for WooCommerce plugin is intentionally thin on the WordPress side. Everything operational lives in wp_options: drip_account_id, drip_default_checkbox, snippet attributes set via the drip_set_snippet_* filters, and any checkout-text overrides. The default settings page handles one site cleanly. It never rolls up across multisite.
SleekView Charts treats those option rows as a chart source. A Number card pins the count of stores connected to the right Drip account. A Pie surfaces the opt-in-default mix (on vs off) across the network, which is the single field that caused the 1.0.4 changelog warning. A Bar ranks blogs by checkout-text customisation depth. An Area card plots option edits over time so a privacy reset shows as a curve.
The dashboard runs on the same row schema the SleekView for Drip audit table uses, so a saved chart view inherits the table filters. One configuration covers the morning compliance check and the executive report.
Workflow
How SleekView Charts reads Drip data
Aggregate option rows
Pivot privacy flags
Detect schema
wc_orders vs posts) gets surfaced so chart cards can scope to stores on the modern schema.
Save per role
Sample dashboard
Charts you can build from Drip data
Stores connected to Drip
drip_account_id, scoped to the multisite network. Disconnected stores stand out by their absence.
Count
Opt-in default mix
Count
group by drip_default_checkbox
Stores by Drip account
Count
group by drip_account_id
Drip option edits per day
Count
group by option_modified
Comparison
Default Drip reporting vs SleekView Charts
Default Drip settings page
- No dashboard view, only a per-site settings page
- Opt-in default mix across stores has no roll-up
- Snippet attribute audit is invisible without grepping themes
- Disconnected stores only complain on the next save
- Multisite ops cannot chart account-to-store relationships
SleekView Charts
- Number card for stores connected to Drip across the network
- Pie card for the opt-in-default flag mix (on vs off)
- Bar card ranking Drip accounts by how many stores point at them
- Area card for daily option-write volume across blogs
- Filters carry from the table view so audit and chart share a slice
Features
What SleekView Charts gives you for Drip for WooCommerce
Real columns drive real charts
Charts pull from wp_options directly, so every card uses the same field Drip's own runtime reads on each request. No CSV exports, no spreadsheet pivots.
Privacy flags as a KPI
The opt-in-default flag becomes a sortable Pie slice rather than a per-site checkbox. The 1.0.4 mistake stays catchable in one screen instead of 20 admin sessions.
Filters carry across cards
Scope to a single blog, account, or date range once and every chart card respects it. One saved configuration drives both the audit table and the leadership board.
Audience
Who builds Drip charts dashboards with SleekView
Privacy team
A board that pins opt-in-default mix, snippet-override count, and stores-without-account so a regulator review reads in one screen, not a tab tour.
Marketing ops
Confirm every regional store points at the right Drip account before a launch. The account Bar plus the connected Number card is the launch checklist.
Migration support
Stage-to-prod cutovers chart account-ID drift between blogs. A diff that used to be a screenshot comparison becomes a Bar card.
The bigger picture
Why Drip's thin WP layer needs visibility at scale
Drip's plugin gets restraint right: it does not duplicate customer data into WordPress, does not cache events, and does not invent its own admin UI for things WooCommerce already does. That restraint is correct as architecture. It becomes an operational gap at multisite scale.
The opt-in-default flag is the canonical example. Drip's own changelog records that 1.0.4 accidentally turned that flag on for everyone, and the only thing that stops a repeat is a team that can read the flag across every store in seconds. The chart view is what makes that possible.
It does not change Drip's design; it surfaces the data the plugin already stores in a shape that operations can read at the cadence operations actually runs. Twenty option rows become one Pie. One Pie becomes a one-glance compliance answer.
Questions
Common questions about SleekView Charts for Drip for WooCommerce
Directly from wp_options on each multisite blog. The account ID, opt-in default, snippet attributes, and checkout text are the option rows charted. No subscriber data or event log is pulled; those stay in Drip's cloud.
Yes. The drip_default_checkbox option is a chart source. A Pie grouped on that field surfaces the on-vs-off distribution across every blog in the network, which is the field most worth surfacing per the plugin's own changelog history.
No. Flow performance and abandoned-cart events live in Drip's cloud where the customer record is canonical. Charts cover the WP-side configuration layer only. To analyse flows, use Drip's dashboard; the two surfaces complement each other rather than overlap.
Yes. The chart view reads the same option rows the audit table writes to. When the table updates an opt-in flag or an account ID, the next chart refresh reflects the new value because both surfaces share one source.
Yes. Drip 1.1.4 added HPOS compatibility. Cards that touch order data join either wc_orders or posts depending on which schema is active on each blog. A network with mixed schemas charts cleanly without per-blog reconfiguration.
Yes. View-level filters (blog ID, account ID, date range) apply to every chart card on the dashboard. One saved configuration drives both the audit and the chart view, so morning triage and reporting share a slice.
Yes. Each saved chart view is gated by WordPress capability. Privacy reviewers, marketing ops, and migration leads can each save a view with role-appropriate cards while reading from the same Drip options.
No. Drip's cloud dashboard owns flow performance, revenue reporting, and event analytics. SleekView Charts adds a WP-side reporting surface that Drip never produced, focused on configuration drift across stores rather than on send results.
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