✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Charts for LearnDash Stripe: course payment dashboards

SleekView Charts reads the sfwd-transactions post type and its Stripe payment postmeta directly. Total revenue, plan mix, top courses by sales and revenue trend render as Number, Pie, Bar and Area cards in WP Admin without a separate Stripe report.

♾️ Lifetime License available

SleekView Charts dashboard for LearnDash Stripe Integration

Stripe knows the payments. The course data knows what they bought.

LearnDash's Stripe integration records each course purchase as a sfwd-transactions post with payment data in postmeta: price, currency, stripe_session_id, course_id and the recurrence flag for subscription plans. The transactions list in WP Admin is correct, but it is a list. Revenue this month, plan mix, top courses by gross sales and the daily revenue trend are not default visuals on either the LearnDash side or the Stripe side.

Stripe's own dashboard knows the payment but not the course. It groups by Stripe product ID, not by sfwd-courses post_title. A team that wants to see whether the flagship course or the introductory bundle drives the month has to map Stripe product IDs to courses by hand every time. The information is split across two systems, the join lives in the team's head.

SleekView Charts reads the LearnDash side. A Number card sums price across sfwd-transactions for the current month. A Pie splits revenue across one-off and subscription plans. A Bar ranks courses by gross sales using course_id on the transaction record. An Area trends revenue per day from the transaction post_date. The dashboard sits inside WP Admin, next to the course catalogue, so the revenue answer and the course context arrive on the same screen.

Workflow

Turn LearnDash Stripe payments into a dashboard

1

Map the transaction source

Point SleekView at the sfwd-transactions post type for the payment rows and at the postmeta keys (price, currency, course_id, plan recurrence) that carry the per-transaction details. Both are documented and indexed.
2

Compose the chart cards

Pick Number, Pie, Bar, Area, Line, Radar or Radial cards. Group by course_id, plan type, currency or post_date and aggregate as Count, Sum, Average, Maximum or Minimum across the transaction rows.
3

Save and scope the dashboard

Name the dashboard ("Stripe revenue", "Plan mix", "Top courses by sales") and gate it by WordPress capability so the finance lead, programme owner and L&D each see the right slice of the payment data.
4

Share or export

Send a stakeholder a URL of the dashboard or export the underlying transactions to CSV. The cards refresh against live sfwd-transactions data so a quarterly review starts from the latest payments, not yesterday's screenshot.

Sample dashboard

Charts you can build from LearnDash Stripe data

Each card reads sfwd-transactions and its Stripe postmeta directly, so the dashboard reflects whatever payments LearnDash has already recorded against the course catalogue.
Number · Default

Course revenue this month

Sums the price postmeta on sfwd-transactions posts created in the current month, with the previous month underneath for context. Refunded transactions filtered out by post_status. The anchor revenue KPI.
Sum(price)
Pie · Donut

Revenue by plan type

Splits revenue across one-off course purchases and recurring subscription plans by reading the recurrence postmeta on sfwd-transactions. Reveals whether the business is funded by upfront sales or subscription momentum.
Sum(price) group by plan_type
Bar · Horizontal

Top courses by gross sales

Ranks courses by total Stripe revenue using the course_id postmeta on each sfwd-transactions row, resolved back to the sfwd-courses title. Surfaces the courses that pay for the catalogue.
Sum(price) group by course_id
Area · Gradient

Daily revenue trend

Time series of Stripe revenue per day from the transaction post_date. Reveals weekday patterns, the impact of a launch and the lag between a marketing push and a measurable revenue bump.
Sum(price) group by post_date

Comparison

Stripe dashboard vs SleekView Charts for LearnDash

Stripe dashboard

  • Stripe groups by Stripe product ID, not by sfwd-courses title
  • Course context lives in WordPress, payment context lives in Stripe, the join is manual
  • Per-course revenue ranking requires mapping Stripe products to courses by hand
  • Plan mix on the Stripe side does not distinguish course types or learning cohorts
  • Stakeholders without a Stripe seat cannot see the operational revenue picture

SleekView Charts

  • Revenue KPI sourced from price postmeta on sfwd-transactions
  • Donut split across one-off and recurring plan types
  • Bar ranking courses by gross sales using course_id on the transaction
  • Area trend of daily revenue from transaction post_date
  • Same join the LearnDash admin already uses, no manual product mapping

Features

What SleekView Charts gives you for LearnDash Stripe Integration

Revenue in course terms

Render sfwd-transactions and its Stripe postmeta as four chart cards keyed to course_id. The dashboard speaks the catalogue's language instead of Stripe's product-ID schema.

Filter by plan or course

Filter to a single course or to subscription plans only and the underlying transaction table stays in sync. Same sfwd-transactions query, two surfaces, no duplicate filter UI.

Share without a Stripe seat

Send a programme owner or finance partner a URL of the revenue dashboard. They see the per-course revenue picture without needing a Stripe seat or a Stripe-to-course mapping in their head.

Audience

Who builds LearnDash Stripe charts dashboards with SleekView

Programme owners

Anchor a monthly business review on revenue, plan mix and top courses. See whether the flagship course is still pulling its weight and whether subscription momentum is replacing one-off sales as planned.

Marketing teams

Compare the area chart of daily revenue against campaign dates. A launch that does not show up as a step change usually means the campaign did not reach the segment that buys, not that the offer is wrong.

Finance partners

Pull a per-month CSV from the dashboard for an internal report. The export reflects whatever filters the dashboard applies, so a finance review of subscription-only revenue is a one-click export instead of a Stripe-side query.

The bigger picture

Why course revenue belongs next to course data

LearnDash and Stripe each hold half the revenue picture. Stripe knows the amount, the gateway and the timing. LearnDash knows the course, the plan and the learner.

The Stripe dashboard groups by Stripe product ID and the LearnDash admin groups by course post, so a question like "how much did the flagship course earn last month" requires a manual join every time. Putting sfwd-transactions on a chart dashboard inside WP Admin closes that gap. Revenue is measured in course terms, plan mix is visible at a glance, top courses are ranked by gross sales rather than by Stripe product ID, and the daily revenue trend is visible against campaign dates that any programme owner already knows by heart.

Finance partners get a per-course CSV that means something. Programme owners get a quarterly review that takes three seconds rather than three days. The data does not change.

The friction between question and answer disappears.

Questions

Common questions about SleekView Charts for LearnDash Stripe Integration

The sfwd-transactions post type and the Stripe-specific postmeta keys LearnDash writes per transaction: price, currency, course_id, the recurrence flag for subscription plans, and the stripe_session_id for traceability back into Stripe when an investigation needs the gateway view.

 

No. It reads what LearnDash has already written into sfwd-transactions. That keeps the dashboard fast and avoids Stripe rate limits. The stripe_session_id is on the transaction record for the rare case where a finance review needs to open Stripe's view of the same payment.

 

Yes. The course_id postmeta on each transaction resolves back to the sfwd-courses post, so the Bar chart of top courses by gross sales naturally separates standalone courses from courses sold via a bundle. Bundles can be aggregated through the parent course post.

 

Yes. Refunded transactions are filtered out of revenue calculations by post_status, the same way LearnDash itself treats them in the transactions list. A refund-specific Bar chart can be built alongside the revenue dashboard for a dedicated finance view.

 

Yes. LearnDash writes a new sfwd-transactions post for each renewal, and the recurrence postmeta marks it as subscription revenue. The Pie chart of plan types reads that flag directly, so renewals show up against one-off sales without manual classification.

 

The cards render against the live sfwd-transactions table. There is no scheduled aggregation job and no separate analytics store. A payment LearnDash has already recorded shows up on the dashboard at the next render.

 

No. sfwd-transactions uses standard WordPress post indexes plus the indexed postmeta keys LearnDash writes per payment. Sites with hundreds of thousands of transactions still render the dashboard well under a second on typical Kinsta or WP Engine hardware.

 

Yes. Every dashboard exports the underlying transactions to CSV or JSON. Useful for sending a per-course revenue report to a finance partner or for combining LearnDash payment data with the company's accounting system outside WordPress.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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