Chili Piper now allows you to track your meetings using our UTM Tracking feature! This will allow you to automatically track any passed UTMs, and ensure that the booking information, reporting, and CRM are all updated instantly with the correct data.
In this article, we take a closer look at:
UTMs only work within this flow if your CRM is Salesforce.
Setup
This is done via each Meeting Type. When editing a Meeting Type, click the UTM Tracking option and set the appropriate UTMs. Don't forget to toggle "Enable UTM Parameters" to enable it for that specific Meeting Type.
Note, campaign, source, and medium are all mandatory fields and must be included.
If the booking link URL has no UTM parameters, the default values provided above are always going to be taken into consideration while booking a meeting with this Meeting Type.
Tracking
Once a meeting is booked, the parameters you chose in the Meeting Type can be tracked in the Dashboard, and you can apply custom filters for easier viewing/sorting.
These parameters can also be recorded in Salesforce on the Lead or Contact objects.
To track the parameters in Salesforce, you edit this within the Workspace's CRM Actions. Select "UTM Tracking Actions" and define which Salesforce field should be mapped to which UTM parameter.
Once done, we will automatically record these to SFDC when meetings are booked using those parameters.
Custom Parameters on Booking Links
You can pass different UTM parameters to a booking link so that you can track the performance of different platforms or mediums you are using to reach out to your customers.
To make this process easy, you can also retrieve an automatically generated one at the bottom of the UTM Tracking page:
One significant benefit is that you can use the same URL for different campaigns, different mediums, different sources, and so forth to track each differently!
Note: As with the fields above, campaign, source, and medium are required.
For example, if you had a round-robin queue but wanted to pass a different source:
https://yourdomain.chilipiper.com/book/campaign_1?type=meeting&utm_source=twitter&utm_campaign=my-campaign&utm_medium=social-media&utm_term=post
versus -
https://yourdomain.chilipiper.com/book/campaign_1?type=meeting&utm_source=facebook&utm_campaign=my-campaign&utm_medium=social-media&utm_term=post
This is entirely customizable in a way that works for your campaign!
Note: If you define values within the meeting type, any parameters passed through a Booking Link URL will overwrite these "default" values.
Note: If you are using our REST API, you can also pass these UTM parameters directly to the POST request! More info on that here.