Booking embeds: inline, pop-up or floating badge
On this page
Which booking embed belongs on your website?
Choose Inline when the page exists mainly for booking, a pop-up when booking follows some explanation, or a floating badge when the action should stay available as visitors browse. All four use one booking flow. Your meeting rules stay attached to the event.
| Feature | Inline | Popup button | Popup text link | Floating badge |
|---|---|---|---|---|
| Where the entry sits | Inside page layout | Button in your content | Link in your content | Floating page corner |
| Booking form appears | On page load | After a click | After a click | After a click |
| A good starting use | Dedicated booking page | Consultation offer | Sentence or navigation | Persistent booking action |
Inline occupies space in the layout immediately. The other modes wait for a click before opening the booking dialog; pick one of those if a full calendar would interrupt the page's main content.
What can I change without building a booking interface?
The embed builder controls theme, accent color, hidden details and guest pre-fill, while the event editor controls questions and meeting rules. We start the builder in Inline mode with Theme set to auto and parent UTM copying enabled, so check those defaults before generating your snippet. You can change those choices before copying. You don't need a custom form.
| Option | Use it when |
|---|---|
| Theme | The booking frame should follow light/dark preferences or use a fixed theme |
| Hide event details | The surrounding page already explains the meeting |
| Name, email and answer pre-fill | You already know some guest details |
| Pass parent UTM parameters | Website campaign tags should travel with the booking |
We pass UTM fields only when that option is on. Insights explains the attribution you can inspect, including the difference between stored campaign fields and the "Top UTM sources" panel.
Choose a mode, then copy its generated code
Open an event's "Embed & share" section to use the Embed builder and preview. Copying its output gives you the options you selected, including the event URL and display mode. Use the installation guide for the steps on your website. Start with the preview.
- Select the event and open "Embed & share".
- Choose "Mode", "Theme" and any pre-fill or display options.
- Add your website's origin under Settings, "API & webhooks", "Allowed origins".
- Copy the generated code and test it on the published website.
The website embed installation guide handles the platform instructions. If a frame is refused, check the allowed origin, including its protocol and any www prefix; it must match the website where the booking frame is used.
When is the booking API a better choice than an embed?
Use the API when your application needs its own date picker or booking form; keep the embed when you want our guest interface inside your site. We keep conflict checks and approval rules in the booking system, so changing the presentation doesn't remove them. Build only what you need.
The API and webhook overview explains keys and booking notifications. Embeds are included without an extra plan; see the current fair-use policy and prepare your website's booking event.
Frequently asked questions
Will my embed grow when the booking form gets longer?
Yes. The inline embed adjusts its height as the booking view changes. Resize messages are accepted only from the matching iframe and origin, so an unrelated frame on the page can't set the booking frame's height. Test the longest form in the actual website layout, because showing the calendar alone doesn't establish that every later field remains visible.
Why are my website campaign tags missing from bookings?
Check Pass parent UTM parameters in the embed builder and recopy the generated code if needed. The option must be enabled, and the parent page must contain the tags. A booking without those inputs won't acquire a campaign source automatically.
Can I pre-fill the form for a returning client?
Yes. The embed supports a guest name, email and question-answer pre-fill. Guests still complete and submit the booking form; pre-filling doesn't reserve a time or bypass required answers, calendar checks or approval rules. Check that pre-filled details still belong to the intended guest and avoid exposing private client information in a publicly shared URL.
Related pages
- How to embed a booking calendar on your website
Embed a booking calendar with generated HTML or React code. Choose inline, pop-up or badge mode and check optional allowed-origin restrictions.
- Booking API and webhooks for your own application
Build with REST, OpenAPI and signed webhooks. Browser keys require allowed origins; server keys stay private. Default API access is 600 requests/minute.
- Booking insights: sources, attendance and record exports
See booking counts, page conversion and Top UTM sources. The heatmap uses meeting starts; Export CSV downloads booking records, not dashboard totals.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link