Analytics v2 — Expanded Event Tracking

What shipped

Analytics v2 is a full rebuild of how NomadMD emits events to your marketing stack. Every meaningful moment in the customer journey — request created, appointment confirmed, order paid, membership renewed — is now a first-class event keyed to the booking account.

What changed from the legacy integration

• New identity model: events are keyed to the booking account (mu_/cp_ IDs), not per-patient email. That means multi-patient households and group appointments show up as one customer, not many.
• Wider event coverage: orders, appointments, memberships, and package redemptions all now emit dedicated lifecycle events with typed properties.
• Provider & ops events: internal lifecycle events (dispatch, staff actions) are keyed separately from customer events, so your marketing dashboards stay clean.

Where it goes

Segment v2 and Google Tag Manager both consume the new payload out of the box. If you use another destination, the schema reference in Integrations & Developer Tools shows exactly what to expect on the wire.

Migration path

The legacy Segment integration keeps working until you switch it off. When you're ready, follow the Migrating from the Legacy Segment Integration to Segment v2 guide to move over.