Rewards and Benefits
Part of Paid loyalty memberships
Measuring whether paid members use the promised benefits
Measure entitlement, attempts, completed uses and failed claims for each paid-membership benefit.
Measure use against the members entitled to each benefit during a defined paid term. Record attempts, completed uses and failures separately. A low-use total alone cannot tell you whether a benefit was unwanted, unnoticed or difficult to claim.
Map each promise to an event
List the benefits in the joining offer and their access conditions. For each, identify the account event showing entitlement, any observable attempt and the event showing completed fulfilment. A voucher issued but never applied is not automatically a completed use. A booking made and a service attended are also different events.
| Question | Record to define |
|---|---|
| Who could use it? | Eligible paid members and their entitlement periods |
| Who tried? | Members with a recorded claim or booking attempt |
| Who received it? | Members with at least one completed use and total completed uses |
| What failed? | Attempts blocked by eligibility, stock, capacity, checkout or system error |
| What remains open? | Issued vouchers, bookings and unresolved requests |
Report both the share of entitled members who completed at least one use and completed uses per entitled member. Name the denominator and period for every rate. If an attempt cannot be observed in a channel, disclose that gap rather than treating absence of a record as proof that no attempt occurred.
Compare equivalent opportunities
Group members by joining or renewal term, and account for how long each had access. A new member has had less opportunity to use an annual benefit than one near the end of the term.
Record interruptions in stock, booking availability or system access. For a benefit limited to one use, a member-based completion rate may be straightforward; for repeatable benefits, show both distinct users and total uses.
Investigate the gap
Compare visibility of the benefit, invitations, stock or appointment availability, checkout errors and support contacts. Ask relevant members whether they knew about the benefit and could use it under the stated conditions. Keep interview answers separate from event counts. A failed in-store attempt or informal question may be absent from system data.
The ACCC can require businesses to back up claims they make about their products or services. If a promised benefit is repeatedly unavailable under its stated conditions, review the delivery problem and the member-facing claim together.
Pros and Cons of Tracking Benefit Use via System Events
- ProsObjective data on actual usage; supports compliance with ACCC guidelines on transparency in loyalty schemes.
- ConsMay miss informal attempts (e.g., in-store inquiries); absence of system records does not prove no attempt occurred.
Use the result
Review completed uses, failed claims, outstanding entitlements, fulfilment cost and complaints for each benefit. Investigate differences by channel or membership cohort where the records support them.
Benefit use shows whether members received part of the promise; it does not, by itself, show that membership caused additional purchasing. Preserve current entitlements when revising a paid offer.
