AutoSync Custom Fields
Custom Fields
This embedded spreadsheet shows the most current list of custom fields for each platform:
Note: The original naming convention had each variable begin with "MB". Now that we support additional integrations beyond Mindbody the new convention is to start each variable name with the symbol "⇌". If you started with the original variable names we will continue to support the old naming convention and additional locations will continue to use the old naming convention.
⇌ Start Date
The date the client account was created in Mindbody
⇌ Last Purchase
Holds the name of the last item of any type purchased through Mindbody. Very useful as a trigger in workflows
⇌ Last Purchase Value
The value of the last item purchased in MB
⇌ Service Purchase Total
Cumulative purchase total for services in Mindbody - calculated starting when MBSync integration is activated
⇌ Contract Purchase Total
Cumulative purchase total for contracts in Mindbody - calculated starting when MBSync integration is activated
⇌ Contract End Date
End date of most recent active contract
⇌ Pricing Option
Most recent active pricing option/plan
⇌ Pricing Duration
Duration that the current pricing option or plan will be valid
⇌ Pricing Start Date
Start date of current pricing option or plan
⇌ Pricing End Date
End date of current pricing option or plan
⇌ Pricing Visits Available
Number of visits available when purchased
⇌ Pricing Remaining Visits
Number of visits remaining on this pricing option
⇌ Product Purchase Total
Cumulative purchase total for products in Mindbody - calculated starting when MBSync integration is activated.
⇌ Combined Purchase Total
Cumulative combined total of all purchases in Mindbody of all types (service, contract, product) - calculated starting when MBSync integration is activated.
⇌ Lifetime Value
Lifetime total for all purchases in software - calculated from the beginning of client record in Mindbody
⇌ Mindbody Site ID
Site ID in Mindbody account. This is available as a custom value as well but there are rare use cases where a studio might have more than one mindbody account using a single CRM account; in that scenario you should use mindbody_site_id to identify which location each client belongs to.
⇌ Mindbody ID
Client ID in Mindbody account
⇌ Booker Site ID
Site ID in Booker account. This is available as a custom value as well but there are rare use cases where a studio might have more than one booker account using a single CRM account; in that scenario you should use Booker Site Id to identify which location each client belongs to.
⇌ Booker ID
Client ID in Booker account
⇌ Link
Direct link to client record in software
⇌ Waiver
Tracks whether contact signed the Mindbody standard waiver. If it is “signed” in Mindbody this field will be populated with the date the waiver was signed
⇌ Class Count
Cumulative total of all completed classes in software. Useful for gamification or rewards based on number of completed classes
⇌ Appt Count
Cumulative total of all completed appointments in software. Useful for gamification or rewards based on number of completed appointments
⇌ Last Class/Appt Booked
The name of the most recent class or appointment booked in software. Can be useful if you need to reference the name in a GHL message. Keep in mind that it may not necessarily be the next class or appointment if the client booked multiple classes or appointments at the same time
⇌ Client Type
This will reflect whether the client is a Prospect or a Member. There is also a special type New Member which will be set on the first day when a client becomes a member, or possibly longer if the membership type is configured with a pricing option that does not begin until the first class is attended; in that situation it will show New Member until the client completes their first class. There is no default. If it is unclear which type the field will remain blank.
Note: You can update mb_client_type for all MBO clients by running the sync-client-status command
⇌ Client Status
Anytime a client record is created or updated in MB please update the GHL "MB Client Status" field to match. It should be one of these values:
Non-Member
Active
Suspended
Terminated
Declined (Mindbody only)
Expired (Mindbody only)
Note: You can update mb_client_status all MBO clients by running the sync-client-status command
⇌ Status End Date
If client status is changed to suspended and an end date is assigned (typically this would be if they put a "vacation hold" on their account for some period of time, i.e. 2 weeks) the date will be populated in this field
⇌ Trial Name
If contact signs up for a trial the name of the most recent trial purchased will show here
⇌ Trial Duration
Displays the number of days in the trial that the client purchased
⇌ Trial Start Date
The date the trial will start. This accounts for the trial configuration whether you set it to begin when they purchase or begin at the date of their first booked appointment.
⇌ Trial End Date
The date the trial will end
⇌ Trial Visits Remaining
The number of visits that are still available on this Trial (pricing option). Note - if it was set up for “Unlimited” you will see a very high number in this field.
⇌ Home Studio
Name of client’s preferred location
⇌ Home Studio Address
Address of client's preferred home studio
⇌ Last Visit Date
Date of the client’s last appointment or class completed.
⇌ Visit Total
Number of visits (class or appointment) completed in total
⇌ Visit 30 Days
Number of visits (class or appointment) completed in past 30 days
⇌ Contract Name
Name of client’s current contract
⇌ Prospect Stage
If your Mindbody account includes Prospect Stages it will show the current prospect stage in this field
⇌ Referrer
Name of person who referred this contact
⇌ Referree
Name of person who this client referred
⇌ Referral Type
The referral type as recorded in the Mindbody dropdown "referral type"⇌
⇌ Related Client ID
The client ID for a related account, if applicable. This could be a parent to a client client account, or a friend who referred the client, etc.
⇌ Gender
Gender of client. Useful for segmenting your audience.
⇌ Emergency Contact Name
Name of emergency contact
⇌ Emergency Contact Relationship
Relationship of emergency contact to client
⇌ Emergency Contact Phone
Phone number of emergency contact
⇌ Emergency Contact Email
Email of emergency contact
⇌ Allow Permissions
Determines what types of communications are allowed on the platform
⇌ UTM Source
Sets the attribute tracking value utm_source in a custom field that MBSync uses for reporting
⇌ UTM Medium
Sets the attribute tracking value utm_medium in a custom field that MBSync uses for reporting
⇌ UTM Campaign
Sets the attribute tracking value utm_campaign in a custom field that MBSync uses for reporting
⇌ UTM Content
Sets the attribute tracking value utm_content in a custom field that MBSync uses for reporting
Notes
This is not technically a custom field, but we weren't sure where else to include this 😉 When a client log or note is added in Mindbody it will create a new note in GHL in the standard notes area for that contact.