Checkfront · Google Ads conversion tracking

Checkfront Google Ads conversion tracking

For Checkfront operators running Google Ads, and the people who manage their accounts. The three ways to count Checkfront bookings as Google Ads conversions, what each one sends, how to keep a booking from being counted twice, and how to troubleshoot missing, duplicate or mis-valued purchases in GA4, Google Ads and Meta.

Last reviewed November 1, 2026. Checked against Checkfront's help center and Google Ads, Analytics and Tag Manager documentation.

Short answer

Checkfront Google Ads conversion tracking is built in: create a website purchase conversion action in Google Ads with "Use different values for each conversion", copy its Conversion ID and Conversion Label, and enter them under Manage > Integrations > Conversion > Google Adwords in Checkfront. Checkfront's documentation says the integration tracks the conversion, ad source, booking ID and conversion amount on the Receipt and Waivers/Document pages. The alternatives are importing a GA4 key event, or firing a Google Ads conversion tag from your own page through a Custom Receipt URL and Google Tag Manager. Whichever you choose, make only one of them a primary conversion action so each booking is counted once. If bookings are missing, doubled or valued wrongly in GA4, Google Ads or Meta, the troubleshooting section covers each cause on Checkfront.

Three ways to count Checkfront bookings in Google Ads

Checkfront's booking steps run on Checkfront's own pages, inside the Booking Widget's iframes or on the Hosted Customer Booking Page, and Checkfront does not allow custom scripts in the booking flow (Tracking referrals and campaigns). So a Google Ads tag on your website cannot see the booking itself. The routes that can:

RouteWhere the conversion firesValue and IDChoose it when
1. Checkfront's Google Adwords integrationCheckfront's Receipt and Waivers/Document pagesConversion amount and booking ID are tracked, per Checkfront; currency is not mentionedYou want the documented, low-maintenance setup
2. Import a GA4 key eventWherever your GA4 purchase firesWhatever the GA4 event carriesGA4 already records bookings with value and good attribution
3. Google Ads tag on a Custom Receipt URL page, through Google Tag ManagerA confirmation page on your own siteBooking total and booking ID from the receipt URL; currency set by youYou want the conversion on your own domain, alongside GA4 and Meta tags you control

Route 1 and Route 3 do not mix well: Checkfront says its Google Analytics and Google Ads plugins "DO NOT WORK when using a Custom Receipt URL" (ecommerce settings article). If you set a Custom Receipt URL, the Google Ads conversion has to come from your own tag, and the Checkfront integration should be switched off. The Checkfront integration is described in Introduction to the Checkfront Integration with Google Ads. Our booking tracking overview compares the same choice on other booking platforms.

Create the purchase conversion action in Google Ads

Routes 1 and 3 both need a conversion action with its own Conversion ID and Conversion Label. Checkfront's Setting up Google Ads article walks through it. Google moves its menus from time to time, so the exact labels in your account may differ slightly.

  1. In Google Ads, start a new conversion action and choose Conversions on a website as the source. Enter your website address and click Scan, then choose the Google tag as the data source.
  2. Set the category to Purchase.
  3. Choose to set it up Manually with code. Google's Tag Manager help notes that automatically created conversion actions have no standalone label, which is why a manual action is needed here (Google Ads conversions in Tag Manager).
  4. Under value, choose Use different values for each conversion. Enter any default value; Checkfront says the actual values come from your items or products.
  5. Set count to Every. Checkfront recommends it for purchases, and Google describes "Every" as a good choice for sales in About conversion counting options.
  6. Give it a plain name such as Checkfront Bookings.
  7. On the summary step, open the Use Google Tag Manager tab and copy the Conversion ID and Conversion Label. Click Finish.

Leave it as a primary action if this is the conversion you want bidding to use. Checkfront's article notes that primary actions are used for bidding and secondary actions are for observation.

Route 1: connect Checkfront's Google Adwords integration

  1. In Checkfront, go to Manage > Integrations and click the Google Adwords tile in the Conversion section.
  2. In the Add-on Setup window, enter the Google Conversion ID and Google Conversion Label from the previous step.
  3. Click Activate.

These steps are from Setting up Google Ads in Checkfront, which also says new customer bookings are then sent to Google Ads with the transaction value, the conversion action stays Unverified until the first conversion, and the first conversion can take up to 3 hours to appear. You need Admin permissions in Checkfront, and Checkfront suggests turning off ad blockers while you work in Google Ads.

What Checkfront's introduction says the integration does: it "tracks the conversion, ad source, booking ID, language, and conversion amount", it "adds the Google Ads tag to the booking page", and "Only the Receipt and Waivers/Document pages are tracked". A booking where the customer stops at the Guest page is not tracked.

What the documentation does not say

Checkfront does not say which currency is sent with the value, whether the booking ID is sent as Google's transaction ID (which is what lets Google Ads drop duplicates), whether a booking that reaches both the Receipt and the Waivers/Document page records one conversion or two, or how the ad click is carried from your site into the booking pages. Check the first few real conversions against Checkfront's bookings: count, value and currency.

Route 2: import the GA4 booking event

If GA4 already records Checkfront bookings (see our Checkfront GA4 guide), you can import that event into Google Ads. Google's requirements, from Create conversions from Google Analytics events:

  1. Link Google Ads and GA4, and turn on auto-tagging in Google Ads.
  2. Mark the booking event as a key event in GA4.
  3. Have at least the Marketer role in GA4, then create the conversion action from the GA4 key event in Google Ads.

Imported data can take up to 24 hours to appear, and earlier data is not included.

Think about attribution before you choose this route. Checkfront's GA4 introduction says bookings made through the Booking Widget appear in GA4 as direct traffic. A booking that GA4 cannot connect to the visit that came from an ad has little for Google Ads to credit. Import works best when GA4 sees the purchase in the same session as the ad click: through the Hosted Customer Booking Page with cross-domain settings, or through a Custom Receipt URL on your own site.

Google notes that conversions based on Analytics key events can be created as secondary actions "to prevent counting the same event twice for bidding" when your account already has goals from Analytics (Create Google Ads conversions based on key events). Check the status of the imported action after you create it.

Route 3: a Google Ads conversion tag on your own confirmation page

This route uses Checkfront's Custom Receipt URL (Manage > Ecommerce Setup > Settings) to send customers to a confirmation page on your site with booking details in the address. The full setup, including the script that turns {$BOOKING_ID} and {$BOOKING_TOTAL} into a data layer purchase event, is in our Custom Receipt URL and GTM steps. Once that event exists, add:

Google Tag Manager setting

Variables (Data Layer Variable, Version 2)
  DLV - ecommerce.transaction_id   ecommerce.transaction_id
  DLV - ecommerce.value            ecommerce.value
  DLV - ecommerce.currency         ecommerce.currency
Tag 1
  Name: Conversion Linker
  Type: Conversion Linker
  Triggering: All Pages
Tag 2
  Name: Google Ads - Checkfront booking
  Type: Google Ads Conversion Tracking
  Conversion ID: from the conversion action
  Conversion Label: from the conversion action
  Conversion Value: {{DLV - ecommerce.value}}
  Transaction ID: {{DLV - ecommerce.transaction_id}}
  Currency Code: {{DLV - ecommerce.currency}}
  Triggering: CE - purchase (Custom Event, event name purchase)

The tag fields come from Google's Google Ads conversions in Tag Manager article, which notes that an empty Conversion Value is sent as 0. The Conversion Linker stores ad click data in first-party cookies on your domain, and Google recommends the All Pages trigger; a container whose Google tag loads on every page does not also need one. Because the conversion fires on your own domain, the click data your site stored when the visitor arrived from the ad is available on the confirmation page.

Google says a second conversion with the same transaction ID is treated as a duplicate and not counted, that the ID must be unique per transaction and up to 64 characters, and that it must not contain customer-identifying information (Use a transaction ID to minimize duplicate conversions). Checkfront's booking ID, for example UHXE-492058, fits those rules.

When you switch to this route, deactivate the Google Adwords integration in Checkfront, since Checkfront says it does not work with a Custom Receipt URL and its Waivers/Document page tracking would otherwise be an unknown second source. Keep the conversion action for your own tag. If you also import a GA4 purchase from the same confirmation page, keep that import secondary.

Avoid double counting

The common way a Checkfront account double counts is running Route 1 and importing a GA4 booking event as well, with both set as primary. Google's advice when Google Ads and Analytics measure the same purchase is to "only use one conversion as your primary goal, to prevent double counting" (Enhanced conversions in Google Analytics).

  • Pick one booking conversion as primary. Set every other booking conversion to secondary so you can still see it.
  • Do not have the Checkfront integration and your own Tag Manager tag both active. If you use a Custom Receipt URL, deactivate the Google Adwords integration.
  • Send a transaction ID wherever you control the tag, so reloads and repeat visits to a confirmation page do not add conversions.

Value, currency and transaction ID by route

FieldRoute 1 (Checkfront integration)Route 3 (your tag)
Value"conversion amount" or "transaction value", per Checkfront{$BOOKING_TOTAL} ("Total value of the booking") or {$BOOKING_PAID} (amount paid, can be a deposit)
CurrencyNot documentedNo placeholder; set it in your code to your account currency
Transaction IDBooking ID is tracked; use as transaction ID not documented{$BOOKING_ID}

Placeholders are from Checkfront's ecommerce settings article. If your Google Ads account uses a different currency from your Checkfront account, check the currency on the first few conversions.

How to verify Google Ads conversions

  1. Make a test booking. Checkfront's Google Ads article suggests a test booking and payment on your Booking Page. Checkfront's Test Payment Provider takes test cards, but it overrides any live payment provider, so on a live site use it briefly at a quiet time and disable it straight after, or make a low-value real booking and then cancel and refund it.
  2. Route 3: run the booking with GTM Preview open. On the confirmation page, check that the Google Ads Conversion Tracking tag fired once on the purchase event and that Conversion Value, Transaction ID and Currency Code show real values, not blanks.
  3. Check the conversion action status. In Google Ads, find the action in your conversions list. Google's Tag Assistant troubleshooting article says you can hover over an Unverified, Tag inactive or Needs attention status, choose Troubleshoot, connect Tag Assistant to your site, trigger the conversion, then select Finish. After that the status reads "no recent conversions" until real conversions arrive, then "Recording".
  4. Route 1: allow up to 3 hours, as Checkfront notes, before expecting the first conversion.
  5. Reconcile. After a week, compare conversions and conversion value with Checkfront website bookings for ad-driven visits. Large gaps point to the problems below.
  6. Cancel and refund the test booking, and switch off the Test Payment Provider if you used it.

Checkfront tracking troubleshooting: GA4, Google Ads and Meta

When Checkfront bookings are missing, doubled or valued wrongly in GA4, Google Ads or Meta, the cause is usually one of four things: the purchase fires on Checkfront's booking pages through its own integrations, so nothing on your site can see it; a Custom Receipt URL is set, which Checkfront says stops its Google Analytics and Google Ads plugins from working; the Booking Widget's iframes make GA4 report bookings as direct, as Checkfront documents; or two routes are reporting the same booking. Each problem below covers what you see, the likely causes on Checkfront, how to confirm it and how to fix it.

How Checkfront tracking fits together

Checkfront's booking steps run on Checkfront's pages: inside the Booking Widget, which Checkfront says is built with iframes, or on the Hosted Customer Booking Page at your Checkfront address plus /reserve/. Checkfront does not support custom scripts in the widget or the booking flow (widget code article, Tracking referrals and campaigns). Purchases reach your ad and analytics accounts in one of two ways:

  • Checkfront's integrations under Manage > Integrations > Conversion: Google Analytics, Google Adwords and Facebook Advertising. Checkfront adds your tags to its booking pages.
  • A Custom Receipt URL under Manage > Ecommerce Setup > Settings, which sends the customer to a page on your site with booking details in the address, where your own tags fire.

Most of the problems below come from not knowing which of the two is active for each platform.

Quick checks for Google Ads

  • Status stays Unverified on Route 1. Confirm the Conversion ID and Label in the Google Adwords add-on match the action, that the integration is active, and that a booking reached the Receipt page. If you have a Custom Receipt URL set, Checkfront says the integration will not work.
  • Conversions higher than bookings. Usually two primary actions for one booking, or a confirmation page tag without a transaction ID. See duplicate purchases.
  • Value is 0 or wrong. On Route 3, an unmapped value variable is sent as 0. On Route 1, check the conversion action uses different values for each conversion. See wrong or missing value.
  • Imported GA4 conversions are far below bookings. Expected if most bookings come through the widget and GA4 records them as direct. See cross-domain session breaks.

The order to fix things in

  1. Write down the route for each platform. For GA4, Google Ads and Meta, note whether the Checkfront integration is active and whether a Custom Receipt URL is set. Checkfront says the Google Analytics and Google Ads plugins "DO NOT WORK when using a Custom Receipt URL" (ecommerce settings article), so a receipt URL with only native integrations is the first thing to resolve.
  2. Check the base tags on your site. If you use Checkfront's GA4 integration, Checkfront asks for the Google tag directly in the page head, once per page, and not through Google Tag Manager, for its cross-domain tracking (Setting up GA4 in Google Analytics). Your Meta pixel base code should use the same Pixel ID as the Checkfront integration.
  3. Check the IDs in each Checkfront integration: GA4 Measurement ID and Parent Page Domain, Google Conversion ID and Label, Facebook Pixel ID.
  4. Get exactly one purchase per booking in each platform (see no purchase event and duplicate purchases).
  5. Fix value and currency.
  6. Improve attribution: cross-domain settings, unwanted referrals, Tracking IDs.
  7. Check consent on your site and ask Checkfront how its booking pages handle it.
  8. Settle primary and secondary conversions in Google Ads, and deduplication in Meta.

Run a clean diagnostic test booking

  1. Pick the payment method for the test. Checkfront's Test Payment Provider (Manage > Ecommerce Setup > Payment, Sandbox category) accepts test cards such as Visa 4111111111111111. Checkfront warns that it "overrides any live Payment Provider" and should not be enabled on a customer-accessible website, so on a live site enable it only for a few minutes at a quiet time, or instead make a low-value real booking that you then cancel and refund. Test transactions show as "TestPayment" with "TEST" in the booking Log.
  2. Prepare the browser. Turn off ad blockers and privacy extensions for the test, since Checkfront notes they can prevent tracking. Install the Tag Assistant Chrome extension: Google says iframe-loaded tags can only be debugged with it installed (Troubleshoot with Tag Assistant). Install Meta Ads Data Advisor, formerly Meta Pixel Helper (Meta Ads Data Advisor).
  3. Open the tools. Start GTM Preview or Tag Assistant on your site, open GA4 DebugView, and open your pixel's Test events tab in Meta Events Manager.
  4. Accept the cookie banner, then book the way customers do: through your widget, or through your link to the hosted page. Add a Tracking ID to the link, such as ?tid=tracking-test, so the booking is easy to find in Checkfront.
  5. Record what fires on each page: Booking Form, Payment, Receipt, Guest Form and Documents/Waivers (Checkfront's tracked pages), or your confirmation page. For each platform, note the event name, how many times it fired, and its value, currency and ID.
  6. Check the address bar on the last page. If it shows your confirmation page, a Custom Receipt URL is active.
  7. Clean up. Cancel and refund the booking and switch off the Test Payment Provider if you used it.

No purchase event

What you see. Bookings in Checkfront, but no purchase, key event or conversion in GA4, Google Ads or Meta.

Likely causes on Checkfront.

  • The integration is not active, or has the wrong ID.
  • A Custom Receipt URL is set, so Checkfront's Google Analytics and Google Ads plugins do not work, by Checkfront's own description, and no tag has been added to your confirmation page. For Meta, Checkfront's Facebook FAQ suggests a custom event when a custom receipt URL is used.
  • You are looking for a specific event name. Checkfront's GA4 integration creates events on the Receipt, Guest Form and Documents/Waivers pages, but its GA4 introduction does not name them.
  • The customer stopped before the tracked page. Checkfront's Google Ads introduction says only the Receipt and Waivers/Document pages are tracked, and a customer who drops out at the Guest page is not.
  • The booking was made by staff or through an OTA. Checkfront's GA4 reporting article says those do not appear in Google Analytics.
  • An ad blocker or consent choice stopped the tags.

How to confirm. Run the clean test booking. In GA4 DebugView, list every event on the Receipt page, whatever its name. In Google Ads, check the conversion action status. In Meta Test Events, look for the purchase event on the receipt page.

How to fix. Correct the IDs and reactivate the integration. If you rely on a Custom Receipt URL, add your own purchase tags to the confirmation page, following our Custom Receipt URL and GTM steps. For GA4, mark the receipt event as a key event once you know its name.

Duplicate purchases

What you see. More purchases or conversions than bookings, often about double.

Likely causes on Checkfront.

  • Several post-booking pages. GA4 events are created on the Receipt, Guest Form and Documents/Waivers pages, and the Google Ads integration tracks both the Receipt and the Waivers/Document page. If more than one of those GA4 events is a key event, a booking counts more than once. Checkfront does not say whether Google Ads records one conversion or two when a customer reaches both pages.
  • Two routes at once. A native integration left active next to your own confirmation page tag, or a GA4 import and the Checkfront Google Ads tag both set as primary. When you use a Custom Receipt URL, deactivate the Google Analytics and Google Adwords integrations, and check that Checkfront's Facebook integration is not sending a second Purchase.
  • A server event with nothing to match. A Conversions API Purchase sent alongside Checkfront's native pixel, which has no documented event ID.
  • Reloads. A confirmation page tag without a once-per-booking check or transaction ID.
  • The Google tag loaded twice on your site, directly and through Tag Manager.

How to confirm. In the clean test, count how many times each purchase event fires and on which page. Reload the confirmation page and see whether it fires again. In Google Ads, look at which booking conversion actions are marked primary.

How to fix.

Wrong or missing value and currency

What you see. Purchases arrive but revenue is zero, blank, in the wrong currency, or does not match Checkfront's booking totals.

Likely causes on Checkfront.

  • The native GA4 and Meta integrations are not documented as sending value or currency. Checkfront's Google Ads integration is documented as sending a "conversion amount", but not a currency.
  • The Google Ads conversion action uses one value for every conversion instead of "Use different values for each conversion", the setting Checkfront's Setting up Google Ads article asks for.
  • On a Custom Receipt URL, the address has no {$BOOKING_TOTAL}, the script cannot read it as a number, or the currency in your code does not match your Checkfront account. Checkfront has no currency placeholder.
  • You are comparing different numbers: {$BOOKING_TOTAL} is the total value of the booking, while {$BOOKING_PAID} is the amount paid, which can be a deposit or 0.
  • Value sent without currency. Google says currency is required with value for revenue metrics to be computed accurately (recommended events reference), and Meta's Pixel reference lists both as required for Purchase.

How to confirm. In the clean test, read the parameters on the purchase event in DebugView, Tag Assistant and Meta Test Events, and compare with the booking total in Checkfront. On the confirmation page, read the address bar to see the raw total Checkfront passed.

How to fix. If the native events carry no value, move the purchase to a Custom Receipt URL page and send value and currency yourself. In Google Ads, switch the action to different values per conversion. In your script, set the currency explicitly and decide once whether to report total or paid.

Cross-domain session breaks and direct traffic

What you see. In GA4, bookings attributed to direct traffic or to your Checkfront domain as a referral, sessions split in two, and imported Google Ads conversions far below bookings.

Likely causes on Checkfront.

  • Booking Widget. Checkfront states that because the widget is built with iframes, "referral information cannot be tracked by Google Analytics 4" and widget conversions "appear as direct". This is the documented behavior of the native route.
  • Hosted page links without linker parameters. Checkfront's integration supports cross-domain tracking, but Google's linker only adds _gl to links to configured domains, and Google lists JavaScript-triggered navigation and redirects that drop query parameters as cases where linking fails (Set up cross-domain measurement).
  • The Google tag deployed through Tag Manager. Checkfront says this "does not support cross-domain tracking with Checkfront".
  • Different Measurement IDs on your site and in Checkfront. Google says every domain must use the same Google tag ID from the same web stream.

How to confirm. Click your booking link and check whether the Checkfront address contains _gl=. In GA4, look at the traffic source of test purchases. Compare the Measurement ID in Checkfront with the one on your site.

How to fix.

  • For ad landing pages, link to the Hosted Customer Booking Page rather than embedding the widget, with the Google tag loaded directly and your domains added under Configure your domains.
  • Add your Checkfront domain and any payment processor that appears as a referral to List unwanted referrals (Identify unwanted referrals).
  • Or move the purchase to a Custom Receipt URL page on your own domain, so it is recorded in the visitor's own session on your site.
  • Use Checkfront Tracking IDs (tid) on campaign links so you can reconcile campaigns in Checkfront's Booking Index whatever GA4 shows.

What you see. Purchases missing for some visitors or regions, nothing in DebugView until you accept cookies, or Google Ads and Meta numbers well below bookings in Europe.

Likely causes on Checkfront.

  • Your cookie banner blocks or delays tags on your own site and your confirmation page. Google's DebugView article says events do not appear in DebugView when consent mode is active and Analytics consent has not been given.
  • Checkfront's help articles do not describe how its integrations on the booking pages handle consent or consent mode. Checkfront says its customer booking page "does not utilize any external cookies" and uses cookies for booking sessions and the cart, and that browser cookies must be allowed for the widget and plugins to work.
  • Browser privacy controls. Checkfront builds the Booking Widget with iframes, Google describes cookies in cross-site contexts such as iframes as third-party cookies (Audit your use of cookies), and WebKit says Safari's tracking prevention blocks all third-party cookies by default (Tracking Prevention in WebKit).

How to confirm. Run the clean test twice, once accepting and once rejecting cookies, and compare which tags fire on your site, inside the booking pages and on your confirmation page.

How to fix. On your own pages, set consent mode defaults before any measurement command and update them when the visitor chooses, as Google describes in Set up consent mode on websites. For the booking pages, ask Checkfront support how its Google and Facebook integrations handle consent, especially if you advertise to people in the European Economic Area, where Google requires consent signals for measurement and remarketing (EEA consent mode updates). Moving purchases to a Custom Receipt URL page puts them under your own banner and consent settings.

Tags running inside the Checkfront booking pages

What you see. Tag Assistant or Meta Ads Data Advisor shows Google or Meta tags inside the widget or on your Checkfront domain that your Tag Manager container did not fire, or GA4 shows booking-page events you did not create.

Likely causes on Checkfront. These are usually your own integrations at work. When the Google Analytics, Google Adwords or Facebook Advertising integration is active, Checkfront adds your Measurement ID, Google Ads tag or pixel to its booking pages: the GA4 integration tracks the Reserve/Booking, Booking Form, Payment, Booking Invoice, Receipt, Guest Form and Documents/Waivers pages, the Google Ads integration "adds the Google Ads tag to the booking page", and the Facebook integration runs your pixel on the customer booking pages. Checkfront does not support a second Tag Manager container or custom scripts in the booking flow, so these platform-managed tags are the only tags there that you configure.

How to confirm. With the Tag Assistant extension installed, compare the IDs firing inside the booking pages with the IDs in your Checkfront integrations. An ID that matches is yours, sent by Checkfront on your behalf. If you see an ID that does not match any of your accounts, ask Checkfront support what it is before changing anything.

How to fix. Nothing to remove if the IDs are yours; this is the normal way Checkfront tracking works. Make sure only one of them counts as the purchase (see duplicate purchases), and if a booking-page event duplicates your confirmation page purchase, unmark it as a key event or switch that integration off. To change what is sent, edit the integration under Manage > Integrations > Conversion.

Frequently asked questions

Does Checkfront have a built-in Google Ads integration?

Yes. It is the Google Adwords tile under Manage > Integrations > Conversion. You enter a Google Conversion ID and Conversion Label, and Checkfront says it sends new customer bookings to Google Ads with the transaction value.

Where do the Conversion ID and Conversion Label come from?

From a manually created website conversion action in Google Ads. Checkfront's setup article says to open the "Use Google Tag Manager" tab on the conversion action's summary, where both values are shown.

Why is the Checkfront conversion action still Unverified?

Checkfront says the status stays Unverified until the first conversion, which can take up to 3 hours to appear. If it stays that way after a completed booking, check the ID and label, and check that no Custom Receipt URL is set, since that stops the integration from working.

Should the GA4 import or the Checkfront Google Ads tag be the primary conversion?

Use one, not both. The Checkfront tag sees every receipt but its currency and transaction ID handling are not documented. A GA4 import is only as good as GA4's attribution, and Checkfront says widget bookings appear as direct in GA4. Make the route that best matches your Checkfront bookings primary and set the other to secondary, so you can still compare them.

Can Checkfront send enhanced conversions?

Checkfront's documentation does not mention enhanced conversions, and the Custom Receipt URL does not pass customer details. Ask Checkfront support whether the integration supports it in your account.

Why does Checkfront show bookings that GA4 does not?

Checkfront's GA4 reports only include bookings customers make from your website, not staff or OTA bookings, and Checkfront notes that ad blockers and privacy settings can prevent tracking. It says GA4 should not be used as a reliable source for sales figures, so expect GA4 to be lower than Checkfront.

Why did tracking stop after setting a Custom Receipt URL?

Checkfront says its Google Analytics and Google Ads plugins do not work when a Custom Receipt URL is used, and that tracking then has to be built on your receipt page. Add your own GA4, Google Ads and Meta tags to the confirmation page and switch the native Google integrations off, or remove the Custom Receipt URL and go back to the native integrations.

Can a Google Tag Manager container be added inside the Checkfront booking widget?

No. Checkfront does not support custom scripts in the widget code or the booking flow. Use its integrations, or a Custom Receipt URL page on your site where your container runs.

Is the Checkfront Test Payment Provider safe to use on a live site?

Checkfront says it overrides any live payment provider and should not be enabled on a customer-accessible website. If you use it, keep it on only for the few minutes of the test, or make a small real booking and refund it instead.

Want a second check on your booking tracking?

We check booking tracking setups like this one as part of our Booking Signal Audit: whether each booking reaches GA4, Google Ads and Meta once, with the right value, and what the ad platforms are learning from it. Ask us about an audit or see how the audit works.