UTM tracking for embedded scheduling links

Previously, when clients embedded their NeetoCal scheduling link within their website and promoted that website URL through ad campaigns (such as Google Ads, Meta Ads, or Instagram Ads), there was no way to identify which ad platform the booking originated from.

Even though NeetoCal already supported UTM parameter tracking, that only worked when users shared the direct NeetoCal link (for example: neetocal.com/s/john?utm_source=googleads).

In embedded cases, such as when a NeetoCal scheduling page was embedded to a website landing page like advantageinvestment.co.uk/book-demo, those UTM parameters weren’t being passed into the embedded iframe.

As a result, all bookings appeared identical, and marketing teams couldn’t distinguish between bookings from Google Ads, Instagram, or any other campaign.

What we fixed

NeetoCal can now capture and store UTM parameters even when the scheduling link is embedded inside another website.

When a visitor lands on a webpage that includes a NeetoCal embed, any UTM parameters for example: utm_sourcein the page URL, are automatically passed into the embedded NeetoCal scheduling page.

This means:

• If someone visits advantageinvestment.co.uk/book-demo?utm_source=googleads and books a meeting, NeetoCal will record that the booking came from Google Ads.

• Similarly, a booking from ?utm_source=instagram will show up with Instagram as the campaign source.

These captured parameters are visible in:

• The booking details are viewed inside NeetoCal.

• Google Sheets exports, if integration is enabled.

Why this matters

With this enhancement, marketing teams running multi-platform campaigns can now:

• Attribute each booking to its true campaign source.

• Analyze ad performance directly from NeetoCal data.

• Understand which channels bring the most qualified leads, without changing how they embed scheduling page.

To learn how to use this, refer to this help article.