SleekView for Amplitude Analytics
Read the Amplitude WordPress plugin's API key, event toggles, and user-property mappings directly. Each configured event becomes a row with status, hook source, post type, user property, and the last config change.
♾️ Lifetime License available
An API key in a settings field is not a tracking plan
The Amplitude WordPress plugin stores an API key and toggles for which events to forward: post published, user registered, login, comment posted, WooCommerce purchase, and similar hooks. The settings screen confirms the plugin is connected. It does not give you one list of every configured event with its hook source, the post type it applies to, and when the configuration was last touched.
SleekView turns the same plugin options into a table where each row is a tracked event. Status, hook source, post type, user property, and the option-modified timestamp sit in one sortable view inside WP Admin. Filter to one event name, one hook source, or one status and the table updates instantly.
The same dataset powers the SleekView Charts coverage dashboard for Amplitude, so a filter applied to the audit table carries straight into the chart cards. Amplitude keeps receiving events on the same hooks, with no extra front-end work.
Workflow
How SleekView reads Amplitude plugin data
Pick the source
wp_posts as one joinable source.
Compose the column set
Save and scope the view
Filter, sort, and export
Sample columns
A typical Amplitude event coverage table
wp_options (Amplitude plugin options) + wp_posts
| Event name | Status | Hook source | Post type | User property | Last change |
|---|---|---|---|---|---|
| Page Viewed | Active | wp | page | — | Apr 25 |
| Signed Up | Active | user_register | — | signup_source | Apr 23 |
| Logged In | Active | wp_login | — | role | Apr 22 |
| Purchase Completed | Disabled | woocommerce_order_status_completed | shop_order | order_total | Apr 14 |
| Comment Posted | Unconfigured | comment_post | post | — | — |
Comparison
Default Amplitude plugin settings vs SleekView
Default Amplitude plugin settings
- Settings screen confirms the API key is set but does not list every event in one place
- Hook source and post type are not surfaced per event in the admin UI
- User-property mappings live on a separate tab from event toggles
- Configuration changes are invisible without an external audit log
- No way to export the active event set without writing custom SQL
SleekView
- Read directly from the Amplitude plugin's API key and event toggles
- Per-event status, hook source, post type, and user property in one row
- Saved views per WordPress role for product, analytics, and engineering
- Shared filters with the SleekView Charts coverage dashboard
- CSV export of the tracking-plan audit without leaving WP Admin
Features
What SleekView gives you for Amplitude Analytics
Tracking plan as a list
Build separate views for product, engineering, and growth. Each saved view picks columns from the same Amplitude plugin options without admin compromises.
Precise event filters
Combine event name, hook source, status, and post type. Save the filter as a named view your team reuses every release QA or tracking-plan review.
Same data, two surfaces
The table view and the SleekView Charts coverage dashboard share one dataset. A filter in the audit table applies to the chart cards with no rebuild step.
Audience
Who uses SleekView for Amplitude Analytics
Product analytics teams
Filter to active events and confirm every step of the tracking plan is firing on the right hook before drawing funnel or retention conclusions in Amplitude.
Implementation engineers
Sort by last configuration change and trace a sudden drop in an Amplitude event back to the plugin option that changed, using the shared audit table.
Growth agencies
Filter to one client's hook sources, export the active event set to CSV, and attach it to the quarterly client report alongside the Amplitude funnel screenshots.
The bigger picture
Why Amplitude implementations need an event list
Amplitude is built on the assumption that the events arriving in it match the tracking plan on the source. WordPress installs make that assumption fragile. A plugin update silently disables a default event.
A staging copy keeps the dev API key in production for a day. A custom post type rename leaves the event firing on a slug that no longer exists. The Amplitude plugin settings tab cannot answer those questions in one screen, because it stores configuration rather than coverage.
SleekView turns the same plugin options into a table where each tracked event is a row, with hook source, post type, user property, and the last change in plain view. Same options, same WordPress hooks, but an audit list engineers and PMs can actually point a tracking-plan review at.
Questions
Common questions about SleekView for Amplitude Analytics
It reads the Amplitude WordPress plugin's options (API key, event toggles, user-property mappings), the wp_posts table for post_type and post_status, and the option revision history. No Amplitude server-side API token is required for the table view.
No. SleekView reports on what the WordPress plugin is doing locally: which events are enabled, which hooks they fire on, and how the configuration has changed over time. Funnel, retention, and cohort analysis stay in Amplitude.
Yes. If your install adds custom event-to-hook mappings, SleekView lists them in the column picker so the audit table can show them alongside the Amplitude plugin's defaults.
Yes. The table view and the SleekView Charts coverage dashboard share one dataset. A filter for one event name, one hook source, or one post type applies to both surfaces.
Yes when the Amplitude plugin's WooCommerce integration is active. Hooks for purchase, add to cart, and checkout become event slots in the plugin options, and SleekView reads them the same way it reads the core toggles.
No. SleekView reads existing options and posts and never writes to the Amplitude plugin's settings. The plugin keeps forwarding events on the same hooks, with no change to sampling, identity, or session handling.
Yes. Each subsite stores its own Amplitude API key and event mappings in its own options table. Network admins can build per-subsite tables or a network view scoped to specific blog IDs.
Yes. Any filtered set in the table exports to CSV with the visible columns. Engineering and product teams use the export to attach a tracking-plan audit to a sprint review or release checklist.
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