> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/mindbody/how-earning-works.md).

# How earning works

Perkville can use activity and sales data from MINDBODY to automate point earning. The exact earning rules, filters, and point values depend on how your Perkville program is configured.

## Common MINDBODY activities Perkville can reward

Depending on your setup, Perkville can automate earning from MINDBODY records such as:

* **Class and workshop attendance**
* **Appointments**
* **Facility arrivals or check-ins**
* **Retail and service purchases**
* **Purchases filtered by revenue/product category or payment type**
* **Qualifying contract purchases for membership sign-up rewards**

For spend-based rules, Perkville can use the qualifying purchase amount as the activity quantity. For example, a rule can award one point per dollar spent, or use a different point rate defined in Perkville.

If you need to identify MINDBODY revenue categories for a sales rule, see [Finding product categories](https://docs.perkville.com/integrations/integration-reference/mindbody/finding-product-categories.md). If earning depends on contract type, see [Finding contract names](https://docs.perkville.com/integrations/integration-reference/mindbody/finding-contract-names.md).

## Membership sign-ups and tier rewards

* **Membership sign-ups** — Reward qualifying contract purchases using configured contract-sale earning rules.
* **Membership tier rewards / upgrades** — Not supported by the standard MINDBODY member sync, which does not send membership type or original join date. Contract purchases can earn sign-up rewards, but do not supply the current membership-type data required for tier-based upgrade rewards. See [Membership tiers](https://docs.perkville.com/features/earning-rules/membership-tiers.md) for the feature's requirements.

## Attendance, cancellations, and no-shows

Attendance-based earning should be driven by the qualifying attendance record from MINDBODY rather than by the booking alone.

A cancellation or no-show should not count as completed attendance. If a member receives points for an activity they did not attend, compare the attendance status in MINDBODY with the Perkville transaction and contact Perkville Support if they do not match.

## Purchases, unpaid transactions, and refunds

Spend-based earning should use completed qualifying sales rather than unpaid bookings or balances.

Refunds can be handled separately from the original sale and may reverse previously awarded spend points depending on the integration and program configuration. If automatic refund handling is important to your program, confirm the expected behavior with your Perkville representative when the earning rule is configured.

{% hint style="info" %}
Sales rules can also be filtered so that only selected product categories or payment types earn points.
{% endhint %}

## Zero-point activities can still drive bonuses

An underlying earning activity does not need to award base points in order to be useful elsewhere in the program.

For example, a class-attendance rule can award **0 base points** while still recording the attendance activity. That activity can then count toward a [Frequency bonus](https://docs.perkville.com/features/earning-rules/promotions-and-bonus-earnings/frequency-bonus.md), such as “Attend 8 classes this month and earn 100 bonus points.”

This is useful when you want to reward consistency without awarding points for every individual visit.

## Troubleshooting missing or unexpected points

If a MINDBODY activity did not earn the expected points:

1. Confirm the member and activity exist in MINDBODY.
2. Confirm the attendance, payment, or sale status is eligible for the rule.
3. Check that the activity occurred at a location included in the Perkville earning rule.
4. For class or appointment attendance rules, check whether the specific class or service is included in the rule's configured eligibility filters. If your business has excluded certain services or class types, attendance at those activities may not earn points.
5. For sales rules, confirm the product category, payment type, or contract matches the rule's filters.
6. Review the member's Perkville point history to see whether the transaction was received under a different earning rule.
7. If the MINDBODY record looks correct but Perkville does not match it, contact [Perkville Support](https://docs.perkville.com/overview/support.md) with the member, location, activity date, and relevant MINDBODY transaction or visit details.

## Booking and package FAQs

### Can pre-booking points wait until the appointment is attended?

Yes. A pre-booking rule can award points when the customer attends the pre-booked appointment, so a canceled appointment does not earn that attendance-dependent award. Confirm the booking conditions with your CSR.

### Can class points vary by package or membership?

Yes. The class-attendance award can depend on what paid for the class, such as ClassPass, a package or a membership. Share the payment/package categories and intended point amounts with your CSR.

See the [MINDBODY partner profile](https://partners.perkville.com/partners/mindbody).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/integrations/integration-reference/mindbody/how-earning-works.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
