The AI Concierge announces its activity to your analytics so you can measure how guests use it. Every time the chat opens and every time it produces a set of results, it pushes an event to the browser data layer for Google Tag Manager, and dispatches a matching browser event for any tooling that listens that way. Both are passive and never interfere with the chat.
The events #
| Data layer event | Browser event | Fires when |
|---|---|---|
| hr_ai_concierge_opened | hr-ai-concierge:opened | The chat opens (one per open). |
| hr_ai_concierge_results | hr-ai-concierge:results | The assistant produces a set of results (every search, any count). |
Every payload includes a per-conversation id, hr_ai_session_id, so you can group events into sessions. The results event carries extra detail:
| Field | Meaning |
|---|---|
| result_count | How many properties matched. |
| on_explorer | True when results were applied in place on the search page. |
| redirected | True when the response sent the guest to the results page. |
| handpicked | True when the assistant curated specific listings rather than only setting filters. |
Counting results pages in GTM #
- Create a new trigger of type Custom Event with the event name
hr_ai_concierge_results. - Add a tag (a GA4 event, for example) that fires on that trigger. Map
result_count,handpicked, andhr_ai_session_idas parameters if you want them in your reports. - Open GTM Preview, load your site, open the assistant, and run a search. You will see the event arrive in the data layer, and your tag fire.
Use hr_ai_concierge_opened the same way to count how many times the assistant is opened. To count unique conversations rather than raw opens, group by hr_ai_session_id.
A note on the older marker #
Earlier builds put a temporary hr_ai_ask parameter on the page URL whenever a search came in through the page-reload path. That was an incidental side effect of an older flow, not a deliberate event, and the in-page assistant no longer reloads the page, so the parameter is no longer produced. The data layer events described here are the stable, intended way to track the assistant, and they work whether it filters in place or sends the guest to a results page.
Listening without Tag Manager #
If you do not use GTM, the same information is available as standard browser events. Listen for hr-ai-concierge:opened and hr-ai-concierge:results on the window object; the event detail carries the same payload described above.