Skip to main content
KoalendarMeeting & appointment schedulers

Conversion tracking for Koalendar, built on the redirect

Koalendar's help center is explicit that custom Google Analytics and GTM scripts are not supported on the booking page, and that tracking belongs on the page you redirect to. That makes the post-booking redirect the entire design: send the invitee to your own domain, pass the event details along, and fire the conversion there. Done carelessly, it double-counts every refresh and loses anyone who closes the tab before the redirect completes.

Free30 minutesNo obligation

Koalendar · what breaks

Why Koalendar bookings go uncounted

  1. 01

    No scripts allowed on the booking page

    Everything before the redirect is invisible to your tags.

  2. 02

    Ads that link straight to the Koalendar URL

    No visit to your domain first, so no first-party cookie to match against.

  3. 03

    Thank-you page reloads and bookmarks

    Each visit fires again unless the page knows it has already seen this booking.

  4. 04

    A booking type with no redirect set

    Invitees land on Koalendar's own confirmation, where nothing of yours runs.

Koalendar · the fix

What the rebuild gives you — Koalendar

  • One conversion per real booking

    Keyed on the details Koalendar passes, so reloads are ignored.

  • Click data kept on your domain

    Ads land on your page first, so the cookies are yours.

  • A server-side copy of each booking

    Blocked browsers no longer mean missing conversions.

Koalendar · architecture

What Koalendar actually lets you do

Confirmed from Koalendar's help center and settings, with the unconfirmed parts marked as checks.

  1. 1

    Redirect invitee after booking

    A URL you set, so the invitee lands on your own page.

  2. 2

    Pass event details to the redirect URL

    Optional, and it is what lets the page know which booking it is confirming.

  3. 3

    No custom GA or GTM on the booking page

    The help center says to track on the redirect page instead.

  4. 4

    Check whether a native Google Analytics field exists on your plan

    Mentioned on an integration page we could not confirm; test it before relying on it.

  5. 5

    Check whether the booking page can be embedded

    Not confirmed. If it can, test whether the redirect still fires from inside the embed.

Koalendar · diagnose

Where Koalendar tracking breaks, in diagnostic order

On Koalendar nearly every fault sits on the redirect, so the checks start and end there.

  1. 01

    Check every booking type has a redirect URL

    One missing redirect is enough to lose a whole campaign's conversions.

  2. 02

    Make a booking and read the redirect URL

    Confirm the event details arrive and identify the booking uniquely.

  3. 03

    Reload the thank-you page

    If a second conversion fires, the page is not deduplicating.

  4. 04

    Find ads that link directly to Koalendar

    They skip your domain, leaving nothing to match the booking to.

  5. 05

    Compare the meeting list with platform counts day by day

    A steady shortfall means the redirect; spikes mean duplicate firing.

Koalendar · prove

Proof on Koalendar

Run on your Koalendar booking types with real bookings and real redirects.

Source of truth

Koalendar's list of scheduled meetings by date and booking type

  • A booking from a tagged ad click with the conversion confirmed on the redirect page.
  • Event details on the redirect confirmed for every booking type in use.
  • A reload of the confirmation page confirmed not to fire twice.
  • Browser and server events confirmed deduplicated on a shared event ID.
  • Matched meeting by meeting against each platform over a closed window.
  • A booking made from an email-signature link confirmed not credited to an ad.
  • Re-checked after 30 days and whenever booking types change.

Koalendar · free audit

What we check in the free audit

  • Check every booking type has a redirect URL
  • Make a booking and read the redirect URL
  • Reload the thank-you page
  • Find ads that link directly to Koalendar
  • Compare the meeting list with platform counts day by day

Checked against

Koalendar's list of scheduled meetings by date and booking type

Get my free conversion tracking audit

Free30 minutesNo obligation

Koalendar · when not to buy

When you don't need this on Koalendar

Koalendar setups are often closer to done than people think.

  • If you only want booking counts in GA4 and every booking type already redirects to a page carrying your tag, you may be most of the way there.
  • If paid traffic brings a handful of bookings a month, matching the meeting list against ad clicks by hand is cheaper than a build.
  • If your meetings are internal or with existing customers, there is nothing to attribute.
  • A redirect plus a fire-once thank-you page is often something your own developer can finish in a day.

Koalendar · what we deliver

The event map around Koalendar

  • Landing page visited

    Where the ad click and cookies are captured, on your domain.

  • Booking link clicked

    Recorded on your page before the visitor leaves for Koalendar.

  • Meeting booked

    Fired on the redirect page from the passed event details.

  • Booking type

    From the passed details, so a sales call and a support call are not blended.

  • Meeting held or no-show

    Added from your CRM or notes after the date.

Written guarantee

95%+ tracking accuracy

Measured against Koalendar's list of scheduled meetings by date and booking type. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Koalendar questions, answered

Koalendar's help center says custom GA and GTM scripts are not supported there. Track on the page you redirect to instead.

Free · 30 min

Get Koalendar tracking done properly

Free30 minutesNo obligation