> 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/abc-glofox/setting-up-and-launching-perkville-with-glofox.md).

# Setting up and launching Perkville with Glofox

This guide covers launching Perkville across one or more Glofox branches.

## Launch checklist

Use these steps for one or more branches after arranging your Glofox API access with your Perkville Customer Success Representative (CSR). Your CSR will confirm any configuration handled by Perkville or Middle.

| Step                            | Business responsibility                                                                              | Perkville / integration check                                                                                                           |
| ------------------------------- | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Identify branches**           | Provide each Glofox Branch ID and the corresponding business location                                | Confirm the participating branches are whitelisted and mapped to the right Perkville locations                                          |
| **Choose earning activities**   | Decide whether qualifying visits, attended bookings, sales, or membership actions should earn points | Verify that the relevant Glofox events are available and map to the configured Perkville earning rules                                  |
| **Set up referrals**            | Choose the referral offer and the activity required to complete a referral                           | Confirm whether referral-lead delivery into Glofox has been separately configured; lead delivery does **not** itself award the referrer |
| **Configure challenges**        | Set requirements, participation dates, rewards, and manual or automatic enrollment                   | Verify that each qualifying activity arrives in Perkville and counts toward challenge progress                                          |
| **Test before launch**          | Test representative members at each branch, including a referral and a challenge activity            | Compare Glofox records against Perkville profiles and correct any location or member matching issues                                    |
| **Make the program accessible** | Coordinate a link to your hosted Perkville program in Glofox's Community section if desired          | A Community link is **not** the same as a native embedded loyalty application or automatic single sign-on                               |

For general feature setup, see [Earning rules](https://docs.perkville.com/features/earning-rules.md), [Configuring referrals](https://docs.perkville.com/features/referrals/configuring-your-referral-program.md), and [Challenges](https://docs.perkville.com/features/challenges.md).

### FAQ

**Does a Glofox referral lead automatically complete the referral?** No such assumption should be made. Delivering a prospect to a sales system and earning the Perkville referral reward are distinct workflows. The latter depends on the tracked Perkville referral and a qualifying completion activity.

**Can we run a Bingo challenge?** Check the current availability of the specific Bingo challenge design with your CSR. Standard challenges can track configured requirements, but this guide does not establish that a Bingo-style grid is supported in every account.

**Can we configure everything ourselves?** Businesses can design their loyalty rules and campaigns in Perkville, but Glofox whitelisting, field mapping, and some cross-system workflows require coordination with Perkville.


---

# 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/abc-glofox/setting-up-and-launching-perkville-with-glofox.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.
