SleekView Feedback for Monarch Pro
Monarch Pro stores share buttons, follow counters, and network configs inside the Divi options API. SleekView reads those records and turns each network, placement, and counter into a votable card so editors and growth teams can rank what is working and retire what is not.
♾️ Lifetime License available
Sharing feedback built on the Monarch options
Monarch Pro from Elegant Themes lives inside the Divi options pipeline. Networks, placement choices (inline, sidebar, popup, fly in, media, automatic share), and follow counters are all serialized into the et_monarch_options entry in wp_options, with per post overrides scattered across wp_postmeta. The default Divi screens give one admin a stack of toggles, but no shared view of which networks actually earn shares or which placements convert.
SleekView reads the Monarch configuration straight from wp_options and any custom logging table you set up to record share clicks. Map a click counter or a per network follower meta key to the vote column, point status pills at values like Live, Paused, A B test, or Retired, and use the placement label as the category chip. The result is a board where each Monarch network and placement gets one card and editors can upvote the ones worth keeping.
Because SleekView is read mostly against Monarch records, the Divi settings page stays the source of truth. Editors flip toggles where they always have, but the votes, status pills, and category chips on the board give the growth team a shared queue without exporting CSVs into a spreadsheet every week.
Workflow
From Monarch options to a public board
Point SleekView at Monarch
et_monarch_options entry plus any per post overrides, so every Facebook, X, LinkedIn, or Pinterest button you have configured shows up as one row in the board.
Map votes, status, category
Embed the board for the team
Votes feed the next experiment
Sample board
Sample Monarch share board
Comparison
Monarch admin vs SleekView Feedback
Default Monarch options
- Divi options stack of toggles with no ranked view of which networks actually earn shares
- Click counts, if logged at all, sit in a CSV export the growth team rebuilds every week
- No public roadmap of which Monarch experiments are Live, Paused, or Retired across the site
- Per post overrides are scattered across postmeta with no surface to triage them in bulk
- Editors argue about placement changes in Slack instead of voting on a shared queue
SleekView Feedback
-
Reads the serialized
et_monarch_optionsentry and per post overrides with no migration - Upvote button writes back to a click counter or vote meta key so Monarch can read it
- Status pills cover Live, Paused, A B test, and Retired states out of the box on every card
- Placement labels like inline, sidebar, popup, and fly in appear as colored category chips
- Saved views let growth leads share boards like Underperforming Networks without code
Features
What SleekView Feedback gives you for Monarch Pro (Elegant Themes)
Native Monarch options support
SleekView speaks the Monarch options schema. It maps each configured network, placement, and follower counter to a card with vote, status, and category fields, so a sharing feedback board can launch on top of an existing Divi install in minutes.
Click counts drive votes
Each upvote increments a meta value you tied to Monarch share clicks. The score is queryable, exportable, and visible inside the Monarch settings, which means the source of truth stays inside Divi instead of forking into a separate analytics tool.
Placement experiments visible
Inline, sidebar, popup, and fly in placements each get their own card on the board. Editors and growth leads see at a glance which placements are Live, which are running an A B test, and which are queued for retirement without opening the Divi admin.
Audience
Three teams that ship Monarch experiments with SleekView
Editorial growth squads
Growth leads open a board ranked by share clicks per network. Pinterest cards float above LinkedIn on lifestyle posts, the team upvotes a placement test, and the next sprint is already scoped before the Monday standup begins.
Agency client roadmaps
Agencies running Monarch on client sites share the board with the client. They see which buttons are Live, which placements are queued, and what is retired, so the conversation moves from gut feel to a shared, vote driven queue.
QA and bug triage
Editors flag broken share counts and weird popup behaviour on specific networks. Each bug becomes a card with a status pill, so the developer fixing the floating sidebar on iOS knows exactly which Monarch config is in scope.
The bigger picture
Why Monarch sharing needs a public board
Monarch ships with a generous bag of networks, placements, and follower widgets, which makes it easy to throw every button on every page and call it done. That is exactly how share buttons stop earning their place. Pinterest carries lifestyle posts but the team forgets to enable it on the new long form template.
The StumbleUpon button is still lit up three years after the service died. The mobile popup is breaking on iOS but nobody on the editorial team logs into Divi to notice. The data to fix all of this exists, it just lives in serialized options and per post overrides that one admin at a time can edit.
SleekView gives the same records a shared, vote driven home. Click counts become vote weights. Placement labels become category chips.
A B test, Live, Paused, and Retired become colored status pills. Growth leads open one board, sort by score, and see which Monarch experiments actually moved shares. Editors flag broken counters on a card instead of in a Slack thread.
The result is fewer dead buttons, fewer half tested placements, and a sharing setup that the whole team can defend in a roadmap review.
Questions
Common questions about SleekView Feedback for Monarch Pro (Elegant Themes)
No. SleekView reads the serialized et_monarch_options entry and per post overrides through the normal WordPress options API. The only write is the upvote increment, which lands on a meta key you choose so the score sits alongside the rest of the Monarch configuration.
You either point SleekView at a click log table you already maintain, or you wire up a small action hook that increments a counter on every Monarch share. The view treats that counter as the vote score, so popular networks float to the top of the board automatically.
Yes. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a shortcode. Drop the board on an internal Growth Dashboard page and editors can vote, flag bugs, and read status pills without ever loading the Monarch settings screen.
Yes. Per post type overrides Monarch stores in postmeta show up as their own cards on the board, so a placement tuned for case studies appears as a separate row from the global default. Editors can vote on each variant individually instead of arguing about averages.
Both modes are supported. Most teams keep the Monarch board internal because the audience for share placement decisions is editorial, but a public Roadmap page that exposes the cards with vote and status pill is a clean way to publish the sharing plan to readers.
When you delete a network in Monarch, the underlying option key disappears and the corresponding card drops off the board on the next refresh. If you only disable the network, the card stays with a Paused status pill so the historic vote count is still visible to the team.
Yes. The follower widget exposes per network counters that SleekView can read like any other meta value. Map the follower count to a numeric column on the card and editors get a leaderboard of follower growth per channel without leaving WordPress.
SleekView paginates and sorts at the database level, so a Monarch setup with hundreds of per template placements still renders the top of the board in well under a second. Scoping a saved view by template or by status keeps both the query and the audience focused.
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