[WORLDSERVICE-643] Implement click tracking on Opera Mini for Canonical

[elvinasv]

Resolves JIRA: https://jira.dev.bbc.co.uk/browse/WORLDSERVICE-643

Summary

A very high-level summary of easily-reproducible changes that can be understood by non-devs, and why these changes where made.

Code changes

• A bullet point list of key code changes that have been made.

Developer Checklist

• UX
  • UX Criteria met (visual UX & screenreader UX)
• Accessibility
  • Accessibility Acceptance Criteria met
  • Accessibility swarm completed
  • Component Health updated
  • P1 accessibility bugs resolved
  • P2/P3 accessibility bugs planned (if not resolved)
• Security
  • Security issues addressed
  • Threat Model updated
• Documentation
  • Docs updated (runbook, READMEs)
• Testing
  • Feature tested on relevant environments
• Comms
  • Relevant parties notified of changes

Testing

• Manual Testing required?
  • Local (Ready-For-Test, Local)
  • Test (Ready-For-Test, Test)
  • Preview (Ready-For-Test, Preview)
  • Live (Ready-For-Test, Live)
• Manual Testing complete?
  • Local
  • Test
  • Preview
  • Live

Additional Testing Steps

1. List the steps required to test this PR.

Useful Links

• Coding Standards
• Repository use guidelines
• Add Links to useful resources related to this PR if applicable.

[karinathomasbbc]

I am wondering if we need to check if it's on lite - because this will technically fire a page view on load, which we might not want to do on canonical...

[karinathomasbbc]

If this is the case, then perhaps we're best moving it to the Lite Renderer instead of adding it here.

[elvinasv]

processClientDeviceAndSendStaticBeacon only defines the beacon, but doesn't fire it on load. It is used by viewTracking and clickTracking

Probably it could be renamed similar to addSendStaticBeaconToWindow ? 🤔

[karinathomasbbc]

Just thinking more about this - processClientDeviceAndSendStaticBeacon does send the beacon here:

simorgh/src/server/utilities/staticATITracking/index.ts

Line 72 in 7d9df95

window.sendStaticBeacon(`${atiURL}&${paramValues}`);

I just want us to prove / double check that we're definitely not firing duplicate beacons - especially on opera mini on lite + canonical, because I am fairly sure in its original state, it was used to send the initial page view on lite, while the implementation in viewTracking + clickTracking was to fire the beacons for a component view/click respectively.

[elvinasv]

(Adding for traceability)

processClientDeviceAndSendStaticBeacon does not send a beacon immediately when added:

1. It creates the function and assigns it to the window, but does not invoke it.

2. processClientDeviceAndSendStaticBeacon only sends the beacon if atiURL is passed (e.g., by clickTracking and viewTracking).

There is a separation of concerns: CanonicalATIAnalytics handles page view tracking, while ComponentTracking handles component view and click tracking.

However as discussed, it would be a good idea to rename (e.g. addProcessClientDeviceAndSendStaticBeaconToWindow) or refactor to extract parameter building logic from the sending of the beacon

[elvinasv]

processClientDeviceAndSendStaticBeacon only defines the beacon, but doesn't fire it on load. It is used by viewTracking and clickTracking

Probably it could be renamed similar to addSendStaticBeaconToWindow ? 🤔

[karinathomasbbc]

Looking great, just a couple of minor things, otherwise good to go! 🚢 🚢 🚢 🚢