✨ 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 LifterLMS PayPal: course payment dashboards

SleekView Charts reads llms_order posts and the PayPal gateway postmeta directly. Active subscriptions, plan mix, daily revenue and gateway split against Stripe render as Number, Pie, Bar and Area cards without a separate PayPal-side report.

♾️ Lifetime License available

SleekView Charts dashboard for LifterLMS PayPal

PayPal sees the payment. LifterLMS sees the access plan. The dashboard sees both.

LifterLMS PayPal records every payment as an llms_order post with postmeta keys for _llms_total, _llms_currency, _llms_payment_gateway set to paypal, the recurrence flag and the PayPal transaction ID. Subscription renewals create child orders linked to the parent. The orders screen lists the rows, but a course business that takes payments through both PayPal and Stripe needs a visual to see how the gateway split is moving.

PayPal's own activity view groups by transaction type and payer email, not by LifterLMS access plan. A team that wants to see whether the monthly or annual plan drives PayPal revenue has to cross-reference PayPal exports with the LifterLMS orders list every time. The information lives in two places, the join lives in a spreadsheet, and the spreadsheet goes stale the day it is sent.

SleekView Charts reads the LifterLMS side. A Number card sums _llms_total across PayPal-source orders for the current month. A Pie splits revenue across access plans. A Bar compares PayPal against Stripe gross revenue using _llms_payment_gateway. An Area trends daily revenue per gateway against campaign dates. The dashboard lives inside WP Admin, next to the catalogue, so a gateway-mix conversation starts and ends on one screen.

Workflow

Turn LifterLMS PayPal data into a dashboard

1

Map orders and gateways

Point SleekView at the llms_order post type for the order rows and at the PayPal-specific postmeta keys (_llms_total, _llms_payment_gateway, _llms_status, recurrence, paypal_transaction_id) that carry the per-order details.
2

Compose the chart cards

Pick Number, Pie, Bar, Area, Line, Radar or Radial cards. Group by access plan, payment_gateway, status or post_date and aggregate as Count, Sum, Average, Maximum or Minimum across the PayPal-source rows.
3

Save and scope the dashboard

Name the dashboard ("PayPal revenue", "Gateway mix", "Per-plan PayPal sales") and gate it by WordPress capability so the finance lead, programme owner and L&D each see the slice that fits their role.
4

Share or export

Send a stakeholder a URL of the dashboard or export the underlying PayPal-source orders to CSV. The cards refresh against live llms_order data so the next quarterly review starts from the latest PayPal payments.

Sample dashboard

Charts you can build from LifterLMS PayPal data

Each card reads llms_order posts filtered to the PayPal gateway and the related postmeta directly, the same sources LifterLMS itself queries for the built-in orders screen.
Number · Default

PayPal revenue this month

Sums the _llms_total postmeta on llms_order posts with _llms_payment_gateway of paypal for the current month, with the previous month underneath. Failed and refunded orders filtered out via _llms_status.
Sum(_llms_total)
Pie · Donut

Revenue by access plan

Splits PayPal revenue across configured access plans by summing _llms_total and grouping on access_plan_id. Reveals which access plans rely on PayPal versus Stripe and where the gateway choice changes the conversion shape.
Sum(_llms_total) group by access_plan_id
Bar · Horizontal

Gateway split: PayPal vs Stripe

Ranks gateways by gross revenue using _llms_payment_gateway on llms_order. Useful for tracking whether a payments rollout is shifting the gateway mix as planned and whether one gateway absorbs more failed orders than the other.
Sum(_llms_total) group by _llms_payment_gateway
Area · Gradient

Daily PayPal revenue

Time series of PayPal revenue per day from llms_order.post_date. Reveals weekday patterns and helps measure whether a marketing push produced a measurable bump within the PayPal stream specifically.
Sum(_llms_total) group by post_date

Comparison

PayPal activity view vs SleekView Charts for LifterLMS

PayPal activity view

  • PayPal groups by transaction type and payer email, not by LifterLMS access plan
  • Per-plan PayPal revenue requires cross-referencing PayPal exports with the orders list
  • Gateway split between PayPal and Stripe is not a default visual on either side
  • Daily revenue against campaign dates requires a manual spreadsheet pivot
  • Stakeholders without a PayPal seat cannot see the operational revenue picture

SleekView Charts

  • Revenue KPI from _llms_total on PayPal-source llms_order rows
  • Donut of revenue across LifterLMS access plans for the PayPal stream
  • Bar comparing PayPal against Stripe via _llms_payment_gateway
  • Area trend of daily PayPal revenue from order post_date
  • Same join LifterLMS already uses, no manual gateway mapping

Features

What SleekView Charts gives you for LifterLMS PayPal

PayPal revenue in plan terms

Render llms_order posts and the PayPal postmeta as four chart cards keyed to the access plan. The dashboard reports revenue in catalogue terms instead of in PayPal's txn_type schema.

Gateway mix at a glance

Compare PayPal against Stripe on a single Bar card using _llms_payment_gateway. The mix shift across a quarter shows whether the rollout plan is landing or whether one gateway is quietly absorbing more failed orders.

Share without a PayPal seat

Send a finance partner or programme owner a URL of the revenue dashboard. They see the per-plan PayPal picture without needing PayPal access or a manual export and merge step.

Audience

Who builds LifterLMS PayPal charts dashboards with SleekView

Programme owners

Anchor a monthly business review on PayPal revenue, plan mix and gateway split. See whether PayPal still pulls its weight against Stripe or whether the gateway mix is quietly shifting under campaign changes.

Finance partners

Pull a per-month CSV from the dashboard with the gateway and plan filters the live cards use. The export replaces the monthly PayPal-to-LifterLMS reconciliation with a one-click download.

Growth marketing

Compare the area chart of daily PayPal revenue against campaign dates. A push that produced no bump in PayPal-side revenue often means the segment that responds to that campaign was already on Stripe, not that the offer is wrong.

The bigger picture

Why PayPal revenue deserves a plan-level dashboard

LifterLMS and PayPal each hold half the revenue picture. PayPal groups by transaction type and payer email, LifterLMS groups by access plan and order post, and the team that wants to know which plan drives the PayPal stream has to cross-reference exports by hand. Putting llms_order filtered to the PayPal gateway on a chart dashboard inside WP Admin closes the gap.

Revenue is measured in access-plan terms, gateway split against Stripe is visible at a glance, daily revenue is plotted against campaign dates that the marketing team already knows, and finance gets a per-plan CSV that means something without a reconciliation step. The data does not change, the time to see it does, and the conversation about gateway mix moves from quarterly spreadsheet to live dashboard URL. Same llms_order rows, dramatically more operational confidence in how PayPal contributes to the catalogue revenue.

Questions

Common questions about SleekView Charts for LifterLMS PayPal

The llms_order post type and the PayPal-specific postmeta keys: _llms_total, _llms_currency, _llms_payment_gateway set to paypal, _llms_status, the recurrence flag and the PayPal transaction ID. Renewals create child orders linked through _llms_parent_order for attribution back to the originating sign-up.

 

No. It reads what LifterLMS has already written into llms_order when each PayPal IPN or webhook fired. That keeps the dashboard fast and avoids PayPal rate limits. The order record carries the PayPal transaction ID for the rare case where a finance review needs the gateway view of the same payment.

 

Yes. The Bar chart groups by _llms_payment_gateway and ranks gateways by gross revenue. The same dashboard can show a side-by-side view, a single-gateway view or a stacked area chart of the gateway mix over time without rewriting the underlying query.

 

Yes. _llms_status carries values like llms-failed, llms-pending, llms-refunded and llms-cancelled in addition to llms-active and llms-completed. The dashboard can filter to failures only or split revenue by status for a gateway-health view.

 

Yes. LifterLMS writes a child llms_order for each PayPal renewal IPN, with _llms_parent_order pointing back to the original sign-up. The dashboard separates new sign-ups from renewals without manual tagging and can attribute renewal revenue to the originating access plan.

 

The cards render against the live llms_order table. There is no aggregation job and no separate analytics store. A PayPal IPN LifterLMS has already processed shows up on the dashboard at the next render.

 

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

 

Yes. Every dashboard exports the underlying llms_order rows to CSV or JSON. Useful for sending a per-plan PayPal revenue report to a finance partner or for combining LifterLMS gateway 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