OrcLink
← Help Center

Forms

Calendly

Count a Calendly booking in its embed as a conversion.

Built, not yet tested liveBuilt. Not yet tested against a live Calendly account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

  • Capture > Rules > Iframe form vendors: tick Calendly. Keep the OrcLink script on the page that shows the embed.

What OrcLink reads

  • Only the vendor's "submitted" message, and only from Calendly's own addresses. No answers, no ids.

What OrcLink writes back

  • Nothing.

Never stored

  • Form answers: never read.

Known limits

  • The message format is written from the vendor's public documentation and not yet checked on a live embed: check with Capture > Test tool.

How to count Calendly submissions as conversions in OrcLink. Tested against a copy of Calendly's form markup and submit behaviour (app/api/capture/__tests__/fixtures/builders/calendly.html, test app/api/capture/__tests__/tjs/builders.test.ts). Limits of that test: it is a copy of the markup and of the submit flow as documented, not the live builder; no Shadow DOM; the builder re-rendering the form is not modelled. Check your own page with the test tool.

Set up

  1. Add the OrcLink script to the page that shows the Calendly embed (Conversions > Install). You do not need the script inside the Calendly form.
  2. In Capture > Rules, under Iframe form vendors, turn on Calendly.
  3. Publish.

The script listens for Calendly's own "calendly.event_scheduled" message, accepted only from https://calendly.com. It reads only that signal: no field of the form, no answer, no id. It then records one appointment conversion for the visitor's click (olid).

Other paths for Calendly:

  • Redirect to your own thank-you page after the submit, and add a thank-you page rule (Capture > Rules) for it. Map URL parameters to order_id or email only if Calendly adds them; an email or phone parameter is removed from the address at once.
  • If you can put the OrcLink script inside the form page itself (some plans allow custom code), it captures like any form on your site and gets the click id from the page around it (the frame handshake).

Notes

  • Calendly records an appointment conversion (not a form) when a visitor books.
  • The invitee's name, email and answers stay with Calendly. To tie the booking to a person later, send it from your server (Conversions API) with the same email; OrcLink joins it by hashed email.

Check it

  1. Open Capture > Test tool in OrcLink and turn test mode on (or add data-orc-test to the script tag on a test copy of the page).
  2. Open the page from an OrcLink link (so the address has ?olid=), fill in the form and send it.
  3. Within a few seconds the test tool shows one row: kind, the field NAMES read and hashed (email, phone), match "click id", outcome "Yes". It never shows values.
  4. Turn test mode off. Test outcomes are never sent to an ad platform.

Privacy

  • The script reads only the first email-shaped and the first phone-shaped field of the form. Names, messages, dates of birth, insurance and every other field stay in the page. The server hashes the email and phone on arrival and never stores them raw.
  • Nothing is read or sent before the visitor gives advertising consent (when the workspace follows the consent manager). In HIPAA mode the same rules hold; hashes only.