Fix · salesforce · cal_com

Cal.com → Salesforce routing without losing UTM context

Cal.com's native Salesforce sync overwrites Lead Source on every booking, wiping your first-touch attribution. Here's the workaround that preserves the original UTM bundle.

salesforcecal_com

The problem

What's actually broken

Cal.com's Salesforce integration writes Lead.Source = "Cal.com" on every BOOKING_CREATED event. This is a hard overwrite — your first-touch UTM (paid-social, organic-search, etc.) is gone. The fix is a 2-line custom field that captures the original source before Cal.com touches it.

FAQ

Frequently asked

Why doesn't Cal.com offer a config flag?+

It's on their backlog but not prioritised. Their assumption is that the booking is the canonical lead source.

Can I use a Salesforce Process Builder?+

Yes, but Process Builder is being deprecated. We recommend Flow Builder for new deployments.

Need help?

We've fixed this exact problem dozens of times.

Book a 15-minute scoping call and we'll tell you whether your case fits the standard pattern or needs a custom approach.

Book a call