If your product already sends identify and track calls to Segment, Gleap can receive them from there. Same contacts and events as calling the SDK directly — no extra instrumentation.
In Segment, add a Webhook destination pointing at:
https://api.gleap.io/webhooks/segmentAuthenticate it with HTTP Basic auth. The username is your project's identity verification secret; leave the password empty.
You'll find that secret in your project settings, behind Show secret key. It's not the same value as your SDK API key, and the settings page says so explicitly — using the wrong one gives you 401s on every event.
Two call types are handled, and the rest are ignored.
identify — creates or updates the contact for that user id, with the traits you send. Where there's no user id, the anonymous id is used instead.
track — records an event on that contact: the event name, its properties, and the timestamp Segment sent.
Page and screen calls don't come through, so if page views matter to you, the widget already tracks those on its own.
The user id is what ties everything together. Send the same id to Segment as to Gleap.identify — otherwise the same person becomes two contacts, one holding the conversations and one holding the events.
Traits map onto Gleap's contact fields by name, so name, email and phone land where you'd expect and everything else becomes custom data.
Use Segment when your events are already there and you'd rather not add another call to every code path. Use the SDK when you want the widget to react immediately — events routed through Segment arrive slightly later, which matters for a checklist or a message that should fire the moment someone finishes setup.
Doing both is fine, as long as the ids match and you don't send the same event twice under different names.
Segment's event delivery view shows what it sent and what came back. A 401 means the wrong secret; a 200 with nothing visible in Gleap usually means the call type wasn't identify or track.