Skip to main content
FielddHome & field services

Conversion tracking for Fieldd booking portals

Fieldd sends customers from your site to its own booking portal, which can run on a white-label domain, and lets you enter a GA4 Measurement ID, a GTM container ID and a Facebook Pixel ID under Customer Hub. That's more than most field-service schedulers offer. The catch is what fires: GA4 ecommerce steps up to adding a card, plus an older 'Booked_Online' event in some docs — and a saved card isn't a paid job, which is what a mobile service business actually earns on.

Free30 minutesNo obligation

Fieldd · what breaks

What goes wrong on Fieldd

  1. 01

    Add-card treated as the sale

    The card is saved at booking; the charge comes after the work is done.

  2. 02

    The redirect starts a fresh session

    Moving from your site to the portal drops the source unless the domains are linked.

  3. 03

    Two tag sets on one portal

    Fieldd's native GA4 and Pixel fields plus your GTM container can count each booking twice.

  4. 04

    Booked_Online versus the ecommerce events

    Which one actually fires on your portal decides what the ad accounts see.

Fieldd · the fix

What changes — Fieldd

  • Completed jobs as the conversion

    Sent from Fieldd's job records once the work is done and charged.

  • One clean tag path on the portal

    Fieldd's native fields or your GTM container, not both.

  • Service mix carried as value

    Base service plus add-ons, so bigger jobs weigh more.

Fieldd · architecture

What Fieldd actually lets you do

Fieldd documents more tracking hooks than most schedulers in its category. Here's what's confirmed, and the one thing to check on a live booking.

  1. 1

    GA4 Measurement ID and Facebook Pixel ID fields

    Native, in Customer Hub > Analytics, both running in the browser on the portal.

  2. 2

    GTM container ID field

    Your own container on the booking portal, which is where a clean setup starts.

  3. 3

    Standard GA4 ecommerce events

    Page, service list, service view, checkout and add card.

  4. 4

    White-label booking domain

    Supported, which makes cookie handling simpler when it's a subdomain of your site.

  5. 5

    Check whether Booked_Online still fires

    It appears in older Fieldd documentation. Confirm which completion event your portal sends today.

Fieldd · diagnose

Where Fieldd tracking breaks, in diagnostic order

Fieldd gives you enough hooks that most failures are configuration, not missing features.

  1. 01

    Open Customer Hub > Analytics and note every ID entered

    Two GA4 sources, or a Pixel in two places, is the commonest fault.

  2. 02

    Book a job from a tagged link and watch the session

    If GA4 shows a new session starting on the portal, cross-domain linking is missing.

  3. 03

    Identify the completion event

    Booked_Online, an ecommerce step, or nothing — on your portal, not in the docs.

  4. 04

    Compare booked jobs with completed, charged jobs

    Cancellations and no-access visits widen this gap.

  5. 05

    Check the value on the conversion

    Blank or fixed means add-ons and larger services are invisible to bidding.

Fieldd · prove

The QA evidence — Fieldd

Run on a live booking through your actual Fieldd portal, not GTM preview alone.

Source of truth

Fieldd's job records — jobs completed and charged by date, with services and add-ons

  • A booking from a tagged link that keeps its source across the redirect to the portal.
  • Exactly one booking event per job at each destination.
  • Card-added confirmed as a step, never reported as revenue.
  • A completed job sent server-side and deduplicated against the browser event.
  • A cancellation reversed and a reschedule left alone.
  • Reconciled per job over a fully closed window.
  • Re-checked 30 days later, and after any change to the Fieldd portal.

Fieldd · free audit

What we check in the free audit

  • Open Customer Hub > Analytics and note every ID entered
  • Book a job from a tagged link and watch the session
  • Identify the completion event
  • Compare booked jobs with completed, charged jobs
  • Check the value on the conversion

Checked against

Fieldd's job records — jobs completed and charged by date, with services and add-ons

Get my free conversion tracking audit

Free30 minutesNo obligation

Fieldd · when not to buy

When you don't need this on Fieldd

Fieldd's native fields cover more than people expect. Sometimes they're enough.

  • If you sell a single fixed-price service and only run Google, filling in Fieldd's GA4 field and linking the domains may genuinely be enough.
  • If most of your work is recurring customers on a schedule, new bookings are a small share and retention deserves the attention.
  • If Meta only needs to see bookings, the native Pixel ID field plus a correct completion event can do it — at browser-level accuracy.
  • If the dispatcher books most jobs by phone, call tracking comes before portal tracking.

Fieldd · what we deliver

The event map on Fieldd

  • Service list and service viewed

    From Fieldd's GA4 ecommerce events.

  • Checkout started

    Customer details and address entered.

  • Card added and booking placed

    The leading indicator, at quoted value.

  • Job completed and charged

    The primary conversion, sent server-side.

  • Job cancelled or rescheduled

    Cancellations reversed; reschedules left alone.

  • Service and add-ons

    Carried on every event so value reflects the actual job.

Written guarantee

95%+ tracking accuracy

Measured against Fieldd's job records — jobs completed and charged by date, with services and add-ons. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Fieldd questions, answered

One, not both. The GTM container gives you control over events, consent and server-side forwarding; the native field is faster to set up but fixed.

Free · 30 min

Get Fieldd tracking done properly

Free30 minutesNo obligation