Skip to main content
All CollectionsStaff & AdminsStaff & Admins | GrowFAQs
Grow | What Information Comes From Core
Grow | What Information Comes From Core

Data & information is being sent from Core to the Grow CRM. As the system is continuously being upgraded, it's important to know the data is

Updated over a year ago

The PushPress Core & Grow CRM are connected through an API connection. This API is continuously being built and improved upon to deliver gym owners with a kick ass product to not only make your life as a gym owner easier, but to improve the client and lead journey.

Below is a list of current information that Core is sending over to the Grow CRM. Each of these data points and tags can be used to trigger workflows and automated messaging!

Note: this list will be continuously updated as new features are released. Also note, that at this time, Grow does not send information to Core. This is something we are working on, and when it is available this document will be updated

TAGS

HOW/WHY/INTENTION

Lead

From plans sold in core with 'Lead' designation

Member

From plans sold in core with 'Member' designation

Non-member

From plans sold in core with 'Non Member' designation

Ex-Member

When a client no longer has a valid plan on their profile in core.

Paused

When a client's membership is paused in Core

Recent Check In

This tag is sent every time a client checks into class (used for at risk workflow)

First Class Reserved

This tag is sent when a client/lead reserves their first ever class and can be used to trigger trial workflows based on reserving but not checking in

First Class Attended

This tag is sent when a client/lead checks into their first ever class and can be used to trigger trial workflows based on checking in

DATA

HOW/WHY/INTENTION

Pause Date

When a plan is paused in core, the pause date will be sent to Grow and applied to the contact record

Resume Date

When a plan is paused in core, the resume date will be sent to Grow and applied to the contact record

First Reservation Coach

The coach name who is assigned to the client's first class will be sent to Grow (used for first class messaging)

First Reservation Class Name

The name of the class for the client's first class will be sent to Grow (used for first class messaging)

First Reservation Class Date

The class reservation date for the client's first class will be sent to Grow (used for first class messaging)

First Reservation Class Time

The time of the client's first class will be sent to Grow (used for first class messaging)

Last checkin coach name

The coach name who was assigned to the client's last check in class will be sent to Grow (used for first class messaging)

Total Check-ins

total number of check ins will be updated every time a client checks into class. Can be used for milestones etc

Last Check-in date

The date of the client's last check in will be sent to Grow

Plan Category

The plan category name that the client's plan is associated with is sent to Grow. This can trigger workflows based on the type of plan sold from Core

Plan Name

The plan name that the client's plan is sent to Grow. This can trigger workflows based on the name of plan sold from Core

Nickname

If a client is assigned a nickname in Core, this nickname will be sent to Grow. This can be used for messaging if a client prefers to be called by their nickname in messaging. This will make it seem more personal in messaging.

Did this answer your question?