Locations and Multi-Site Brands
How studios are identified and named, renames, and adding locations as you grow.
Multi-location brands are the reason CRMConnect exists. This page explains how studios are identified, how they are named in Klaviyo, and what happens when you rename or add one.
How Mindbody identifies a studio
Mindbody identifies every studio by a pair of numbers: a Site ID for the business or franchise region, and a Location ID within that site. Every appointment, sale, and visit record carries those numbers. Numbers are fine for an API; they are useless in an email.
The location naming table
CRMConnect maintains a naming table for your account. A settings pass reads your locations from the Mindbody API and writes one entry per location, pairing the site and location id with the studio's display name:
| Mindbody identity | Name used everywhere in Klaviyo |
|---|---|
| Site 722422, location 1 | APIANT Wellness - Doylestown |
| Site 722422, location 2 | APIANT Wellness - Philadelphia |
| Site 722422, location 98 | Online Store |
| Site -5589000, location 1 | APIANT Wellness - Chicago |
(The table above is from APIANT's demo account; yours contains your studios.)
Records with a blank or zero location id fall back to the site's primary studio name, so nothing ever arrives unnamed.
What this gives you in practice
- Every location-bearing property shows the studio name: home studio, last visited, last purchase location, upcoming appointment location. Segments and email personalization read naturally: "your studio: SweatHouz Back Bay", never "location 3".
- One Klaviyo account for the whole brand. Each Mindbody site feeds the same shared Klaviyo account, and locations stay delineated by name. A brand with 100+ studios does not need 100 Klaviyo logins.
- Members who visit multiple studios keep a full trail. The visited-locations list accumulates every studio a member has used, instead of each visit overwriting the last.
- A per-location marketing package. Segments for each studio (members of, visited, upcoming appointment at, no upcoming appointment, purchased at, service taken) and a per-location welcome flow are generated from the same table, so studio #107 gets the same treatment as studio #1 on day one.
Renaming a studio
Rename the location in Mindbody, then tell APIANT (or wait for the next scheduled refresh). The naming table is refreshed and audience definitions that reference the old name are re-pointed as part of the managed change. Historical events keep the name that was current when they happened, which preserves accurate history; profile properties and segments move to the new name.
Adding a location or a new site
- A new location inside an existing site is picked up by a settings refresh: it gets its name in the table and its per-location package on request.
- A brand-new site (a new region or franchise entity) is connected once by APIANT, named by the same settings pass, and inherits the full pipeline into your shared Klaviyo account. Adding your next city is a connection and a settings run, not a project.