SleekView Charts for Iterable for WordPress
Iterable users, templates and workflows live in the Iterable SaaS. The Iterable WordPress plugin keeps the API key, the data center, form-to-list mappings and an identify/event log in wp_options. SleekView Charts renders that as Number, Pie, Bar and Area cards.
♾️ Lifetime License available
Iterable's WP plugin owns the bridge surface, not the campaign data
Iterable is a cross-channel marketing platform whose journeys, templates and reporting live in its SaaS. A WordPress install that uses Iterable typically does so through a bridge plugin or first-party SDK package that injects the Iterable client and persists API credentials, the data-center region and per-form list mappings to wp_options. Form bridges (Contact Form 7, Gravity, Fluent) keep their list mappings in wp_postmeta on the bridged form post.
The plugin's own admin shows the configuration screen and a connection check. It does not aggregate identify calls, it does not chart event volume per workflow, and it does not summarise how many pages the tracking client loaded on this week. The data is in the plugin's option store and event log; the surface to see it is missing.
SleekView Charts reads those storage paths directly. A Number card anchors weekly identify calls. A Pie distributes events across mapped Iterable lists or workflows. A Bar groups form bridges by source plugin. An Area trends events over time so a regression after a theme update is visible inside a day. Same plugin data, charted on one screen.
Workflow
Turn Iterable plugin storage into a dashboard
Map the Iterable plugin storage
Compose the chart cards
Save and scope the dashboard
Drill into the rows
Sample dashboard
Charts you can build from Iterable for WordPress data
Identify calls this week
Count
Events by Iterable workflow
Count
group by workflow_id
Form bridges by source plugin
Count
group by source_plugin
Events over time
Count
group by sent_at
Comparison
Default Iterable plugin reporting vs SleekView Charts
Default Iterable WP plugin admin
- Plugin admin is configuration plus a connection check, not aggregates
- Per-workflow event volume isn't summarised inside WordPress
- Form-to-list bridges open one at a time across multiple form plugins
- Tracking-client coverage across the site isn't visible at all
- No read-only dashboard URL to share with lifecycle ops
SleekView Charts
- Number KPI for weekly identify calls and events
- Pie split across the mapped Iterable workflows
- Bar grouping bridges by source form plugin
- Area trend of events for regression detection after a release
- Filters carry between chart and table view on the same dataset
Features
What SleekView Charts gives you for Iterable for WordPress
Dashboard over the event log
Render identify calls and events as Number, Pie, Bar and Area cards so the Iterable bridge becomes a one-screen dashboard the lifecycle team can read at a glance.
Workflow coverage
Pie across workflow_id surfaces which workflows are receiving entries and which mapped workflows have gone silent before the next campaign review.
Share a read-only snapshot
Send lifecycle a URL of the bridge dashboard or export the filtered event cohort to CSV. Reviews work off live numbers, not last week's screenshot.
Audience
Who builds Iterable for WordPress charts dashboards with SleekView
Lifecycle marketers
Anchor weekly reviews on identify call count, workflow mix and the area trend. Catch a workflow that stopped receiving entries before the next campaign drops into an empty cohort.
Growth and CRO
Rank form bridges by source and events by page slug to find the high-converting capture combinations. Replicate the winning pattern on adjacent pages.
Marketing ops
Track tracking-client coverage across staging and production. A flag set on staging but not on production surfaces as an obvious chart split on the multisite roll-up.
The bigger picture
Iterable's reporting lives in the cloud, the WP bridge needs its own dashboard
Iterable is a serious cross-channel platform and its dashboards reflect that. They live where they belong: in the Iterable SaaS, next to the workflow editor and the cross-channel reports. The WordPress bridge has the opposite problem.
It is small enough that operators forget it exists, until a theme switch removes the tracking embed or a list mapping points at a workflow that no longer takes entries. Charting the plugin's identify and event log against its bridge mappings turns the quiet settings screen into a one-page early warning system. A workflow with zero events is a workflow whose WP-side entry just broke.
A flat area chart the day after a release means the embed went missing. None of those signals require a new analytics tool: they are already in the plugin's option store and event log.
Questions
Common questions about SleekView Charts for Iterable for WordPress
No. Users, workflows and templates stay in the Iterable SaaS, which is exactly where cross-channel logic should live. SleekView Charts reads only the WP-side plugin storage: settings, form-to-list postmeta and the identify/event log.
Settings, the API key, the data-center region and tracking flags live in wp_options. Form-to-list mappings live in wp_postmeta on the bridged form post. SleekView reads both paths and pivots them into named columns.
Yes. Each dashboard respects a workflow filter, so a per-workflow audit scopes every card to one workflow and surfaces event count, source-form mix and time trend just for that workflow.
Yes. The plugin writes bridge mappings to each form plugin's standard postmeta location. SleekView reads them all, so a mixed-form site produces one clean dataset with a source-plugin column for grouping.
No. Chart queries hit the option store and postmeta on read, never on write. Identify calls and form bridges continue to run through the Iterable plugin's own runtime path with no added work, so visitor-facing latency stays unchanged.
Yes. The tracking flag is a boolean in the Iterable settings option. On a multisite or staging-plus-production setup, SleekView's roll-up shows that flag as a column on every site, so a staging-on, production-off mismatch is immediately visible.
Some Iterable plugin versions disable local event logging by default. SleekView shows an empty-state on the event cards in that case, and the settings and mapping cards (over wp_options) keep rendering so the rest of the dashboard stays useful.
Yes. Each saved dashboard is scoped by WordPress capability. Lifecycle sees workflow coverage and event trends while ops sees the tracking flag and bridge audit, with each role saving its own filter presets on the Iterable dataset.
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