here's an issue where visit to the production websites are no longer being tracked by hotjar. This did work at some point previously.
We're uncertain on the exact date this change of behaviour occurred.
What to do
There are two potential aspects of this that need to be explored.
Infrastructure
@mikeAdamss
tracking codes are being provided to the apps running on the cluster and have not changed ....but ... there are some undocumented changes to tracking codes in this PR: https://github.com/GSS-Cogs/idpd-platform/pull/79/files
given we used to work in a less diciplined way it's very possible that these codes were applied to the old cluster prior to the PR and are (potentially) the reason the tracking broke (as even if correct they would have been overwritten on the next IAC apply).
Try those codes
Chat with UR and find out where they came from, i.e from John or a different hotjar account?
If they're still not the right ones, confirm with UR what the codes should be.
Note - I have done the last point in passing but its quite technical and undocumented, so some crossed wires is possible, this is principally an exercise in permanently ruling this out. Once we figure out whatever it was that was done previously, writing it down would be a good idea.
Frontend/Volto
If/when deployed tracking codes are confirmed correct...
Then it's a frontend issue, as (its implied but not documented) that Volto should somehow be picking up theses codes to enabled hotjar tracking.
We'll need to figure out how this functionality was implemented and why it's no longer working and fix it.
Note - if you get some temporary tracking codes from John for say https://climate-change.staging.ukstats.dev and let platform (Mike) know we should be able to debug this in the staging environment.
Acceptance Criteria
[x] Tracking codes shared with the apps on the clusters are confirmed as correct (platform - Mike)
[ ] Tracking is confirmed to be working as expected by UR
[ ] Process for implementing site tracking for future sites is documented
What is this
here's an issue where visit to the production websites are no longer being tracked by hotjar. This did work at some point previously.
We're uncertain on the exact date this change of behaviour occurred.
What to do
There are two potential aspects of this that need to be explored.
Infrastructure
@mikeAdamss
tracking codes are being provided to the apps running on the cluster and have not changed ....but ... there are some undocumented changes to tracking codes in this PR: https://github.com/GSS-Cogs/idpd-platform/pull/79/files
given we used to work in a less diciplined way it's very possible that these codes were applied to the old cluster prior to the PR and are (potentially) the reason the tracking broke (as even if correct they would have been overwritten on the next IAC apply).
Note - I have done the last point in passing but its quite technical and undocumented, so some crossed wires is possible, this is principally an exercise in permanently ruling this out. Once we figure out whatever it was that was done previously, writing it down would be a good idea.
Frontend/Volto
If/when deployed tracking codes are confirmed correct...
Then it's a frontend issue, as (its implied but not documented) that Volto should somehow be picking up theses codes to enabled hotjar tracking.
We'll need to figure out how this functionality was implemented and why it's no longer working and fix it.
Note - if you get some temporary tracking codes from John for say https://climate-change.staging.ukstats.dev and let platform (Mike) know we should be able to debug this in the staging environment.
Acceptance Criteria