WS-2532-Run Search OJ ordering experiment

[Nabeel1276]

Resolves JIRA: https://bbc.atlassian.net/browse/WS-2532

Summary

• Sets up the client-side Search OJ Optimizely experiment with seven validated variations
• Activates the experiment when the mid-article Recommendations OJ enters view
• Adds tracking for OJ clicks, including portrait and standard video curations
• Enables page-view, article-completion and scroll-depth metrics
• Maps each assigned variation to its matching mobile OJ layout with a safe control fallback
• Sends the newswb_ws_oj_order_referrer_search activation event to Piano when Optimizely returns a valid variation

Code changes

• See files changed

Testing

1. Run the app locally with yarn dev
2. Open http://localhost:7081/arabic/articles/ce8l40gnk41o?renderer_env=live&debugReferrer=search in a mobile viewport
3. Scroll until the mid-article Recommendations OJ enters view
4. Confirm Optimizely assigns a variation and the matching OJ layout appears
5. Filter browser developer tools for xiti to check Piano events
6. Scroll through and click each available OJ, confirming its view and click events are logged
7. Confirm the newswb_ws_oj_order_referrer_search activation event is logged once with the assigned variation

Useful Links

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

[Copilot]

Pull request overview

Introduces a new client-side Optimizely experiment hook-up on ArticlePage to resolve and apply a “Search OJ ordering” experiment variant, and pass experiment tracking props into the mid-article onward-journey (Recommendations) module.

Changes:

• Added SearchOjExperiment component that resolves an Optimizely variation and reports a validated SearchOjVariant back to the page.
• Added experiment configuration (experiment name, allowed variants, and layout definitions) under ArticlePage/SearchOjExperiment/config.ts.
• Updated ArticlePage to lazily resolve the experiment variant around the mid-article OJ area and pass experimentProps into Recommendations.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/app/pages/ArticlePage/SearchOjExperiment/index.tsx	New component to resolve Optimizely variation and report a validated experiment variant to the parent.
src/app/pages/ArticlePage/SearchOjExperiment/config.ts	New experiment configuration: name, variants, helpers, and layout mappings for variants.
src/app/pages/ArticlePage/ArticlePage.tsx	Integrates the experiment into the mid-article OJ (wsoj) rendering and passes experiment tracking props into Recommendations.

[pvaliani]

Did the ticket brief get updated to match the experiment brief? Just highlighting so we have that consistency going forward - not strictly related to the PR but will be easier to review the work down the line

[pvaliani]

Will want to add the experiment here

simorgh/src/app/hooks/useClickTrackerHandler/index.jsx

Line 30 in b2f6cc9

'topic-discovery-curation-grid-promo',

so that we can get oj_clicks correctly logged

Similarly in

simorgh/src/app/components/OptimizelyPageMetrics/experimentsForPageMetrics.ts

Line 11 in ad83802

const experimentsForPageMetrics: ExperimentsForPageTypeMetrics = [

otherwise article_completes won't log correctly

From looking at the dashboard it looks like Hausa is still included (audiences value) but i think it should be excluded for this work i believe?

[Nabeel1276]

Did the ticket brief get updated to match the experiment brief? Just highlighting so we have that consistency going forward - not strictly related to the PR but will be easier to review the work down the line

Which part of the ticket brief needed updating? Are you referring to the table with the Footer OJ order? That was in the other ticket (https://bbc.atlassian.net/browse/WS-2995)

[pvaliani]

Did the ticket brief get updated to match the experiment brief? Just highlighting so we have that consistency going forward - not strictly related to the PR but will be easier to review the work down the line

Which part of the ticket brief needed updating? Are you referring to the table with the Footer OJ order? That was in the other ticket (https://bbc.atlassian.net/browse/WS-2995)

Yeah it was the render order alignment between the experiment brief and ticket - not strictly needed right now but was just highlighting it to make sure we've captured it and included topic discovery

[louisearchibald]

We should check against the brief which of these we need to remove after we are done testing. (assuming those code comments are still true!)

[pvaliani]

This has been addressed in a sub task for the ticket to do clean-up after the AA test