add trigger custom click event

[bblaisATcoveo]

TEST CASE 1 :

• Perform a search that fires a trigger (like 'signin')
• Make sure the trigger is displayed at the top of the results page
• click on a link in the trigger and make sure a custom event is sent at that moment using Chrome debug/network tool
• validate the event from the visit browser

[Garneauma]

@bblaisATcoveo Est-ce que ce qui suit est le genre de payload qui devrait être dans l'évènement triggered?

{
    "language": "en",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36",
    "originContext": "Search",
    "originLevel1": "canada-gouv-public-websites",
    "originLevel2": "default",
    "originLevel3": "/en/sr/srb.html",
    "splitTestRunName": "Canada public websites - Gene...-mirror-1733855881",
    "splitTestRunVersion": "Canada public websites - Generic",
    "customData": {
        "context_searchPageUrl": "/en/sr/srb.html",
        "context_searchPageRelativeUrl": "/en/sr/srb.html",
        "coveoHeadlessVersion": "2.52.0",
        "triggerLinkUrl": "https://www.coveo.com/"
    },
    "facetState": [],
    "anonymous": false,
    "clientId": "4eba2bf7-d22b-4090-8e41-51b443695d36",
    "eventType": "queryPipelineNotificationTrigger",
    "eventValue": "click",
    "lastSearchQueryUid": "a5e2c7db-e762-4403-a28f-05cdc99ddf01"
}

C'est un peu difficile à évaluer puisqu'aucun nom de propriété match l'évènement qui est envoyé dans connector.js (type, meta, evt), mais c'est la différence que j'ai remarqué avec la version released. Merci!

Si c'est bien cela, c'est approuvé.

[bblaisATcoveo]

@Garneauma oui c'est bien l'événement attendu, on regarde "eventType" et "eventValue" pour confirmer que c'est bien un click sur un trigger.

[BeraJosh]

Approved, thank you!

[GormFrank]

I simply resolved the merge conflict.

@cfoss-coveo Please review and test. Once (and if) we receive positive feedback from you, this PR can be merged by @Garneauma. Thanks!

[cfoss-coveo]

Happy to approve to get this out the door, but in my testings, the logging wasn't 100% reliable.

I think what's happening is on page navigation (i.e., clicking a link), the browser cancels all pending requests. This includes the request logging the custom trigger event. The suggested changes just pauses page navigation briefly for the analytics event to be logged.

[cfoss-coveo]

@GormFrank @Garneauma This is safe to deploy, but see my comment above.

[Garneauma]

@cfoss-coveo We'll leave as-is for now as this needs to get out. We'll have to keep this in mind if we have issues with event logs.

[Garneauma]

@ServiceCanada/sc-release-management For your review.

[BeraJosh]

Approved, thank you