Chargebee

Chargebee works like the other billing integrations: nothing leaves Gleap, and the customer's subscription picture appears next to the ticket you're answering.

Connect it

Add Chargebee from Integrations and give it two things: your Chargebee site and an API key.

The site is the name in your Chargebee URL — the acme in acme.chargebee.com. If you run a test site alongside a live one, make sure you've taken the key from the same site you named.

A read-only key is enough. Gleap only reads customers, subscriptions and invoices — it never writes to Chargebee.

How a contact is matched

If the contact carries chargebeeCustomerId as custom data, that customer is used. Otherwise Gleap searches Chargebee by the contact's email address.

Gleap.identify("user-123", {
  email: "[email protected]",
  customData: { chargebeeCustomerId: "16BdBpSAaFTZ4dc" },
});

There's no domain-level fallback here, so the email has to match. In B2B, where the person writing in often isn't the billing contact, sending the customer id is the difference between the panel working and staying empty.

What you see

The customer, their subscriptions and their invoices — enough to answer “what am I paying for” and “did my last invoice go through” without leaving the ticket.

When nothing shows

Check, in this order: the contact has an email address; that address exists on a Chargebee customer; the site name is right; the key belongs to that site. Wrong site with a valid key is the quiet one — everything looks configured and nothing ever matches.