Skip to main content
HomeRunner
View Categories

Booking data for tools like Triptease

0:00 0:53

Third-party marketing tools such as Triptease can read booking data from your HomeRunner site. No native HomeRunner integration is required.

How it works. When a reservation completes, the HomeRunner confirmation page pushes a purchase event to your site’s dataLayer. The event contains:

  1. The booking confirmation number (ecommerce.transaction_id)
  2. The total booking value (ecommerce.value)
  3. The booking currency (ecommerce.currency)
  4. The booked property details (ecommerce.items[])
  5. The stay dates (formValues.checkInDate and formValues.checkOutDate)

Any tool that reads the dataLayer through Google Tag Manager, or that ships its own site-wide script tag, can consume these fields directly.

Using the confirmation page URL. The confirmation page URL also carries the reservation ID as a query parameter (/confirmation/?reservation=<id>), which can serve as a page-level trigger.

Inquiry bookings. For unpaid inquiry-status bookings, the event name is generate_lead instead of purchase. Tools that listen only for purchase see only confirmed, paid bookings.

Still stuck? Contact the HomeRunner team with your site address and what you tried, and we take it from there.