SleekView for Drip: WP-side sync settings & event hooks as tables
Drip pushes WooCommerce events straight to its cloud where the customer record lives. The WP plugin keeps account ID, opt-in defaults, JS-snippet flags and checkout text in wp_options. SleekView turns that into a real audit table.
♾️ Lifetime License available
Drip is intentionally thin on the WordPress side
The Drip for WooCommerce plugin is intentionally thin on the WordPress side. The plugin's design philosophy is "do as little as possible locally and let Drip own customer data." That means the only WP-side surface is a small set of options: drip_account_id, drip_default_checkbox, snippet attributes set via the drip_set_snippet_* filters, and any checkout-text overrides. There is no custom table, no per-product flag store, and no cached customer data.
That thinness is a feature on a single store and a problem on a multisite network. WordPress multisite gives each blog its own option row, so the same Drip account can be configured differently on the main store, the EU store, and a forgotten staging blog. The default Drip settings page is per-site and never rolls up. SleekView aggregates each blog's option row into one network-wide audit table, so a privacy team can confirm the opt-in default is off everywhere it matters and a marketing team can confirm every regional store points at the right account ID.
The opt-in default flag is the one most worth surfacing. Drip's own changelog notes that 1.0.4 accidentally turned that flag on for everyone, and the result was a regulator-attracting wave of pre-checked checkboxes at checkout. SleekView makes the current value of that flag a sortable column so it is hard to ship that mistake again.
Workflow
Drip's thin WP layer, made auditable
Aggregate option rows
Surface the privacy flags
Audit JS-snippet attributes
type and attributes set via the drip_set_snippet_* filters end up in options. SleekView shows them so devs are not grepping themes to find which store has which override.
Detect HPOS state
wc_orders vs posts) and joins to Drip's local config so order events line up with the right table on each blog.
Sample columns
A typical Drip multisite settings audit
wp_options. SleekView reads each multisite blog's option row.
wp_options
| Site | Drip account | Opt-in default | Snippet type | Checkout text | Status |
|---|---|---|---|---|---|
| main store | 9012345 | Off | module | Default | Active |
| EU store | 9012345 | Off | module | Custom (DE) | Active |
| test store | 9012345 | On | default | Default | Opt-in default on |
| legacy | (empty) | Off | default | Default | Not configured |
Comparison
Default Drip settings vs SleekView
Default Drip settings page
- Settings page is per-site — no multisite roll-up
- Opt-in default toggle is buried under a checkbox label
-
JS-snippet customization (added in 1.1.7) lives in
wp_optionswith no UI -
No quick way to audit which sites have
account_idset vs missing - Checkout-text overrides aren't visible from the network admin
SleekView
-
Show every multisite's Drip
account_idin one table - Flag sites where the opt-in default is on (a privacy red flag in many regions)
-
Surface custom JS-snippet attributes set via the
drip_set_snippet_*filters - Inline-edit checkout opt-in copy across stores
- Detect HPOS vs legacy WooCommerce so Drip's order events line up
Features
What SleekView gives you for Drip for WooCommerce
Network-wide Drip audit
On WordPress multisite, Drip is configured per blog. SleekView pulls each blog's option row into one cross-site table that an ops team can scan in one minute, not one hour.
Opt-in default visibility
If "opt-in by default" is enabled, every checkout pre-checks the box. SleekView lets you find and disable that fast for GDPR-sensitive stores before a regulator notices.
Snippet attribute audit
Custom type and attributes set via drip_set_snippet_* filters end up in options. SleekView shows them so devs are not grepping themes to find overrides.
Audience
Who uses SleekView for Drip
Multisite store ops
Confirm every regional store points at the right Drip account before a major campaign. One filtered table replaces opening each store's settings page individually.
Privacy team
Check that no production stores ship with the opt-in default set to on. Drip's own changelog warns this was accidentally everyone in 1.0.4, and SleekView keeps that mistake from spreading again.
Migration support
When migrating a store to Drip, audit the staged config against production before swapping account IDs. The diff is one column on the audit table, not a manual screenshot comparison.
The bigger picture
Multisite Drip drift is invisible from one settings page
Drip's plugin is small and well-behaved by design. It does not duplicate customer data into WordPress, it does not cache events, and it does not invent its own admin UI for things WooCommerce already does. That restraint is correct: Drip's value is in its cloud, where revenue reporting and abandoned-cart automations actually run.
The cost of that restraint is that the WP-side configuration becomes invisible. The only signal that the opt-in default is on, or that the staging store has a stale account ID, comes from clicking into the Drip settings page on each blog one at a time. On a 20-blog multisite, that is 20 round trips through three checkboxes.
The 1.0.4 changelog entry that admits opt-in-default-on shipped to everyone is the canonical example of why this matters. The flag was simple, the fix was simple, but the spread was real because nobody could check 20 sites at once. SleekView turns that audit into a single filtered table that takes 10 seconds to run.
Questions
Common questions about SleekView for Drip for WooCommerce
No. Drip's design pushes events out via JS and webhooks; none of that round-trips back into WordPress. SleekView focuses on the local WP-side config: account_id, opt-in defaults, snippet attributes, checkout strings. Cloud contacts and the per-event log live in Drip and are reached through the Drip dashboard.
Drip's options live in wp_options, typically under drip_account_id, drip_default_checkbox, and a few related keys for snippet customization and checkout text. SleekView surfaces them as named columns so the underlying serialized values become readable, sortable and filterable across the network.
Drip reads orders and products via WooCommerce's own data layer at runtime. The orders themselves are in wc_orders (HPOS) or posts (legacy). SleekView for WooCommerce covers that side; this view is the Drip configuration on top, so a complete audit usually combines both views.
Drip records events in its cloud, not in WordPress. To audit which events fired, use the Drip dashboard. SleekView's role is the WP-side surface only, which means it can confirm the integration is configured to fire events but not show the event log itself. That separation keeps the audit fast and the data model honest.
Yes. Drip 1.1.4 added HPOS compatibility. SleekView reads whichever order schema is active (wc_orders for HPOS, posts for legacy) and joins to Drip's local config without changes. On a network with mixed schemas across blogs, each row in the audit shows the active schema for that blog.
Yes. Drip 1.1.9 added multisite support, and each blog has its own settings option row. SleekView aggregates across blogs into one network-wide audit table. Filtering by site, account ID or opt-in flag works the same way it would on a single store.
Drip reports recurring revenue from WooCommerce Subscriptions through its cloud-side integration; the per-renewal event still lives in Drip. SleekView shows whether the subscriptions extension is active alongside Drip on each blog, so the configuration audit covers both extensions, but the event timeline belongs to Drip.
The database stores the current value, not the change history. If your install runs an option-change log plugin like Stream, SleekView can join that log into the audit table and surface the last change timestamp. Otherwise, only the current value is visible, which is still enough to catch the most common mistake.
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