How embedding works
Embedding has three parts. First, the host's meeting account must allow it: usually by creating a small developer app inside that same account and switching on the embedding feature. Second, the website needs a secure way to prove to the meeting platform that each guest is allowed in, which is done with a signature generated on the server using the app's keys. Third, the page loads the platform's embedding code, which draws the meeting inside the page and connects the guest's camera and microphone through the browser.
To the guest, it simply looks like the meeting appearing on your site. Behind the scenes, the video still runs on your meeting platform and counts against your licence.
What embedding makes possible
Once the meeting lives on your page, the page can do things a plain meeting link cannot:
- Carry your logo, colours and navigation around the meeting.
- Ask guests for a name and email before they enter.
- Hold guests in a branded lobby until the host is ready, then start for everyone at once.
- Show offers, resources or forms beside the meeting.
- Play effects such as confetti or applause over the meeting for everyone on the page.
- Send guests to a follow-up when the meeting ends.
The limits to know
Embedding is not a new meeting service. Capacity is still your licence's participant limit. The meeting's own recording captures the meeting, not anything your page adds on top of it. Some advanced meeting features may behave differently, or be unavailable, inside an embedded view compared with the desktop app. Browsers also ask each guest for camera and microphone permission the first time, so a short line on the page explaining that helps.
Guests who prefer the desktop app can still join the regular way, but they will see only the meeting, not your page around it.
Build it or use a product
Building your own embedded meeting page is entirely possible. It involves the developer app, server code to generate signatures securely, the front-end integration, handling errors such as an invalid signature or a meeting that has not started, and keeping all of it working as the platform updates its toolkit. For a company with engineers and a specific product need, building can make sense.
For most hosts who simply want their meetings on their own page, a ready-made room is faster. BrandedRooms connects to the meeting account you already use and gives you an embedded meeting inside a branded page, with a waiting room, Start the room and guest capture on every plan. The Generic Room adds the standard effects pack and the attendee list, and a Branded Room adds your own branding, your domain, the offers rail, integrations and follow-up funnels.
Getting a first embedded meeting running
If you use BrandedRooms, the setup guide walks through it in order: create the developer app in the account that hosts your meetings, switch on embedding, activate the app, copy its keys into your room settings, add your meeting and its passcode, set capacity and then test on a second device as a guest. The most common first-time errors have their own help pages with the fix.