All 16 Lucky Wheel sections

See every section

Leads and revenue

Updated Lucky Wheel 1.12.0Tested with WordPress 7.1

Every spin is stored on the Leads screen: the email, whether they won, the coupon, and — once they buy — the order and the revenue it brought in. Search and filter the list, and export the whole thing to CSV at any time; the file's column headings are in your admin language. The totals at the top, and on the dashboard, show emails collected, spins, wins and the revenue the wheel has earned. A spin turned away after it was taken (nothing left to win, the prizes changing under it, or a coupon that could not be made) is given back, and a shopper spinning for the first time is then not stored at all.

The revenue is what the shop kept, after refunds. A paid order that used a wheel coupon adds its total, less any refund already made on it, to the lead who won the coupon, and one order to the count. A refund made after that comes off the revenue as it is made. An order that is cancelled, fully refunded or whose payment fails comes off entirely and leaves the order count. If it is later paid again (moved back to Processing or Completed), what is left of it after refunds is added back once; an order refunded in full stays out of the count.

Deleting a refund, with the delete link on the order screen or through the WooCommerce REST API, puts its amount back. An order that is out of the figure because it is marked Refunded, Cancelled or Failed stays out after a refund on it is deleted, because WooCommerce leaves its status as it was; move it back to Processing or Completed and what is left of it is added back then. A refund deleted any other way, by another plugin say, is not seen.

This works from the update that added it onwards. It does not go back through old orders. On a shop that had the wheel before, the card says since when, for example from 12 orders, after refunds since 22 September 2026. A refund or cancellation from before that day stays in the figure until something new happens to the same order (another refund, a cancellation or a failed payment). Then that order catches up with every refund it has, so the figure can drop by more than the new refund. A shop that installs the wheel fresh sees from 12 orders, after refunds.

Moving an order to the bin, or deleting it, does not change the figure. Only orders that used a wheel coupon count.

Delete at the end of a row removes that lead for good, and its spins, wins and revenue come out of the totals with it. Coupons already sent keep working, but any expiry reminder still booked for them is cancelled, so the person is not emailed again.

Privacy#

The wheel's leads are part of WordPress's own privacy tools. Tools → Export Personal Data includes what the wheel holds for an address, and Tools → Erase Personal Data clears it: the name, phone number, IP address and consent are removed and the address replaced, while the spins, wins and revenue stay in the totals, as they are the shop's figures rather than the person's. The address is also taken off the coupons the wheel made for that person, which stay locked, so they can no longer be used. Settings → Privacy offers a suggested paragraph for your privacy policy.

The Your prize button keeps a winner's codes (up to five), each with its prize, date, conditions and apply link and a short tag worked out from the email it was won with (not the email itself), in that shopper's own browser (its local storage), not on your site, and sends them nowhere; there is nothing of it for these tools to export or erase. Where the site runs WP Consent API, it is kept only for shoppers who allow preferences. While the reminder is on, the suggested privacy paragraph says in a sentence of its own that the code may be kept in the shopper's browser.

The expiry reminder email stores nothing new about the person: the plugin notes on the coupon when its reminder was sent, and on an order that it used a code after one, so neither is sent or counted twice. While it is switched on, the suggested privacy paragraph gains a sentence saying a winner may be emailed once before their code ends, and only with their agreement where the form asks for it. Uninstalling with Delete all data on uninstall removes those notes and the Dashboard's counts; any reminder still booked is taken off the schedule whatever that setting says, as nothing would be left to send it.

While MailPoet or FluentCRM is switched on under Email Lists, the suggested privacy paragraph says that players are added to the site's own newsletter list.

Still stuck? Ask the developers who wrote it. We aim to reply within one business day.