Cal.com on your landing pages
When the offer is a consultation, a demo or an in-home estimate, the booking is the conversion that matters, and the form is only the way in. The gap between the two is where leads drop: a second form to fill, a link in an email, a rep's voicemail.
Cal.com's embed snippet sits on a LanderLab page in the editor's Custom Code element, usually on the thank-you page the form sends the lead to. LanderLab can carry the lead's answers to that page in its URL, and Cal.com can forward the page's URL parameters into the booking form by itself. Name, email and UTMs arrive with no code written to read them.
Cal.com booking right after the form
Cal.com offers three ways to embed an event type: inline, where the calendar is part of the page; a pop-up opened by clicking an element, like your CTA button; and a floating button. Inline on the thank-you page is the one that turns form fills into bookings, because there's nothing left to click but a time.
You can embed a single event type, your whole profile, or a Cal.com Routing Form that sends each lead to the right person's calendar.
Prefill without a line of parsing code
LanderLab can send the lead's answers on to the thank-you page in its URL, and Cal.com's embed can forward the page's URL parameters into its booking form, an option you switch on in the embed, so name and email arrive filled in.
Auto-forwarding passes every parameter on the page, so keep anything sensitive out of your URLs, as Cal.com itself advises. The email also sits in the thank-you page's URL, where any pixel on that page can see it; check your ad platforms' rules or prefill the name only.
Campaign and click ID on every Cal.com booking
Cal.com tracks the five standard UTMs on bookings automatically. For anything else, like a gclid, an fbclid or a tracker's click ID, a hidden booking question named after the parameter stores the value with the booking.
Only the hosts of a booking see its UTMs and hidden answers, so the attribution data stays with your team, not with the person who booked.
Optimize on bookings, not form fills
The embed fires bookingSuccessfulV2 when a new booking is made. Fire your pixel's Schedule event from it and your ad platform hears about the outcome that matters. If your event type requires confirmation, remember the event fires when the booking is made, which can be before it's confirmed.
