Skip to main content
PicktimeMeeting & appointment schedulers

Conversion tracking for Picktime booking pages

Picktime lets you paste a Facebook Pixel ID and a GA4 Measurement ID straight into its integration settings, and the pixel then reports booking-page views, 'Book Now' clicks and completed bookings by itself. For many accounts that looks finished. It isn't quite: those events fire on Picktime's domain, in the browser only, against cookies that aren't the ones your website set, so a visitor who arrived through your site can look like a stranger by the time they book.

Free30 minutesNo obligation

Picktime · what breaks

Where Picktime's built-in tracking falls short

  1. 01

    Two sets of cookies for one visitor

    Your site and Picktime's page each hold their own, so the journey splits in two.

  2. 02

    Browser-only events

    Ad blockers and Safari's limits strip out a share of completed bookings.

  3. 03

    Book Now clicks mistaken for bookings

    Both are tracked; only one of them is a customer.

  4. 04

    No value on the booking

    Every service counts the same, whatever it's worth.

Picktime · the fix

What changes — Picktime

  • Completed bookings with the original click attached

    The ad click ID passed from your site into the Picktime link.

  • Book Now kept as a funnel step

    Useful for spotting drop-off, never optimized on.

  • A server-side booking alongside the pixel

    Deduplicated, so it fills gaps without doubling.

Picktime · architecture

What Picktime actually lets you do

Picktime documents native Pixel and GA4 fields. A tag manager field isn't confirmed, and neither is any server-side sending.

  1. 1

    Facebook Pixel ID field

    Native, on Picktime's Integration page.

  2. 2

    Auto-tracked page views, Book Now clicks and completed bookings

    Picktime fires these itself once the Pixel ID is entered.

  3. 3

    GA4 Measurement ID field

    Also native, on the same Integration page.

  4. 4

    Check whether a GTM container field exists on your plan

    Unconfirmed. Without one, your own tags can't run on the booking page.

  5. 5

    No Conversions API documented

    Everything native happens in the browser.

Picktime · diagnose

Where Picktime tracking breaks, in diagnostic order

Picktime fires its own events, so the first question is what it's actually sending.

  1. 01

    Open Meta's test events and complete one booking

    Note which events arrive and with what parameters.

  2. 02

    Compare the _fbp cookie on your site and on the Picktime page

    If they differ, Meta sees two people.

  3. 03

    Check whether fbclid or gclid reaches the Picktime URL

    When ads point at your site first, it usually doesn't.

  4. 04

    Compare completed bookings with Picktime's own list

    The shortfall is the browser loss.

  5. 05

    Check which event your campaigns optimize on

    Book Now clicks are a frequent wrong choice.

Picktime · prove

The QA evidence — Picktime

Run on a real Picktime booking from a live ad click.

Source of truth

Picktime's booking records — completed bookings by date, with service

  • A booking from an ad link with the click ID present on the Picktime page.
  • The native completed-booking event confirmed in Meta and GA4.
  • A server-side booking deduplicated against it on one event ID.
  • Book Now confirmed as a step nobody optimizes on.
  • A cancellation confirmed to drop out.
  • Reconciled per booking over a closed window.
  • Re-checked 30 days later, and after any Picktime update.

Picktime · free audit

What we check in the free audit

  • Open Meta's test events and complete one booking
  • Compare the _fbp cookie on your site and on the Picktime page
  • Check whether fbclid or gclid reaches the Picktime URL
  • Compare completed bookings with Picktime's own list
  • Check which event your campaigns optimize on

Checked against

Picktime's booking records — completed bookings by date, with service

Get my free conversion tracking audit

Free30 minutesNo obligation

Picktime · when not to buy

When you don't need this on Picktime

Picktime's native fields solve more than most schedulers'. Check these first.

  • If your ads link straight to the Picktime page and you only advertise on Meta, the native pixel already sees the click and the booking on one domain.
  • If every service costs the same, the missing value parameter costs you little.
  • If bookings are mostly existing customers on a regular schedule, acquisition tracking isn't the bottleneck.
  • If you need a rough count for a small budget, Picktime's native fields filled in correctly may be enough. We'll say so.

Picktime · what we deliver

The event map on Picktime

  • Booking page viewed

    From Picktime's native pixel.

  • Book Now clicked

    Intent, from the same pixel.

  • Booking completed

    The conversion, with service type.

  • Booking value

    Set per service, since the native event isn't documented as carrying one.

  • Cancelled or no-show

    Reversed, or excluded from optimization.

Written guarantee

95%+ tracking accuracy

Measured against Picktime's booking records — completed bookings by date, with service. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Picktime questions, answered

Its events run in the browser on Picktime's domain, so they lose a share to blockers and can't see your site's cookies. Whether that matters depends on how big the gap turns out to be in reconciliation.

Free · 30 min

Get Picktime tracking done properly

Free30 minutesNo obligation