---
title: Conversion tracking with your own GTM container
description: "When you use your own Google Tag Manager (GTM) container and the Toolkit's **Conversion Tracking** module is switched off, HomeRunner does not fire any…"
url: "https://homerunner.io/docs/how-does-homerunner-fire-conversion-tracking-on-the-booking-confirmation-page-wh/"
updated: "2026-10-26"
category: Booking engine and checkout
---

# Conversion tracking with your own GTM container

When you use your own Google Tag Manager (GTM) container and the Toolkit's **Conversion Tracking** module is switched off, HomeRunner does not fire any pixel of its own on the booking confirmation page. Instead, it makes the booking data available to your container.

**How the event works.** When the confirmation page loads, the HomeRunner plugin pushes one event into the page's dataLayer. This is the same dataLayer your GTM container reads. The event is named purchase when your PMS returns the reservation as confirmed, and generate_lead for any other status.

The payload is a standard GA4 ecommerce object containing transaction_id, value (the booking total), currency, tax, and items. The items are the property at the nightly rate with quantity equal to the number of nights, a taxes line, and one line per fee.

HomeRunner's own container on the page reads the same push and only feeds HomeRunner's analytics property.

**Setting up your tags.** Your GTM container can trigger GA4, Google Ads, and Meta tags on those custom events. The push happens on every load of the confirmation page, including a refresh, so configure your tags to dedupe on transaction_id where supported.

**Checking your setup.** GTM Preview mode on a confirmation page shows the push and which of your tags fired.

Still stuck? [Contact the HomeRunner team](https://homerunner.io/contact/) with your site address and what you tried, and we take it from there.