Forms & Bookings: Recap And Verify

5 questions. Answer all of them, then submit; you need 4 of 5 to pass.

1. 1. Why does GTM's built-in Form Submission trigger miss a Calendly or Typeform embed?

   Embedded forms submit over websockets, which GTM cannot seeThe widget lives in an iframe, so the submission never happens in your page's DOM where the trigger listensThe trigger only supports forms with an id attributeThose vendors block GTM by user agent
2. 2. Which event marks the actual booking conversion when you listen to Calendly's postMessages?

   calendly_profile_page_viewed, when the widget loadscalendly_date_and_time_selected, when a slot is pickedcalendly_event_scheduled, when the meeting is actually bookedcalendly_widget_closed, when the visitor is done
3. 3. How does your listener recognize a completed Typeform submission?

   Typeform posts a message with type form-submit, which the listener turns into a typeform_submitted dataLayer pushTypeform sets a cookie named tf_submittedTypeform redirects the parent page to /thanksTypeform fires a native submit event that bubbles out of the iframe
4. 4. HubSpot forms render on your page, yet the built-in form trigger is still unreliable for them. What is the dependable hook?

   A Just Links trigger on the submit buttonAn Element Visibility trigger on the thank-you textPolling the form's DOM for a success classHubSpot's hsFormCallback message with eventName onFormSubmitted, pushed to the dataLayer by a listener
5. 5. After Calendly, Typeform and HubSpot, a fourth embedded widget arrives with its own postMessage events. What changes in your approach?

   You need a new trigger type from the template galleryOnly the listener and the event name: translate the widget's signal into a dataLayer push, then trigger and tag as usualNothing can be reused; every vendor needs a bespoke tag typeYou must move the widget out of its iframe first