> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/marketing/marketing-integrations/growmyclub.md). # GrowMyClub ### Overview GrowMyClub is an all-in-one CRM and marketing platform (powered by JOOLA) built for racquet and paddle Clubs. It reads your PodPlay data directly and turns it into a single, segmentable profile per Customer for contact management, a sales and lifecycle pipeline, email and SMS marketing, automation, broadcasts and campaigns, and engagement and retention reporting. Data syncs from PodPlay to GrowMyClub automatically every 15 minutes, so contacts, Memberships, Reservations, and revenue stay current without anyone lifting a finger. On first connect, GrowMyClub backfills your full PodPlay history, then keeps it up to date from that point on. There is no daily "Import" button to click. ### How the integration works The connection is read-based and secure. GrowMyClub pulls your data out of PodPlay over PodPlay's API, so your Club never has to export spreadsheets or push anything manually. Because the integration only reads from PodPlay, it can't change or delete anything in your PodPlay account. The one exception is marketing opt-outs, covered below. #### What your Club provides To connect, give your GrowMyClub onboarding contact two things: * **PodPlay Subdomain** — the "your-club" part of `https://your-club.podplay.app` * **PodPlay API Key** The GrowMyClub team enters these into their system (the API key is encrypted at rest), validates the connection, and your Club's data immediately begins backfilling and then syncing every 15 minutes. ### What data flows from PodPlay into GrowMyClub Every PodPlay Customer becomes a GrowMyClub contact and is tagged as a Member. Existing contacts in GrowMyClub are automatically matched to their PodPlay record by email, then phone, then name, so you don't end up with duplicates. | Data | What it includes | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Customers | Name, email, phone, birthday, gender, and DUPR / skill ratings. | | Memberships | Plan name, status (active / paused / cancelled), start and end dates, and price. Powers a live "paying Members" view of your base. | | Reservations | Court Reservations, including Club, date, and time. | | Events & Clinics | Event and series sign-ups, including Club and Coach. | | Private coaching | Lessons, including the Coach who taught them. | | Orders & purchases | Every transaction, its line items, and the amount actually paid, rolled up into each Customer's Lifetime Value. | | Check-ins & attendance | Who showed up, at which Club, with which Coach. Guests count toward attendance without cluttering a Member's history. | | Promo & coupon codes | The Promo Code used on an order, so you can target Customers by promotion. | | Upcoming Reservations | Each Customer's next scheduled visit. | | Marketing preferences | Email and SMS marketing opt-in status. | ### What lights up once you're connected With PodPlay data flowing in, these features come to life automatically: * **Unified contact profiles** — one record per Customer with their Memberships, Reservations, spend, ratings, and full activity timeline. * **Lifecycle pipeline** — Customers are automatically sorted into stages like New, Active Customer, and Past Customer based on their real PodPlay activity. * **Lifetime Value (LTV)** — total revenue per Customer, computed from what they actually paid across Reservations, Events, coaching, and retail. * **Membership tracking** — see paying vs. non-paying Members at a glance, and get notified when someone starts or ends a paid Membership. * **Marketing automation** — trigger email/SMS journeys off real events: a new Member joins, a Customer's first Reservation, a win-back when someone lapses, a birthday, and more. * **Broadcasts & campaigns** — send targeted email and SMS to any segment you can define. * **Engagement & retention reporting** — dashboards including retention by Coach, so you can see which Coaches keep Customers coming back. * **Powerful segmentation** — filter and target by Club, Event, Coach, Membership plan, Promo Code, spend, rating, and more. For example, you can build a segment of Members who booked at a specific Club in the last 30 days but have no upcoming Reservation, and send them a one-tap rebooking offer, entirely from PodPlay data, with no manual list-building. ### Most common use cases These are the ways Clubs use the connection most, day to day. Every one runs on PodPlay data that's already syncing, with no lists to build: * **Welcome new Members** — the moment someone joins in PodPlay, they get a friendly welcome series by email or text: how to book, what's happening this month, and who to ask for help. * **Win back lapsed Customers** — when a regular hasn't checked in for 30, 60, or 90 days, GrowMyClub automatically sends a "we miss you" message with a reason to come back, before they're gone for good. * **Turn first-timers into regulars** — after a Customer's first Reservation or Clinic, follow up automatically with a thank-you and the natural next step: an intro program, a Membership, or their next booking. * **Fill Events and Clinics** — promote your next Event to everyone who attended a similar one, plays at the right skill level, or takes lessons with that Coach. * **Nudge the next booking** — Customers who visited recently but have no upcoming Reservation get an automatic reminder to grab their next court time. * **Save Memberships and spot upgrades** — get notified the moment a Membership is cancelled or paused so you can reach out personally, and find frequent Customers who aren't on a paid plan yet, your best upgrade prospects. * **Celebrate birthdays** — an automatic birthday greeting with a small offer, using the birthday PodPlay already has on file. * **Reach exactly the right list** — send newsletters and announcements to precisely who should get them: one Club, one Membership plan, one skill band, or everyone who redeemed a Promo Code. Every one of these can be switched on during onboarding. Tell your GrowMyClub contact which ones you want and they'll be live from week one. ### Marketing opt-outs stay in sync GrowMyClub respects your Customers' marketing preferences and keeps them consistent across both systems. This is the one place where information flows both ways: * **From PodPlay → GrowMyClub:** opt-in / opt-out preferences set in PodPlay are pulled into GrowMyClub. * **From GrowMyClub → PodPlay:** when a Customer unsubscribes from an email, replies STOP to a text, or is opted out inside GrowMyClub, that opt-out is pushed back to PodPlay so the two systems agree. {% hint style="warning" %} Opt-outs are always honored and never silently reversed. Because PodPlay doesn't collect SMS consent at signup, new contacts start opted out of SMS by default until they opt in. {% endhint %} ### Sync cadence & data direction * **Direction:** one-way pull (PodPlay → GrowMyClub), with the single exception of marketing opt-outs, which sync both ways. * **Frequency:** every 15 minutes, automatically. * **History:** on first connect, your full PodPlay history is backfilled, then kept current. {% hint style="info" %} A note on security: * Your PodPlay API Key is stored encrypted and is only decrypted at the moment of a sync. * GrowMyClub does not store payment card data or Customer home addresses. * The integration is read-only against PodPlay apart from the marketing opt-out sync described above. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/marketing/marketing-integrations/growmyclub.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.