Data Sent Through Segment
Overview
This is the complete reference for the customer data PodPlay routes through Segment. Use it when a Club asks what information leaves PodPlay, when building marketing segments and automations in a connected tool (such as ActiveCampaign or Mailchimp), or when checking whether a specific action is being tracked.
What Is Segment?
Segment is a customer data platform (CDP). PodPlay sends customer activity to Segment once, and Segment forwards it to every marketing, analytics, and advertising tool the Club has connected. This means you configure the data one time and reuse it everywhere.
PodPlay sends three kinds of information through Segment:
Events — something a Customer did (created an account, completed an order, checked in)
Identify traits — who the Customer is (name, email, membership, ratings)
Tags — behavioral and location labels used for building segments
Events PodPlay Sends
These events fire from PodPlay's servers whenever the matching Customer action happens.
Account
account_created— a Customer creates an accountaccount_deleted— a Customer deletes their account
Reservations & Coaching
Order Completed— a Reservation is booked and paidreservation_completed— a Reservation finishesfirst_reservation_completed— a Customer's very first Reservation finishesreservation_checked_in— a Customer checks in for a Reservationcoaching_checked_in— a Customer checks in for a coaching sessioncoach_requested— a Customer requests a coach
Events
Order Completed— a Customer signs up and pays for an Eventevent_checked_in— a Customer checks in to an Event
Memberships
Order Completed— a Membership is purchasedmembership_added/membership_resubscribed— a Customer starts or restarts a Membershipmembership_upgraded— a Customer moves to a higher Membershipmembership_downgraded— a Customer moves to a lower Membershipmembership_plan_switched— a Customer changes billing plan (for example, monthly to yearly)membership_reactivated— a canceled Membership is reactivatedmembership_canceled— a Membership is canceled
Marketing
marketing_preferences_updated— a Customer changes their email or SMS marketing opt-in
The Club's app and website also send activity as the Customer moves through the checkout flow, including Product Added, Product Removed, Checkout Started, Order Updated, reservation_cancelled, event_cancelled, and the invite events (invite_button_tapped, invite_accepted, invite_declined, invite_link_tapped).
Purchase Details on Order Events
Every Order Completed event carries the full purchase breakdown so connected tools can report on revenue and target buyers:
Order ID
Total, subtotal, and revenue
Tax
Currency
Discount and coupon code (when a coupon was used)
Product list — each product includes a name, an SKU, a price, a quantity, and a category (Booking, Coach Booking, Membership subscription, Event, or Invitation)
The SKU is a coded label you can match on when building segments. Use Contains to target by location, event type, or coaching:
Booking —
[pod]-[location]-[region]Coach Booking —
[coach tier]-[pod]-[location]-[region]Event —
[Event/Series]-[location]-[region]Membership —
[membership name]-[charge type]-[membership type]
Identify Traits
These describe who the Customer is and update whenever the Customer's details change:
Email
First name
Last name
Phone
Gender
Birthday
Location(s) the Customer is connected to
Membership name, start date, and end date
Virtual credits balance
Replay credits balance
Skill ratings (singles and doubles)
Coach tier (when the Customer books coaching)
Email marketing opt-in
SMS marketing opt-in
Membership Change Details
When a Customer changes their Membership, PodPlay also sends the before-and-after so you can build automations around upgrades, downgrades, and plan switches:
Previous Membership, previous billing type, and previous locations
New Membership, new billing type, and new locations
Effective date of the change
Dynamic Tags
Tags are behavioral and location labels PodPlay attaches to a Customer so you can group and target them. A brand-new Customer with no activity yet will not have behavioral tags.
location:{region}:{area}— the Customer took any action at a location. Example:location:new-york:astoriareservation:{area}— the Customer booked a Reservation at a locationevent:{area}— the Customer signed up for an Event at a locationevent:{category}— the Customer signed up for an Event in a categorycoach:{coach-tier}— the Customer booked private coachingmembership:{membership}— the Customer is enrolled in a Membershipinvite:{area}— the Customer accepted an invite to a location
Channel Context
Every event is labeled with the channel it came from, so you can tell where a Customer action originated:
Web — the Customer acted on the website
iOS / Android — the Customer acted in the mobile app
Front desk — staff acted on the Customer's behalf at a facility
Server — the action was completed automatically by PodPlay
What Staff Should Know
This data flows automatically once an integration is connected — there is nothing to send manually.
Duplicate protection is built in for account and order events, so a Customer will not be double-counted if an action is retried.
To connect a destination such as ActiveCampaign or Mailchimp, see the guides in Marketing Integrations, or contact your PodPlay CSM.
Last updated
Was this helpful?

