Skip to main content
TrackingConsultingFree audit
SchedlyNo-code & online booking tools

Conversion tracking for Schedly bookings

Schedly does something many no-code schedulers don't: it pushes booking events into Google Tag Manager, with names like bookingSuccessfulV2. It's also explicit that booking-specific events aren't sent to other analytics apps by default. So the event exists, but nothing reaches GA4, Google Ads or Meta until someone builds tags on it — and on an embedded Schedly page, it's worth checking which container actually hears it.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamHow Schedly works ↓

Schedly · what breaks

What goes wrong on Schedly

  1. 01

    An event nobody listens for

    bookingSuccessfulV2 reaches GTM, but no tag is triggered by it.

  2. 02

    Assuming GA4 gets bookings automatically

    Schedly says booking events aren't passed to other analytics apps by default.

  3. 03

    Embed and container out of step

    The event fires in one context while your tags live in another.

  4. 04

    Bookings cut off from the Freshsales deal

    The Zapier sync moves the contact but not the ad click behind it.

Schedly · the fix

What changes — Schedly

  • One trigger, every destination

    GA4, Google Ads and Meta all fire from the same booking event with a shared event ID.

  • The booking confirmed in your own container

    Wherever the Schedly page is displayed.

  • Freshsales outcomes sent back

    Qualified and won deals uploaded against the original click.

Schedly · architecture

What Schedly actually lets you do

Schedly's analytics hooks are documented, and narrower than they first look.

  1. 1

    Booking events pushed to GTM

    bookingSuccessfulV2 and related events, available as triggers in your container.

  2. 2

    No default forwarding to other analytics apps

    Stated by Schedly: GA4 and the ad platforms only get bookings if you build it.

  3. 3

    Embeddable booking pages

    Hosted by Schedly and placeable on your own site.

  4. 4

    Freshsales sync via Zapier

    The documented route for the CRM side.

  5. 5

    Check whether the event reaches your page's dataLayer when embedded

    Confirm whether it fires in the parent page's container or only on the Schedly-hosted page.

Schedly · diagnose

Where Schedly tracking breaks, in diagnostic order

Open GTM preview before anything else. Most of the answers show up in the first booking.

  1. 01

    Make a test booking with GTM preview attached

    Look for bookingSuccessfulV2 in the event stream.

  2. 02

    Check that at least one tag fires on it

    An event with no trigger is the most common Schedly finding.

  3. 03

    Repeat the booking on an embedded page

    If the event disappears, the embed is the issue.

  4. 04

    Read the event's payload fields

    Event names carrying a version suffix can change; tags should read what's actually there.

  5. 05

    Follow one booking into Freshsales

    If the click ID isn't on the contact, the offline loop can't close.

Schedly · prove

The QA evidence — Schedly

Run on a live Schedly booking, with GTM preview and each ad platform's test tools open.

Source of truth

Schedly's booking list and the matching Freshsales deals, by date

  • bookingSuccessfulV2 seen in the container that holds your ad tags.
  • GA4, Google Ads and Meta each receiving exactly one conversion per booking.
  • Browser and server events deduplicated on one event ID.
  • A booking from an embedded page confirmed to fire the same way as a hosted one.
  • The click ID confirmed on the Freshsales contact after the Zapier sync.
  • Reconciled per booking over a fully closed window.
  • Re-checked 30 days later, and after any Schedly event-name change.

Schedly · free audit

What we check in the free audit

  • Make a test booking with GTM preview attached
  • Check that at least one tag fires on it
  • Repeat the booking on an embedded page
  • Read the event's payload fields
  • Follow one booking into Freshsales

Checked against

Schedly's booking list and the matching Freshsales deals, by date

Get my free conversion tracking audit

Free30 minutesNo obligation

Schedly · when not to buy

When you don't need this on Schedly

The fix on Schedly is sometimes very small.

  • If you only need booking counts in GA4, wiring one tag to bookingSuccessfulV2 may be the entire job.
  • If you don't use Freshsales or another CRM, there's no offline loop to build.
  • If bookings come mostly from teammates sharing links by email, paid attribution won't change decisions.
  • If you see a few bookings a week, Schedly's own booking list plus UTMs will cover most questions.

Schedly · what we deliver

The event map on Schedly

  • Booking page viewed

    Volume signal.

  • Booking successful

    From bookingSuccessfulV2, with event type.

  • Meeting held

    Recorded in Freshsales or by the host.

  • Deal created in Freshsales

    The qualified-lead conversion, via the Zapier sync.

  • Deal won

    Offline conversion at closed value.

  • Booking cancelled

    Removed from held and qualified counts.

Written guarantee

95%+ tracking accuracy

Measured against Schedly's booking list and the matching Freshsales deals, by date. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Schedly questions, answered

It's the starting point. Schedly says booking events aren't passed to other analytics apps by default, so GA4, Google Ads and Meta only see bookings if tags in GTM are triggered by them.

More on Schedly

Free · 30 min

Get Schedly tracking done properly

Book the free call WhatsApp

Free30 minutesNo obligation