It looks like this link is inactive but I’d be happy to take a look at this with you. When using the same parameters on an account I wasn’t able to reproduce. Check out this link: https://calendly.com/schedulingurl2?utm_medium=social&utm_source=facebook&utm_campaign=summer%20promotion&salesforce_uuid=ffeddb07-041a-4df0-9f22-999c6c7a0740&name=Fredy%20Haag&email=fredyU.haag%40autotest.com

Do you have a link we can see and test? 

The most likely reason the utm_ parameters are being stripped while the salesforce_uuid remains is due to how Calendly handles the redirect from your custom link to the actual scheduling page.

Calendly is designed to preserve certain parameters, often those related to integrations or unique identifiers like the salesforce_uuid, but it frequently has rules that exclude or strip common tracking parameters like utm_ for a cleaner URL, especially upon a server-side redirect.

To prevent the removal of the utm_ parameters, you would typically need to ensure they are explicitly allowed or whitelisted by Calendly to pass through the redirect, but this is often not possible within their standard configuration, and it's a common behavior when one domain redirects to another.

A more robust and modern approach, especially if you're looking to accurately track conversions and tie them back to your campaign data, involves using a server-side solution that captures the data before the redirect and sends it directly to the intended destinations.

Instead of relying solely on the browser's URL parameters that can be stripped or blocked, you would use the Calendly API to get the conversion event data, the Salesforce API to match that conversion to the salesforce_uuid, the Facebook Conversions API to send the conversion event like Purchase or Lead along with the salesforce_uuid and the utm_ data, and the Google Analytics Data API to ensure your custom data is accurately logged.

These APIs are best managed through a server-side tagging solution like Google Tag Manager and a tool like Stape or Google Cloud Platform.

This setup allows you to send richer, more reliable data directly from your server to Facebook and Google, bypassing the browser's limitations, like ad blockers or the URL stripping you're currently experiencing.

This server-side method is far superior for accurate attribution, as it ensures your campaign data, including the utm_ parameters, is correctly associated with the conversion and sent through without relying on the browser to maintain the parameters during a redirect.