Overview
This article will outline the flow and mapped fields of the contacts that are synced from Core into the Grow platform at a site or location level.
Please note: See our HQ: Core to Grow Sync article for information on the fields included at a HQ level.
Below is all of the fields included in the Grow sync at a Location Level
Field Name: The name of the field as it appears in Grow.
Definition: Description of what the field contains.
Below is all of the fields included in the Grow sync at a Location Level:
Field Name | Definition | ||
---|---|---|---|
First Name | Contact’s first name | ||
Last Name | Contact’s last name | ||
Contact’s e-mail | |||
Phone | Contact’s phone number | ||
Date Of Birth | Contact’s birthday | ||
Contact Source | Reserved to Opportunities OR The origin or method through which a contact was added to the system. | ||
Contact Type | Type of the contact | ||
Street Address | Contact’s street address | ||
City | Contact’s city | ||
State | Contact’s state | ||
Country | Contact’s country | ||
Postal Code | Contact’s postal code | ||
DND Text Messages |
|
||
DND Emails | Contact’s Do Not Disturb option for E-mail | ||
DND all channels | Contact’s general Do Not Disturb option | ||
Core Status | Contact’s status, according to the location | ||
Past Active Packages | Every package ever registered for the Contact that is not currently active for the location | ||
Active Package | Every currently active package from the Contact for the location | ||
Active Package Category | Every package category from the contact’s currently active packages for the location | ||
Join Date | Date the contact has joined the location | ||
First Attendance Date | Contact’s first visit date to the location | ||
Intro Offer | Marks if the contact has already claimed the intro offer to the location | ||
Corporate Status | Contact’s status on corporate level. | ||
Anniversary | Number of years since the Join Date | ||
Days Absent |
|
||
Days Inactive |
(Milestone) Number of days since:
|
||
Late Cancel Accrual |
|
||
No Show Accrual | (Milestone) Number of times the contact was absent due to No Show since the last attendance date in the location | ||
Late Cancel No Show Accrual |
|
||
Home Location | Contact’s home location(s), based on the corresponding active packages. | ||
Attendance Total | Number of times a contact has checked-in to the location | ||
Corporate Attendance | Number of times a contact has checked-in to every location of the brand | ||
Location Status |
Contact’s status on location level |
||
First Booking | Contact’s flag to indicate if any booking was already registered, based on the First Booking Date | ||
First Booking Status |
Contact’s flag to indicate if any booking was already registered |
||
First Booking Date |
|
||
First Session Date | The first time the contact successfully attended to a session in the location | ||
Promo Codes Used | List of every coupon code the contact has ever used in the location | ||
Referrals | Number of times the contact was referred by other clients of the same location | ||
Core Source | Through which medium the contact met the brand | ||
Email Opt In | Contact’s opt in/out for email | ||
SMS Opt In | Contact’s opt in/out for SMS | ||
Tags | Contact’s tags managed by grow-sync service for the location |
Differences between the Core to Grow Sync: Location VS HQ Level
Fields that Appear in Location Level and not HQ Level
- First Attendance Date
- Attendance total
- Location status
- First Booking Date
- Promo Codes
- Referrals
- Late Cancel Accrual, No Show Accrual & Late Cancel No Show Accrual
Days Absent & Days Inactive fields are included in Location Level sync while Corporate Inactive field ia included in HQ Level sync.
Multi-location setup in a single Grow account
Hapana does not recommend managing multiple locations under a single GROW subaccount. There are several limitations including:
- Leads don’t have a listed “Home Location” unless they’ve purchased
- All leads feed into one big pipeline
- You lose access to detailed location-level fields
- You’ll need to duplicate custom values per location
- Only one Meta and one Google account can connect
- One phone number and email domain associated with all automations
Please see our Challenges with multi-location setup in a single Grow account article for more information.