Skip to content
English
More support Sign in
Go to patchretention.com
  • There are no suggestions because the search field is empty.

Orders vs heats vs parties — which trigger to use

Goal: Pick the right automation trigger so messages match what actually happened at your track.

ClubSpeed activity shows up in Patch as different types of events. Using the wrong one is the most common reason messages feel off (for example, thanking someone for racing when they only bought a soda).

At a glance

What happened at your venue…

Use this in Patch

Guest paid a closed check (races, F&B, merch, etc.)

Order Finished

A payment was voided / refunded

Order Refunded

Guest finished a heat / race

Checkin Finished

Party or event reservation

Calendar Event

Online race booking / reserved seat

Calendar Event

Membership started or ended

Membership Started / Membership Ended

Profile or credit balance updated on sync

Contact Created / Contact Updated

 

Timing tip: Patch syncs from ClubSpeed about every 6 hours (not real-time). A “thanks for racing” may send later the same day — use quiet hours and short delays in your automations.

 

Orders (closed checks)

Best for: Spend — receipts, reviews after purchase, offers based on what they bought or how much they spent.

Includes: Line items, totals, tax, discount amounts, payment methods.

Good examples

  • Thank-you / review after purchase
  • Buyers of a specific race package or product
  • Win-back for high spenders who went quiet

Not ideal for: “They raced today.” Someone can race without a new check in that window, or buy without racing.

 

Heats / check-ins (finished races)

Best for: Racing activity — they finished a heat.

Includes: Finished heats only (not “added to lineup but not finished”). Heat type when available.

Good examples

  • Post-race follow-up
  • Win-back when they haven’t raced in a while
  • Milestone messages (visit / race counts)

Not ideal for: Party reminders or pure spend offers — use Calendar or Order instead.

 

Parties & online bookings (calendar)

Best for: Something scheduled — birthday parties, group events, or online-booked race times.

ClubSpeed can send two kinds of bookings into Patch as calendar items:

  1. Event / party reservations
  2. Online bookings (only if you use ClubSpeed online booking)

Canceled or expired holds will delete the Calendar Event in Patch.

 

Good examples

  • Reminder before the party
  • Day-of upsell (extra races, food)
  • After-event thank you / rebook / review

Not ideal for: Counting every walk-up race day — many heats never become a party reservation.

 

Simple decision guide

  1. Message about money spent? → Order Finished / Refunded
  2. Message about racing a heat? → Checkin Finished
  3. Message about a booked party or online slot? → Calendar Event
  4. Message about member status? → Membership Started / Ended
  5. Message about birthday, profile, or credit balance? → Contact Created / Updated