What's next
By now you've seen what Koala Smartblock is, where it fits in the journey, how it adopts your brand, and how a traveller uses it.
So what’s next? The integration is intentionally lightweight, but there are a couple of practical steps to make it feel properly integrated in your flow.
A quick look: the event system
Koala Smartblock doesn’t operate in isolation. As a traveller interacts with it, it emits events your page can listen for: when the widget is ready, when a bundle is selected or declined, and when the basket changes.
These events let your page stay in sync in real time (update totals, reflect the selection in an order summary, and carry the choice through to booking completion), so the experience remains consistent end‑to‑end.
One more step: creating the subscription
After a booking is confirmed on your side, your application makes one call to Koala. If the traveller selected protection, it creates the policy. If they didn’t, it deletes the quote, so the offer performance can still be measured accurately. Either way, the call is made for every booking that ends with a sale on your side.
The widget prepares the payload for you. Your developers fill in the few fields only your system knows (for example the booking number and customer details) and then send it. This happens after your booking is confirmed, because the booking number is required.
Where to go from here
The next layers of this documentation are for developers:
Together they cover the remaining implementation work needed for a clean integration.