---
title: Matching GA4 transaction ID to PMS reservations
description: "By default, the transaction_id on the GA4 purchase event is HomeRunner's own reservation ID, a long UUID, rather than the reservation ID in your PMS.…"
url: "https://homerunner.io/docs/how-do-i-make-ga4-transaction-ids-match-the-reservation-ids-in-my-pms/"
updated: "2026-10-26"
category: Booking engine and checkout
---

# Matching GA4 transaction ID to PMS reservations

By default, the transaction_id on the GA4 purchase event is HomeRunner's own reservation ID, a long UUID, rather than the reservation ID in your PMS.

**Using your PMS reservation ID.** To send your PMS reservation ID instead:

1. Go to **HomeRunner**, then **Settings**.
2. Open the **Advanced** tab and find the **Analytics** section.
3. Set **GA4 Transaction ID Source** to **PMS Reservation ID**.
4. Save.

From the next booking onward, the transaction_id on the purchase event carries the PMS reservation ID. This makes it straightforward to join GA4 purchase data against records in your PMS.

**What to expect.** The change is forward-only. Purchase events already recorded keep the ID they were sent with. If the option is not visible, update the HomeRunner plugin to its latest version first.

**Guesty.** For Guesty, the PMS reservation ID used is the full reservation ID shown in the reservation's URL. The short confirmation code (GY-...) is not available as the transaction_id.

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