---
title: "Confirmation page events: deduplicating on transaction_id"
description: The HomeRunner dataLayer push fires on every load of the confirmation page. Because of this, you should deduplicate these events in GTM on transaction_id.…
url: "https://homerunner.io/docs/how-should-i-deduplicate-homerunner-confirmation-page-events-in-gtm-and-what-is/"
updated: "2026-10-26"
category: Setup and plugins
---

# Confirmation page events: deduplicating on transaction_id

The HomeRunner dataLayer push fires on every load of the confirmation page. Because of this, you should deduplicate these events in GTM on transaction_id.

**What transaction_id contains.** When the plugin's **transaction ID source** is set to the PMS reservation ID, transaction_id equals the PMS reservation ID. For Guesty, this is the long reservation ID, not the short confirmation code.

This ID is also the key for matching conversions back to your PMS.

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