> 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/data-sent-through-segment.md). # 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](https://segment.com) 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 {% hint style="info" %} PodPlay follows the [Segment E-commerce spec](https://segment.com/docs/connections/spec/ecommerce/v2/) so purchase data lands in a standard shape that connected tools understand automatically. {% endhint %} **Events PodPlay Sends** These events fire from PodPlay's servers whenever the matching Customer action happens. **Account** * `account_created` — a Customer creates an account * `account_deleted` — a Customer deletes their account **Reservations & Coaching** * `Order Completed` — a Reservation is booked and paid * `reservation_completed` — a Reservation finishes * `first_reservation_completed` — a Customer's very first Reservation finishes * `reservation_checked_in` — a Customer checks in for a Reservation * `coaching_checked_in` — a Customer checks in for a coaching session * `coach_requested` — a Customer requests a coach **Events** * `Order Completed` — a Customer signs up and pays for an Event * `event_checked_in` — a Customer checks in to an Event **Memberships** * `Order Completed` — a Membership is purchased * `membership_added` / `membership_resubscribed` — a Customer starts or restarts a Membership * `membership_upgraded` — a Customer moves to a higher Membership * `membership_downgraded` — a Customer moves to a lower Membership * `membership_plan_switched` — a Customer changes billing plan (for example, monthly to yearly) * `membership_reactivated` — a canceled Membership is reactivated * `membership_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:astoria` * `reservation:{area}` — the Customer booked a Reservation at a location * `event:{area}` — the Customer signed up for an Event at a location * `event:{category}` — the Customer signed up for an Event in a category * `coach:{coach-tier}` — the Customer booked private coaching * `membership:{membership}` — the Customer is enrolled in a Membership * `invite:{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 {% hint style="info" %} PodPlay never sends Customer home addresses through Segment. The **Location** fields refer to the Club location a Customer visited or engaged with, not their mailing address. PodPlay does not store Customer addresses for security reasons. {% endhint %} **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. {% hint style="info" %} PodPlay and PingPod are not affiliated with Segment. Clubs may purchase Segment and connected tools at their discretion. {% 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/data-sent-through-segment.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.