Mangomint can redirect customers to a page on your website after a successful online booking. Configure that redirect first, then use the page to trigger a Google Ads booking conversion.
This records an online booking. It does not establish that the customer attended, paid, or generated a particular amount of revenue.
1. Create the confirmation page and ask Mangomint to enable the redirect
Create a published page on the same domain as your website, such as https://example.com/booking-confirmed. Tell the customer that the booking is confirmed and what to expect next. Keep the page out of the main navigation.
Contact Mangomint chat support and give them that URL. Ask them to configure it as the redirect after a successful online booking. Mangomint documents this process in its online-booking FAQ.
Complete a test booking to confirm the redirect works on desktop and mobile, including when the booking flow opens in another tab. A working tag on a page nobody reaches will not measure bookings.
2. Confirm your website tag setup
This walkthrough uses Google Tag Manager. You need access to the website's container and Google Ads account. Make sure GTM loads on the landing page and confirmation page, and check whether the correct Google tag is already installed before creating another one.
If you need to add a Google tag, copy its Google Ads tag ID, including the AW- prefix, into a Google Tag in GTM. Use a sitewide initialization trigger and verify the site's consent configuration.

Check click-attribution setup as well. Google's Conversion Linker guide says a container loading a Google tag on every page does not also need a separate Conversion Linker tag. Review the existing setup before adding duplicate tags.
3. Create a booking conversion in Google Ads
Open Goals → Conversions → Summary and create a website conversion action. Choose the manual code setup so you can configure the trigger in GTM. Select a category appropriate to an appointment booking and give it a clear name, such as Mangomint online booking.
Review these settings:
- Value: Use no monetary value if you do not have a defensible estimate, or use a clearly understood estimated booking value. This page-view method does not receive actual appointment revenue automatically.
- Count: If the goal is a lead or appointment enquiry, One per ad click may fit. If you deliberately want every separate booking, review Every and how duplicates will be prevented. Google's count-setting guidance.
- Action optimization: Use the action for bidding only when it represents the intended campaign outcome and the trigger has been tested. Check for an existing action measuring the same booking.
- Conversion window: Choose a window appropriate to the time between an ad interaction and a booking.
Select the Google Tag Manager installation option and copy the conversion ID and label.
4. Add the conversion tag and a specific page trigger
In GTM, create a Google Ads Conversion Tracking tag. Paste the conversion ID and label into their named fields. The sitewide Google tag ID and the conversion label are different values.

Create a Page View trigger using Some Page Views. For the example above, require both Page Hostname equals example.com and Page Path equals /booking-confirmed, adjusted to the exact hostname and trailing-slash behavior of your site. Attach it to the conversion tag.
A broad rule such as “URL contains thank-you” can also match unrelated confirmation pages. Use the booking-specific destination and check how the live redirect resolves.
5. Test the whole booking journey
Open GTM Preview, connect to the website, and complete the booking flow. Confirm that the successful booking redirects to the right page and fires the booking tag once. Check that the tag does not fire on the landing page or an abandoned booking.
Test a reload and direct visit to the confirmation page. A page-view trigger can count either as a booking even without a new completed appointment. If this is a material source of duplicates, you need a verified completion signal or a supported unique-booking identifier for deduplication. Choosing One does not make a false page-view event accurate.
Publish the tested container version. Then compare bookings with attributed conversions over a period that allows for reporting delays. A successful tag test verifies firing; attribution still depends on an eligible ad interaction and the measurement setup.
For later optimization, distinguish booked appointments from attended appointments and sales. If the business also collects separate website enquiry forms, FormTrackr is my app for that form-lead workflow. It is not the booking redirect described here.