Gleap's documentation is split in two, and knowing which half you're in saves a lot of searching.
This help center — what the product does and how to set it up from the dashboard.
docs.gleap.io — the SDKs and APIs: every method, its arguments, and installation per platform.
The rule of thumb: if the answer is a line of code, it's in the developer docs.
Two sections. Documentation holds the SDKs, one set of pages per platform: JavaScript, iOS, Android, React Native, Flutter, FlutterFlow, Ionic / Capacitor, Cordova, plus Windows Desktop, .NET MAUI and Unity in beta. Alongside them are server-side event tracking and a handful of guides.
The API Reference is the other section — the REST endpoints, for backends that talk to Gleap directly.
Every platform has roughly the same set, so once you know the JavaScript page names you can find the iOS ones. The recurring ones:
User identity — identifying contacts, and verifying that identity with a hash.
Events and Custom data — what you send about a person and what they did.
Widget control and workflows — opening, closing and driving the messenger from your code.
Console logs, Network logs, Replays — the debug data attached to a report.
Suppressing personal data — masking what shouldn't be captured.
Environment — keeping staging out of your production inbox.
Content security policy — what to allow if your site runs a strict CSP.
The JavaScript SDK has the most surface — AI chat bar, tours, checklists, surveys and UI components each have a page — because the web is where most of that shipped first.
The fastest route isn't the docs at all: the installation screen in your project generates the snippet with your API key already in it, per platform. Use that to install, and the docs for everything after.
