Integrations / Calendly
Calendly logo
Scheduling

LeadLotus + Calendly

Attribute every Calendly booking back to its source.

Calendly's inline embed accepts URL prefill and UTM-style parameters. Install the snippet and tag the embed with data-leadlotus-iframe — LeadLotus rewrites the embed URL with attribution data, which Calendly carries through to the event.

Calendly is hosted — LeadLotus uses the iframe-rewrite path (data-leadlotus-iframe).
1
Install the snippet
Add to your site head as usual.
<!-- LeadLotus Attribution Snippet -->
<script async
  src="https://www.leadlotus.com/snippet.js?key=YOUR_API_KEY"
  data-key="YOUR_API_KEY"
  data-endpoint="https://www.leadlotus.com/api/v1/ingest">
</script>
2
Tag the Calendly embed
Add the data-leadlotus-iframe attribute to your Calendly embed div or iframe. LeadLotus appends UTM-style attribution parameters to the embed URL on page load.
<div
  class="calendly-inline-widget"
  data-leadlotus-iframe
  data-url="https://calendly.com/your-handle/30min">
</div>
<script src="https://assets.calendly.com/assets/external/widget.js" async></script>
3
Read attribution off the booking
Calendly captures URL parameters as "tracking parameters" on each event. Configure them in Calendly → Account → Tracking Parameters or read them via the Calendly API/webhook. Forward to your CRM via Calendly's native HubSpot, Salesforce, or Zapier integrations.

Attribution fields

LeadLotus writes these hidden field values just before your form submits.

Field nameExample valueDescription
leadlotus-channelOrganic SearchTop-level channel (Organic Search, Paid Social, Direct, Referral, etc.)
leadlotus-drilldown1GoogleChannel-specific source (search engine, social network, or utm_source)
leadlotus-drilldown2spring_launchutm_campaign on paid traffic, referring host on organic
leadlotus-drilldown3pricing_keywordutm_term — keyword or ad term, when present
leadlotus-drilldown4hero_ctautm_content — ad variant or placement, when present
leadlotus-landing-url/pricingFirst landing page of the visitor
leadlotus-first-visit2026-04-24Date of the first visit (ISO)
leadlotus-visits3Total sessions before conversion