Calendly Integration
Sending events from Calendly to Tracklution allows you to track booked appointments and integrate this data with your website’s user sessions. By linking Calendly events to Tracklution, you can gain deeper insights into user behavior, track offline conversions, and optimize your marketing efforts by connecting booking activity to other interactions. This helps you understand how appointments impact your overall conversion funnel and improve your tracking accuracy.
Prerequisites
- Tracklution account
- Calendly account with a paid plan
- Zapier or similar system for sending webhooks from Calendly to Tracklution
How to track Calendly events to Tracklution
- Implement Tracklution tracking script(s) to your website (atleast PageViews). Here's instructions: Install website tracking with Google Tag Manager
- Edit your appointment settings in Calendly: external site redirect to your own page with contact information
- Process is explained in “Redirect invitees after they book": https://help.calendly.com/hc/en-us/articles/14073294601495-How-to-customize-the-event-confirmation-page#h_01JS2BQ9HTTY3TTSV4MDQT03Y9. You need to pass event details (at least email) to the redirect page, as described in step 6.
- Create a Zap:
- Trigger: Calendly: invitee created (or whatever trigger you want to use)
- Action: Zapier WebhooksSetup: POST webhookConfigure:
- URL: https://main.trlution.com/collect/hook?k=LS-98765432-1&track=AppointmentBooked
Change the red part to your own unique endpoint URL and yellow part to an event name you want to use for the Calendly-event. Here's where to find your unique endpoint URL: Send Events From Any Platform With a Webhook - Payload type: json
Test the Zap and see if the event appears in the webhook tab in Tracklution with email & event name correctly parsed;
You should now see the event on the Tracklution container dashboard. If the event is correctly tracked, it should be matched to the website session that happened before the user booked the appointment from Calendly. This can be ensured by finding the event on the session log in the dashboard (below the chart), and checking if the event has a parent session attached to it, like this:
