Contacts and tags do not sync to GoHighLevel merely because you have a Levr account. Sync depends on the connection configured for your Portal, the permissions granted to it, and the fields and direction mapped in that integration.

Levr provides a live REST API and webhooks. The current API includes people, businesses, deals and pipeline operations, and webhooks include deal.stage_changed. These platform capabilities do not establish that a specific GoHighLevel connector has implemented contact tags, deal stages or two-way sync.

Confirm which system sends the update, which system receives it, the mapped fields, how matching record IDs are stored, and which Portal the API key belongs to. Then use a non-sensitive test record to check creation and one update in the destination. An API key alone is not proof that records are syncing.

There is no universal sync-time guarantee. It depends on your connector, webhook processing or polling schedule, and retries. If an update is missing, check delivery errors and mapping first. Webhook events may be delivered more than once or out of order, so a custom receiver must deduplicate events and read current record state before applying changes.

A Portal administrator can manage API keys under Settings → Connections → API. For an existing assisted integration or a missing field, ask support to check the configured connector. Share the CRM name, the affected record reference, approximate time and a redacted error. Never send API keys, webhook signing secrets or client financial documents in chat.

It takes nothing to get started. Start here, or use one of these.