Skip to main content
Question

Passing Google Ads GCLID parameter through Calendly redirect for conversion tracking

  • October 11, 2025
  • 1 reply
  • 266 views
V

Hi everyone,

I’m trying to correctly pass Google Ads GCLID parameters through Calendly to my website’s booking confirmation page, so that conversions can be attributed back to Google Ads in GA4.

Here’s my setup:

  • My Google Ads and GA4 accounts are linked correctly.

  • My website uses Google Tag Manager (GTM) with a GA4 event tag booking_confirmation that fires when the user lands on:
    https://xxxx.de/pages/booking-confirmation

  • Calendly is used for booking consultations, and after a booking I redirect users to that confirmation page using:
    After booking → Redirect to an external site → Redirect URL:
    https://xxxx.de/pages/booking-confirmation

The issue is:
I need to pass the gclid parameter from the original Google Ads click through Calendly to my confirmation page, but Calendly doesn’t accept dynamic parameters like {gclid} in the redirect URL (it shows “Not a valid URL” when I try ?gclid={gclid}).

As a result, my GA4 event tracks bookings, but Google Ads doesn’t register any conversions — everything is classified as “Referral” (Calendly) instead of google / cpc.

 

I also verified that the GA4 tag and triggers work correctly on the confirmation page.

What I’d like to know:

  • Does Calendly provide a way to automatically pass query parameters (like gclid) from the booking link to the redirect URL?

  • Is there a supported method or placeholder to include dynamic parameters (like {gclid}) in the redirect URL field?

  • If not, is there another recommended solution to preserve tracking data from Google Ads through the Calendly booking process?

Any insight from the Calendly team or others who’ve successfully tracked Google Ads conversions through Calendly would be really appreciated!

THANKS!

    1 reply

    Cameron
    Employee
    • Cameron
    • Employee
    • May 28, 2026

    Hi ​@Valeryia58452 - Thanks for reaching out!

    Calendly can pass supported UTM parameters through the booking flow and into your redirect URL, but gclid is not a supported redirect parameter.

    So in your case, Calendly will not automatically carry the raw Google Ads gclid from the original ad click through to the external confirmation page after booking.

    The supported approach here is to capture the gclid on your site before the visitor goes to Calendly, map it into one of the supported UTM fields in the Calendly link, and then read that UTM value back on your confirmation page after booking.

    A common setup would look like this:

    1. Capture the incoming gclid on your landing page.
    2. Append it to the Calendly link as a supported UTM value, such as utm_term.
    3. Enable Pass event details to your redirected page in the event type settings.
    4. Read the returned UTM parameter on your confirmation page and use it in your GA4 / Google Ads tracking setup.

    So while there isn’t native gclid passthrough in the redirect itself, using a supported UTM field is the best workaround available today.

    These two help articles should be the most relevant for setup:

    Let us know if you have any additional questions!

    Enroll in Calendly’s Research Community” style= Need Help? Visit 'Get Help. Give Help.'
    Terms & ConditionsAccessibility statement