The Cloudbeds integration: what Converstay reads, and what it never touches
Converstay works only with Cloudbeds, and connects with a read-only API key, three reservation webhooks and a snippet on the booking engine. Here's exactly what each part does, for the hotel and for whoever looks after your Cloudbeds account.
Updated 16 November 2026
The three parts
- A read-only API key you create in Cloudbeds, with read access to Hotel, Rate, Reservation and Room.
- Three webhooks Converstay subscribes with that key: reservation created, reservation status changed and reservation dates changed.
- A one-line snippet in the booking engine's Custom JavaScript, or in Google Tag Manager, that notices when a guest types their email and leaves.
What Converstay reads from Cloudbeds
Everything it reads is there to make the guest's email exact and to count bookings honestly:
| Cloudbeds data | Why |
|---|---|
| Hotel: name, address, currency, time zone | The sender, the email footer, and prices in your currency |
| Rooms: names and photos | The guest sees the room they chose, with its picture |
| Rates and availability | The current rate for their dates, price-drop alerts, and a sold-out check |
| Reservations: guest email, dates, status, total | Stop emailing guests who booked, and match each booking that came back |
The key can't create, change or cancel anything in Cloudbeds. Converstay never sees card details: payment happens on Cloudbeds' own booking engine, and the snippet doesn't read the payment step.
What the snippet does on the booking engine
The snippet loads Converstay's tracker on your Cloudbeds booking engine. It follows the steps a guest takes, saves the room, dates, rate and language they chose, and saves their email once they type it into the guest details form. Nothing is sent to a guest who never typed an email.
It can also show the optional cards you turn on in the dashboard: your perks for booking direct when a guest heads for another tab, Send My Stay, a note that other guests are looking at the same dates, and other booking links when a date is sold out. Each one is off until you turn it on.
How bookings are matched
When Cloudbeds tells Converstay about a new reservation, it looks for a guest who left the booking engine with the same email at the same hotel. A match stops any emails still waiting, and if Converstay had already emailed that guest, the booking counts as recovered.
Bookings that arrive without an email are matched by hotel, dates and a two-hour window around the time the guest left. Cancellations and date changes come through the other two webhooks, so a cancelled booking stops counting the same day. Bookings made by phone, WhatsApp or at the front desk count too, labelled by channel, when the guest's email matches.
Setting it up
The dashboard walks through it and checks each step. The short version:
- In Cloudbeds, open Account → Apps & Marketplace → API Credentials and create a credential named Converstay.
- Create its API key with R (read) ticked for Hotel, Rate, Reservation and Room, and paste the key into Converstay. The webhooks are subscribed for you.
- Paste the snippet into Booking Engine → Customize → Custom JavaScript, or add it to Google Tag Manager.
- Connect your sending domain and approve the emails when you're happy with them.
The full walkthrough, with the common snags, is in following up on Cloudbeds.
Turning it off
Delete the API key in Cloudbeds and remove the snippet from the booking engine, and Converstay stops reading anything at once. You can ask us to delete your hotel's data at any time, as the privacy policy describes.
Questions
Is Converstay in the Cloudbeds Marketplace?
Not yet. Converstay connects with an API key you create in your own Cloudbeds account, which works on any Cloudbeds plan with API access.
Can Converstay change my reservations or rates?
No. The key is read-only: Hotel, Rate, Reservation and Room. It can't create, change or cancel anything.
Which Cloudbeds webhooks does Converstay use?
Reservation created, reservation status changed and reservation dates changed. They let it stop emails as soon as a guest books and take cancellations out of the count.
Does it work with Cloudbeds Booking Engine Plus?
Yes. The snippet goes into the booking engine's Custom JavaScript, or into Google Tag Manager if your booking engine uses it.