# Diverge Docs

> Everything needed to integrate the Diverge chatbot, track chatbot analytics, and work against the chatbot API.

## Docs

- [Chatbot Analytics](/guides/chatbot-analytics): This document covers the analytics events emitted by the chatbot script and how to consume them in
your own tracking setup, for example Google Tag Manager.
- [Chatbot API Errors](/guides/chatbot-api-errors): The chatbot API has two error channels:
- [Chatbot API Flow](/guides/chatbot-api-flow): This guide explains how the public chatbot API fits together from an integrator's point of view.
It focuses on the flow and data model so you can build a client without guessing how responses
should be interpreted.
- [Chatbot Config & Theming](/guides/chatbot-config): `GET /api/v1/chat/config` returns the public UI configuration for the chatbot tied to the
visitor token. Fetch it after `POST /api/v1/chat/auth` and before rendering the first chat
screen. The response contains display identity, fully resolved theme values, livechat controls,
URL-triggered popup messages, and dynamic form references.
- [Chatbot Integration](/guides/chatbot-integration): The standard Diverge chatbot is a **floating widget**: a launcher on your site that opens a chat
window over the page. This guide is the starting point — load the script, open the chat, optionally
attach session metadata.
- [Conversation Export](/guides/conversation-export): The chatbot analytics events give you the front-end side of a chatbot session. This guide covers the
other half: pulling the conversations themselves — the stored rating, topic, and where they were
escalated to — into your own data warehouse, so chatbot journeys can be joined with traffic, order,
and helpdesk data on your side.
- [Intercom Livechat](/guides/intercom-livechat): Use the Intercom integration when you want human livechat requests from Diverge to become
conversations in Intercom.
- [Orders API](/guides/orders-api): Stores that are not on a platform Diverge connects to directly send their orders through the
Orders API. Your backend sends the whole current order every time it changes; your checkout
copies one opaque value, the **visitor stamp**, into each order.
- [Product Feed](/guides/product-feed): A product feed gives Diverge the catalogue information it needs to answer product questions and recommend the right products. In most cases, the same feed you already use for Google Shopping is a good starting point.
- [UI Embeddings](/guides/ui-embeddings): Use these layouts when the standard [floating widget](/guides/chatbot-integration) is not the
right fit. Click a picture to jump to its setup.
- [Universal API Integration](/guides/universal-api-integration): Universal API Integration lets Diverge **call your HTTP endpoints** during a conversation — for
example to look up order status, delivery times, or account details — and use the response in the
assistant's reply.