Learn about using group keys to version and manage evolving interactions while preserving history and audit compliance.

In many industries, such as hospitality, healthcare, and telecommunications, customers frequently modify existing interactions. A hotel guest might change the length of a stay, upgrade a room, or cancel a reservation, all under the same booking ID. Traditionally, each of these updates is sent to Reltio as a new interaction, which clutters the profile view and prevents users from easily identifying the current status of an interaction.

The Append interactions feature tracks updates to a transaction, like a hotel booking, without altering the original. It lets you define a specific attribute (such as a booking ID or appointment ID) as a GroupKey, allowing Reltio to treat a series of related interaction updates as part of a single logical thread. In the Hub UI, you will see only the latest version of the interaction for each GroupKey, while earlier updates remain accessible in an audit log. This approach preserves full history without overwhelming the interface or the user. Here's an example:

Mark books a hotel room. Over the next few days, he:

1. Extends his stay
2. Upgrades to a premium suite
3. He later downgrades to a standard room

Each of these updates is sent to Reltio as a new interaction, but all share the same booking ID as their GroupKey. In the Hub, the Interactions tab shows only the final (downgraded) version. The earlier updates are available in the log panel for full traceability. If you're a data steward, you can review these interactions and understand how they've changed over time.

To work with this feature, you must first enable a grouping attribute for an interaction type. For more information, see topic Create an Interaction type.

Learn more about interaction grouping in the Interaction tab.