Roller and Patch Integration Overview

Key capabilities of the Roller and Patch integration

Keep a unified, marketing-ready guest database synced from Roller into Patch, including contacts, bookings, and memberships.
Run guest lifecycle journeys such as new guest welcomes, birthday and party follow ups, post-visit review requests, and win-back campaigns using Roller activity as the trigger.
Time reminders, upsells, and thank you messages around actual bookings and visits so communication lands at the right moment.
Communicate across email, SMS, and TextChat where enabled, with history tied back to a single guest record in Patch.
Optionally recover lost revenue with abandoned cart follow ups when that part of the integration is enabled for your account.

Note: This article is a high-level overview. For step-by-step setup instructions, see your dedicated integration setup article in the help center or work directly with your Patch onboarding specialist.

What data syncs from Roller to Patch

Once the integration is connected, Roller becomes the source of truth for guest, booking, and membership activity. Patch keeps in sync by listening to Roller events and running periodic safety checks.

Contacts

Patch creates or updates a contact record whenever Roller provides enough information (for example, an email address or phone number). Typical contact fields that sync include:

First name and last name
Email address
Mobile phone number
Date of birth
Address details (when available)
Roller contact ID
Date the contact was created
Marketing consent status (based on opt-in captured in Roller)
Guardian / minor relationships when waivers or bookings include families

This gives you a clean, marketing-ready contact list in Patch that stays aligned with what you see in Roller.

Orders and bookings

Patch receives order / booking events from Roller so you can:

Target guests based on what they purchased (memberships, passes, parties, food & beverage, merchandise, etc.).
Trigger follow-ups and review requests after visits.
Build win-back campaigns for guests who haven’t booked again.

Key order details that sync typically include:

Order total
Discount amount and net subtotal
Products or packages in the order
Timestamps for when the order was completed

Only orders tied to a contact (with an email or phone number) are useful for marketing, so those are the ones Patch focuses on.

Calendar events (sessions, parties, passes)

Session- and event-based data from Roller - such as party packages, session passes, and other bookable experiences, are surfaced in Patch’s calendar so you can:

Send pre-visit reminders
Run during-visit campaigns (for example, upsell concessions)
Trigger post-visit review and win-back flows

You can think of Roller as the system that knows when someone is coming; Patch is the system that knows how to communicate with them around that visit.

Memberships

Membership data from Roller feeds into the Memberships area of each contact in Patch. This allows you to:

Welcome new members with a dedicated onboarding series.
Notify members before their membership is due to expire.
Run offers to convert non-members into members.

Typical membership fields available for automation include things like membership type and membership start / end dates (exact fields depend on your current integration setup).

Abandoned cart (optional)

For customers who enable abandoned cart tracking through Roller and Google Tag Manager, Patch can:

Capture guests who started, but did not complete, a booking.
Trigger an automated reminder campaign (email and/or SMS) encouraging them to finish checkout.

Because this requires additional configuration on the Roller side (Tag Manager, events, etc.), the details live in a separate “Roller Abandoned Cart” article. Your Patch onboarding specialist can confirm whether this is enabled for your account.

Getting started with the integration

At a high level, the integration set up process works like this:

Your Patch team connects Roller to Patch.
1. During onboarding, your Patch onboarding specialist helps you collect the Roller API credentials (Client ID, Client Secret, etc.) and enables the Roller integration add-on in your Patch account.
Patch authenticates and sets up sync + webhooks.
1. Behind the scenes, Patch uses your credentials to authenticate with Roller, configure webhooks for real-time events, and run an initial data pull from a defined start date.
Contacts, bookings, and memberships start flowing into Patch.
1. As guests book online, visit, and renew, Roller keeps sending events to Patch. Patch uses those events to continually update your contact list, calendar, and membership data.
You send your first Blast
1. Working with your Patch onboarding specialist, you build and send your first Blast from Patch to your Roller guests, confirming everything is connected and ready for ongoing campaigns.
You enable recommended automations and campaigns.
1. Your onboarding specialist typically starts you with a core set of pre-built Roller automations (welcome, birthdays, reviews, win-backs, etc.), which you can customize over time.
You measure retention and revenue lift in Patch.
1. Over time, Patch helps you see how many guests are at risk, lost, or loyal, and how your Roller-powered campaigns are influencing repeat visits and spend.

Throughout this process, you do not need to manage the technical integration day-to-day. If you ever suspect data is not syncing correctly (for example, new bookings are not appearing in Patch), contact Patch Support or your CSM rather than attempting to recreate webhooks or change integration settings yourself.

Key benefits for Roller customers

1. A unified, marketing-ready guest database

Instead of exporting lists from Roller every time you want to run a campaign, the integration keeps your Patch contact list in sync with Roller. You can:

Filter guests by visit history, membership status, birthday, spend, and more.
Segment guests into buckets like New, Promising, Loyal, At-Risk, and Lost using Patch’s RFM (Recency, Frequency, Monetary) model.
Quickly see which guests are worth investing in and which segments need attention.

2. Automated journeys around the full guest lifecycle

Because Roller events drive Patch automations, you can set up “always-on” journeys that run in the background, such as:

New guest welcome – A short series that thanks first-time visitors and introduces your brand.
Birthday journeys – Timed offers leading up to a guest’s birthday, helping you book more parties (with the ability to exclude minors where required).
Membership journeys – Welcome and nurture flows for new members, plus reminders around upcoming expirations.
Review and feedback flows – Automatically ask for Google reviews after a successful visit.
Win-back campaigns – Target at-risk or lost guests with tailored offers to bring them back.

Once enabled, these journeys continue to run as new Roller data comes in—your team only needs to tweak messaging or offers as your strategy evolves.

3. Better timing and personalization

Because Patch sees real booking and visit behavior from Roller, you can time messages around moments that matter:

Hours or days before a visit (reminders, upsell offers, what-to-expect messages)
Shortly after a visit (thank-you, review requests, bounce-back offers)
Weeks or months after the last visit (win-back or membership offers)

You can also personalize messages using Roller data such as:

Location visited
Product or package type (e.g., party vs. open play)
Membership vs. non-membership status

4. Consistent communication across email and SMS

The same Roller events that drive email can also drive SMS. With Patch, you can:

Use TextChat for two-way texting from your website and sync those conversations to contacts.
Send email + SMS versions of key campaigns (like birthdays or win-backs).
Keep all communication history tied to the underlying guest record.

Recommended starter automations for Roller + Patch

Every venue is different, but most Roller + Patch customers start with a similar baseline set of automations:

New guest welcome series
Triggered when a contact makes their first booking. Introduces your brand, what to expect, and encourages a second visit.

New member welcome
Triggered when a new membership starts. Covers benefits, how to get the most value, and any member-only perks.

Birthday campaigns
Triggered based on birthday dates from Roller. Sends an offer leading up to the birthday and a reminder close to the date (with logic to exclude minors when needed).

Post-visit review request
Triggered after a completed booking or check-in. Thanks the guest and asks them to leave a Google review, using SmartLinks or similar tools to drive them to the right place.

At-risk / lost win-back
Triggered when a guest hasn’t visited in a defined window (for example, 90+ days). Offers a compelling reason to return.

Non-member membership upsell
Targets frequent visitors without a membership and invites them to upgrade.

Abandoned cart (optional)
For customers who enable the abandoned cart integration, sends reminders to guests who started but did not complete a booking online.

Your Patch onboarding specialist can enable a recommended set of these flows for you and customize the wording, timing, and offers based on your venue’s strategy.

What you need before you go live

From your side, you’ll typically need:

An active Roller account with admin access (or a contact at Roller who can create API keys).
An active Patch account with the Roller integration included in your agreement.
Someone on your team who can confirm:
- Which locations should be connected.
- Which core automations you want to start with.
- Any constraints (for example, rules around messaging minors).

From Patch’s side, your team will:

Coordinate with Roller (if needed) to confirm API access is available.
Configure the integration in your Patch account and test that data is flowing correctly.
Turn on a small set of pre-approved automations and review the content with you before launch.
Help you interpret early results and adjust your strategy.

FAQs

Do my guests ever see Patch?

No. Guests interact with your brand, not Patch. They see emails, texts, and forms that use your venue’s name and branding. Patch runs in the background as the engine powering those communications.

How often does data sync between Roller and Patch?

The integration is designed to send events from Roller to Patch in near real time using webhooks, with periodic safety checks to catch anything that might have been missed. In practice, you can expect new bookings and contacts to appear in Patch shortly after they happen in Roller.

Can I choose which locations or data sync?

Yes. During onboarding, your Patch team can scope which Roller locations are connected and confirm which kinds of data (for example, specific product types or experiences) you want to drive automations from.

What if I think the integration isn’t working correctly?

If you notice that new Roller contacts, bookings, or memberships are not appearing in Patch as expected:

Check whether the guest actually completed the booking and provided an email or phone number in Roller.
If data is still missing, contact Patch Support at success@patchretention.com your Customer Success Manager and mention that you’re using the Roller integration.

Avoid deleting or recreating integration settings or webhooks yourself - your Patch team can safely diagnose and resolve any issues.