SleekView Charts for Gravity Perks
Pivot gf_entry_meta, including Nested Forms parent IDs, Populate Anything sources, and Limit Submissions counters, into chart cards that summarise what your perks are actually doing.
♾️ Lifetime License available
Perks write rich data, dashboards rarely show it
Gravity Perks adds Populate Anything sources, Nested Forms parent/child IDs, Limit Submissions counters, and more, all stored in the same gf_entry_meta rows core Gravity Forms uses. The default Entries screen ignores most of those keys, which leaves perk-augmented sites with workflows whose source of truth lives in meta but whose summaries don't exist.
SleekView Charts reads gf_entry and pivots the perk-stamped meta keys into chart sources. A Number card pins the total entries this month across all perk-enabled forms. A Pie shows entries grouped by status or by Populate Anything source. A Bar ranks forms by submissions, or counts child entries per parent application. An Area card plots submissions per day so Limit Submissions caps are visible before they bite.
The same chart configuration adapts as new perks are added. The column picker reads which meta keys exist in your data, so a new perk's stamped keys show up as group-by candidates the next time you open the editor. No re-configuration when the perk stack changes.
Workflow
How SleekView Charts reads perk-augmented entries
Read the entry tables
gf_entry as the base. SleekView joins gf_entry_meta for perk-written keys and reads form labels from gf_form so the form column shows readable names instead of IDs.
Pivot perk meta into chart sources
Compose the cards
Save per role
Sample dashboard
Charts you can build from Gravity Perks data
Entries this month
Count
Entries by status
Count
group by status
Submissions per form
Count
group by form_id
Submissions per day
Count
group by date_created
Comparison
Default Gravity Forms admin vs SleekView Charts
Default Gravity Forms admin
- No native chart view, only paginated entries per form
- Perk-stamped meta keys don't appear in any summary
- Nested Forms parent/child counts require manual SQL or exports
- Populate Anything source distribution is invisible at the admin level
- Limit Submissions counters live on a settings screen, not a trend
SleekView Charts
-
Pivot perk-stamped
gf_entry_metakeys into chart group-bys - Chart Nested Forms child counts per parent application
- Group entries by Populate Anything source for audit dashboards
- Surface Limit Submissions trends as Area cards before caps hit
- Cross-form Number and Bar cards that ignore the per-form silo
Features
What SleekView Charts gives you for Gravity Perks
Perk meta as chart sources
Any meta key Gravity Perks writes becomes a group-by candidate in the chart editor. Add a perk, and its keys appear in the picker the next time you open it, no schema migration required.
Parent/child relationships visible
Nested Forms parent IDs power Bar cards that count child references per parent application, so application-with-references workflows have a real summary instead of a manual count.
Source-aware reporting
Populate Anything stamps source IDs into meta. Chart cards grouped by that key let auditors see which CRM, post, or user records drove the most prefilled submissions.
Audience
Who builds Gravity Perks charts dashboards with SleekView
Operations
Cross-form submission trends, status mix, and child entry counts for applications, all on one dashboard instead of one per-form Entries screen.
Form admins
Chart Limit Submissions counters approaching caps, audit Populate Anything source coverage, and watch Nested Forms hierarchies stay balanced over time.
Support leads
Top forms by support-related submissions, time-series of incoming volume per form, and status mix so escalations are caught when the backlog starts growing, not after.
The bigger picture
Why perk-augmented data deserves a perk-aware dashboard
Gravity Perks adds genuine power to Gravity Forms: Populate Anything for prefill, Nested Forms for parent/child structures, Limit Submissions for caps, GP Easy Pass for review flows. Each perk writes into the same gf_entry_meta table core fields use, which is great for storage and unhelpful for reporting, because the default Entries screen treats meta as opaque key/value pairs and never aggregates it. The teams running perk-heavy sites end up exporting CSVs, writing custom SQL, or building one-off plugins to answer questions that should be obvious: how many child references came in this week, which CRM source is filling the most applications, which form is about to hit its submission cap.
SleekView Charts reads the same meta the entries view reads, pivots it into chart sources, and lets a small set of cards summarise what every perk is producing. The plugin keeps owning entry storage and hook execution, the chart layer owns the summary, and admins get a dashboard that finally matches the data their perks have been collecting all along.
Questions
Common questions about SleekView Charts for Gravity Perks
No. SleekView Charts reads gf_entry and gf_entry_meta directly, so any subset of Gravity Perks works. The column picker exposes whichever meta keys exist in your data, regardless of which perk wrote them, and new keys appear automatically when new perks start writing them.
Yes. Nested Forms stores the parent entry ID in a meta key on each child entry. A Bar card grouped by that key counts children per parent, so application-and-reference workflows get a clear summary of how many references each application collected.
 Populate Anything stamps source object IDs and types into entry meta when configured. Group a Pie or Bar card by the source-type or source-object-ID key and the resulting card shows which CRM records, posts, or users are driving the most prefilled submissions.
 Yes, for the counters that live in queryable storage. An Area card grouped by date and filtered to a single form plots submission volume over time, so caps near their limits are visible before they trigger a hard-stop on the form.
 
Charts hit indexed columns on gf_entry (id, form_id, status, date_created) and use targeted joins to gf_entry_meta only for the columns a chart actually needs. The column picker scopes meta-key discovery to the active form or recent entries to stay responsive on installations with hundreds of forms.
Yes. Date range, form ID, status, and perk-specific filters set at the view level apply to every chart card on the dashboard. One saved view drives both the table and the chart layer for the same slice of entries.
 Yes. Saved chart views are gated by WordPress capability, so ops, form admins, and support each get their own dashboard with role-appropriate cards. The underlying source is the same, the chart configuration differs per role.
 No. Gravity's own entry list, form editor, and per-form reports stay where they are. SleekView Charts adds a cross-form, perk-aware summary layer on top of the data Gravity Forms and Gravity Perks already collect.
 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