feat(genQA): new RGA UA events added to the search page client

[mmitiche]

SFINT-5206

The following events has been added:

Custom events:

• generatedAnswerCitationHover
• generatedAnswerCopyToClipboard
• generatedAnswerHideAnswers
• generatedAnswerShowAnswers
• generativeQuestionFeedbackSubmit

Search events:

• rephraseGeneratedAnswer

Added the ability to send generated answer metadata in all the Search UA events by adding a new function getGeneratedAnswerMetadata to the SearchPageClientProvider:

example of adding the fields showGeneratedAnswer and generatedAnswerFormat:

The events are documented here: UA events schemas- GenAI v2

[SimonMilord]

👌

[erocheleau]

Some questions / suggestions

[jmprovencher]

Don't we think that generatedAnswerCitationHover might generate a little bit too much data and does it actually provides us with any clear insight ?

[nathanlb]

Don't we think that generatedAnswerCitationHover might generate a little bit too much data and does it actually provides us with any clear insight ?

It's there because hovering over the citation will show a popup with the relevant document snippet inside and we want to see if it is read.
We'll put it on a debounce timer so it should only trigger an event when the hovering lasted a second or two.

[jmprovencher]

Don't we think that generatedAnswerCitationHover might generate a little bit too much data and does it actually provides us with any clear insight ?

It's there because hovering over the citation will show a popup with the relevant document snippet inside and we want to see if it is read. We'll put it on a debounce timer so it should only trigger an event when the hovering lasted a second or two.

Should we allow more than one hover events per generated answer?

[nathanlb]

Don't we think that generatedAnswerCitationHover might generate a little bit too much data and does it actually provides us with any clear insight ?

It's there because hovering over the citation will show a popup with the relevant document snippet inside and we want to see if it is read. We'll put it on a debounce timer so it should only trigger an event when the hovering lasted a second or two.

Should we allow more than one hover events per generated answer?

Each generated answer can have up to 5 citations and each citation will be hover-able. I don't think capping it makes sense. Given the hover needs to be for a "meaningful" amount of time for the event to be sent, I doubt it'll be accidentally abused.

[felixpelletier]

Don't we think that generatedAnswerCitationHover might generate a little bit too much data and does it actually provides us with any clear insight ?

It's there because hovering over the citation will show a popup with the relevant document snippet inside and we want to see if it is read. We'll put it on a debounce timer so it should only trigger an event when the hovering lasted a second or two.

Should we allow more than one hover events per generated answer?

Each generated answer can have up to 5 citations and each citation will be hover-able. I don't think capping it makes sense. Given the hover needs to be for a "meaningful" amount of time for the event to be sent, I doubt it'll be accidentally abused.

Yep. To be clear, we're looking at new ways to track whether customers "click" on documents (because they might not not that there's answers). We think that customers hovering of citations may be a sign of the customer needing more insight, but the info in the citation hover being good enough (there's nothing in the citation hover today, but there could very well be. We heard that as an idea several times). Could be a cue to indicate the answer is suboptimal but the content is good.