What this integration solves
Calendly is often the conversion. If the embed drops query parameters, CRM meetings arrive as Direct or Calendly with no campaign. Paid social and search then look broken while SDRs are full.
The build passes utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid, gbraid and wbraid into invitee questions or Calendly's UTM passthrough, then into HubSpot via native sync or webhook.
Prerequisites and permissions
Calendly owner access on the event types that sales uses. CRM admin to map custom fields. Landing pages must preserve query parameters into the embed (avoid stripping on redirect).
The build, step by step
1. Enable UTM parameter passthrough on the event type if your Calendly plan exposes it.
2. Add hidden invitee questions for gclid, gbraid, wbraid when passthrough does not cover click IDs. Populate them with on-page JavaScript reading location.search before the widget loads.
3. Map Calendly to HubSpot (or Salesforce) fields one-to-one. Meeting booked should create or update contact and set a meeting_booked_at datetime.
4. Fire a GA4 generate_lead or meeting_booked event on the confirmation page with campaign params still present.
5. Optionally upload meeting_booked as an offline conversion with a modest expected value.
Gotchas
Inline embeds inside SPAs that remount without query strings. Branded Calendly share links that bypass your site. Multiple event types with inconsistent questions. Timezone on meeting start versus booking time for conversion timestamps. GDPR: booking forms still need consent language.
How to verify it is working
Book a test meeting from a URL that includes utm_campaign=test_calendly and a fake gclid=test123. Confirm those values on the Calendly invitee payload and on the CRM contact. Confirm the GA4 event in DebugView.
What breaks it later
New event types created without the hidden questions, theme redesigns that replace the embed, and CRM field API name changes. Quarterly checklist of all active event types.
Identity and capture for Calendly attribution tracking
Attribution dies between marketing embeds and sales signature links. Prefer workspace event types with hidden gclid questions. Round-robin and personal Calendly URLs bypass those embeds. Inventory every live event type quarterly, including one-off webinar links.
Upload contract for Calendly attribution tracking
Map invitee answers into HubSpot write-once utm and gclid properties so later nurture forms cannot blank them. Fire meeting_booked once on the confirmation page. Optional offline upload uses a modest expected value from your value table, not full ACV.
Monitoring for Calendly attribution tracking
After theme or embed redesigns, re-test SPA remounts that drop query strings before widget boot. Mobile browsers need a separate pass. Track bookings missing gclid separately from Ads Accepted volume.
Deep dive: Calendly attribution tracking
Humans must actually send the tracked links. Signature and round-robin shortcuts recreate dark meetings. Treat event-type inventory as a sales ops chore, not a one-time marketing setup.
Operator checklist: calendly-attribution-tracking
1) Workspace event types carry hidden gclid questions. 2) Landing embed preserves query params. 3) Test booking writes CRM fields. 4) Confirmation fires meeting_booked once. 5) Signature links audited. 6) Mobile booking re-tested. 7) Quarterly event-type inventory complete.