SleekView Charts for Customer.io for WordPress
Customer.io people, campaigns and journeys live in the Customer.io SaaS. The WordPress plugin keeps the site ID, the tracking flag, form-to-campaign mappings and the identify/event log in wp_options. SleekView Charts renders that as Number, Pie, Bar and Area cards.
♾️ Lifetime License available
Customer.io's bridge data is the only signal WordPress can chart
Customer.io is a lifecycle messaging platform built around an event stream and a journey engine. The WordPress plugin's role is small but well-scoped: load the Customer.io JavaScript, run identify calls for logged-in users, optionally bridge form submissions to campaigns, and persist the site ID, API key and consent defaults to wp_options. Per-form mappings sit in wp_postmeta when a Gravity, Fluent or Contact Form 7 bridge is enabled.
The default Customer.io plugin admin in WordPress shows the settings and a connection check. It does not aggregate, and it does not chart. Questions like "how many identify calls fired this week", "which form is posting the most events into which campaign" and "did the tracking flag turn off on a staging environment" all have answers in the plugin's option storage and event log, but they are not surfaced.
SleekView Charts reads the plugin storage directly. A Number card anchors weekly identify calls. A Pie distributes events across mapped campaigns. A Bar groups form bridges by source plugin. An Area trends events over time so a regression after a theme switch is visible inside a day. Same Customer.io plugin data, organised as a one-screen bridge dashboard.
Workflow
Turn Customer.io plugin storage into a dashboard
Map the Customer.io plugin storage
Compose the chart cards
Save and scope the dashboard
Drill into the rows
Sample dashboard
Charts you can build from Customer.io for WordPress data
Identify calls this week
Count
Events by Customer.io campaign
Count
group by campaign_id
Bridges by source plugin
Count
group by source_plugin
Event volume over time
Count
group by sent_at
Comparison
Default Customer.io plugin reporting vs SleekView Charts
Default Customer.io WP plugin admin
- Plugin admin is configuration plus a connection check, no aggregates
- Per-campaign event volume isn't summarised inside WordPress
- Form-to-campaign bridges open one at a time across multiple form plugins
- Tracking-script 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 on the bridge
- Pie split across the mapped Customer.io campaigns
- 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 Customer.io for WordPress
Dashboard over the event log
Render identify calls and events as Number, Pie, Bar and Area cards so the Customer.io bridge becomes a live performance dashboard inside WP Admin.
Campaign coverage at a glance
Pie across campaign_id surfaces which campaigns are getting traffic and which mapped campaigns have gone quiet, before the next lifecycle review.
Share a read-only snapshot
Send lifecycle a URL of the bridge health dashboard or export the filtered event cohort to CSV. Reviews work off live numbers, not last week's screenshot.
Audience
Who builds Customer.io for WordPress charts dashboards with SleekView
Lifecycle marketers
Anchor weekly reviews on identify calls, campaign mix and the area trend. Catch a campaign that stopped receiving entries before the next nurture send hits 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-script coverage across staging and production. A flag flipped on staging but not on production surfaces as a clear split on the multisite roll-up.
The bigger picture
Customer.io's event stream relies on a small WP plugin staying healthy
Customer.io's product is its event stream and its journey engine, both of which run in the cloud. The WordPress plugin's job is narrow: load the JavaScript, fire identify calls, bridge forms when configured and persist the right settings. That narrow scope is also why the bridge is so easy to lose track of after a theme switch, a page-builder upgrade, or a multisite roll-up.
Charting the plugin's identify and event log against its bridge mappings turns the silent settings screen into a live dashboard. A campaign with zero events is a campaign whose WP-side entry broke. A flat area chart the day after a release means the tracking script went missing.
None of those signals require an extra analytics service: they live in the plugin's own option store and event log, waiting to be charted.
Questions
Common questions about SleekView Charts for Customer.io for WordPress
No. People, campaigns and journeys stay in the Customer.io SaaS, which is exactly where lifecycle logic should run. SleekView Charts reads only the WP-side plugin storage: settings, form-to-campaign postmeta and the identify/event log.
Settings, the site ID, the API key and the tracking flag live in wp_options. Form-to-campaign 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 campaign filter, so a per-campaign audit scopes every card to one campaign and surfaces event count, source-form mix and time trend just for that campaign.
Yes. The plugin writes bridge mappings to each form plugin's standard postmeta location, and SleekView reads all of them. A mixed-form site still 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 Customer.io plugin's own runtime path with no added work, so visitor-facing latency stays unchanged.
Yes. The tracking flag is a boolean in the Customer.io settings option. On a multisite or staging-plus-production setup, SleekView's roll-up shows that flag as a column on every site, making mismatches between environments immediately visible.
Some Customer.io 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 campaign coverage and event trends while marketing ops sees the tracking flag and bridge audit, with each role saving its own filter presets on the same Customer.io 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