Overview
This article will outline the flow and mapped fields of the contacts that are synced from Core into the Grow platform at a HQ level.
Below is all of the fields included in the Grow sync at a HQ Level
Field Name: The name of the field as it appears in Grow.
Definition: Description of what the field contains.
Field Name | Definition | ||
---|---|---|---|
First Name |
|
||
Last Name |
|
||
Contact’s e-mail | |||
Phone | Contact’s phone number | ||
Date Of Birth | Contact’s birthday | ||
Contact Source | Reserved to Opportunities | ||
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 | Contact’s Do Not Disturb option for SMS | ||
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, across the locations | ||
Past Active Packages | Every package ever registered for the Contact that is not currently active | ||
Active Package |
|
||
Active Package Category |
|
||
Join Date | Oldest date the contact has joined a brand’s location | ||
Intro Offer |
|
||
Corporate Status | Contact’s status on corporate level | ||
Anniversary | Number of years since the Join Date | ||
Corporate Absent | (Milestone) Smallest number of Days Absent on any synced location for the Contact | ||
Corporate Inactive | (Milestone) Smallest number of Days Inactive on any synced location for the Contact | ||
Home Location | Contact’s home location(s) | ||
Corporate Attendance | Number of times a contact has checked-in to every location of the brand | ||
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 throughout the sites a Contact attends to. | ||
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 |
Differences between the Core to Grow Sync: Location VS HQ Level
Corporate Inactive field is included in HQ Level sync while Days Absent & Days Inactive fields are included in Location Level sync.
There are several fields included in Location Level that is not included at HQ Level. Please see our Location: Core to Grow Sync article for information on the fields included at a location level.
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.