Holds the calendar date of the most recent qualifying service or purchase activity the connector read from the connected system. The value is refreshed on each successful sync when newer activity is found for a contact.

Holds a short text label for how a contact is classified in the import pipeline, such as lead compared with customer, when the integration supplies or derives that. The text reflects the latest sync; older labels are not kept as history in this field alone.

Holds the amount associated with the single most recent service or purchase line the connector selected for a contact. The underlying source can be an invoice, order, job, or payment, depending on which objects the connected product exposes.

Holds the stable person or company identifier from the system you connected. CRM Connector and GoHighLevel use it to recognize the same record on the next run and to avoid creating duplicates by mistake.

Holds the name or code of the job or work order’s current stage when the source application tracks a pipeline. The field is left blank for integrations that do not expose work-order or project stage fields.

Holds the stage the job or work order was in immediately before the last recorded change, when the source provides that value. It is meant for workflows where you need to see movement between stages, not a full audit log.

Holds the date on which the job or work order stage was last changed, when the source supplies a change date. If the API only provides a point-in-time stage without history, this field may remain empty even when a current stage exists.

Names which product or system last wrote sync data for a contact in locations that can run more than one integration. It is a connector routing label in GoHighLevel, separate from the external record identifier stored in External Contact ID.

Holds a numeric total of completed revenue that the integration attributes to a contact using its own counting rules. What counts as one line item, currency handling, and time window are defined by the integration, not a single hard-coded rule in the UI.

Holds how many completed transactions the integration included when it computed the lifetime total for a contact. The number and the lifetime money field are intended to be consistent with the same rules on each sync.

Holds a plain-language email marketing state such as Subscribed or Unsubscribed, based on an opt-in or opt-out signal when one exists. The value is written as text in GoHighLevel so it is visible in automations and compliance review without reading raw boolean flags from code.

Holds the earliest calendar date of qualifying service or purchase activity the connector found in the history it loads. It can be later than the day a contact record was created if the first real transaction came after signup.

Holds a short summary such as point balance or tier when the connected system exposes a loyalty or rewards program and the sync requests it. If the product has no program or the sync does not include loyalty, the field may stay empty while other sync fields still update.

Holds a single extra value that your sub-account can map to one additional GoHighLevel custom field when the integration is built to support that passthrough. The meaning and format are defined by the integration and your field mapping, not by a fixed name in the connector list.