> 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/myzone.md).

# MyZone

Convert Myzone Effort Points (MEPs) into Perkville points.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

* **Workout effort** — Award points for MEPs earned in a workout using your configured conversion.
* **Rounding** — The documented conversion rounds down per workout; leftover MEPs do not accumulate across sessions.
* **Locations** — Authorize and connect each participating facility separately.

Your configured rules determine which eligible activities award points and which workflows are enabled.

## I**ntegration Steps – Connecting MyZone to Perkville**

#### **Step 1: Authorize Perkville Access**

To begin the integration process, you'll need to authorize Perkville to access your MyZone business data.

* Email your **Perkville Customer Success Representative** the following information:
  * Your **customer name**
  * Your **facility ID(s)** and **facility name(s)**\
    *(Example: MZUK001 – MYZONE UK)*

Perkville will submit this request to MyZone on your behalf to enable the integration.

***

#### **Step 2: Accept MyZone Terms & Conditions**

Once the connection is enabled, Perkville will be notified to allow you to complete the next set of steps:

* Log in to [**moves.myzone.org**](https://moves.myzone.org)
* Navigate to:\
  **Facility Profile → Edit Your Profile**
* Review and accept the **Terms & Conditions** to activate the connection.

> ⚠️ **Important:** If you have multiple locations (each with its own Facility ID), you must complete this step **for each location** individually. Otherwise, points will not sync correctly.

***

#### **Step 3: Set Up the MEPs Earning Activity in Perkville**

Before connecting MyZone to Perkville, a **custom earning activity** must be created for MEPs.

1. Go to your **Rewards Program** page in Perkville.
2. Click the **“+”** icon next to *Earning Activities* and select **“Custom”**.
3. Create a title for the activity (e.g., 25 *MEPs Earned*) and assign a point value.
   * **Recommended Conversion:** 25 MEPs = 1 point
   * On average, a workout earns \~130 MEPs, which equals 5 points.

> 💡 **Note:**

* Points are **rounded down** (e.g., 49 MEPs = 1 point)
* MEPs are **not cumulative** across sessions—they’re only counted per workout.

***

#### **Step 4: Connect the Integration in Perkville**

1. Go to the **Integration** page via the **My Business** dropdown in Perkville.
2. For each location you’d like to integrate:
   * Select **MYZONE** from the dropdown
   * Click **Connect**
   * Enter the location’s **Facility Code** (each location must have its own unique code)
   * Click **Submit**
3. You’ll be taken to the integration edit page:
   * From the dropdown, choose the **MEPs** earning activity you created earlier
   * Enter the **MEP-to-point ratio** (must match the value entered in the activity setup)
   * Click **Connect** to finalize

## FAQ

### Do leftover MEPs carry into the next workout?

No. With the documented 25-MEPs-per-point example, 49 MEPs earns 1 point; the remainder does not carry forward.

See the [MyZone partner profile](https://partners.perkville.com/partners/myzone) for additional integration information.


---

# 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/myzone.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.
