Personalised container test #15183
Draft
Personalised container test #15183
+558
−20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…in the highlights container
abeddow91
added
fronts + curation
feature
abeddow91
force-pushed
the
ab/across-the-guardian-spike
branch
from
03f2c66 to
663d4f5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Adds a dynamic container to fronts that aggregates of all 4 pillar containers and their sub containers. The mapping of containers to pillars is hard coded in DCR.
The control for this test will see the first card from each 4 pillars, displayed in a static medium four container. It content cannot be personalised or reordered.
The variant initially displays the same four cards as the control, unless they have already engaged (negatively or positively) with one or more of the cards in the container.
A card is considered engaged with if either of the following conditions are met:
When an engagement condition is met:
The container’s state and interaction history are persisted in local storage, allowing personalisation to carry across visits without server-side dependency.
The cards are initially rendered on the server. They are hidden from view using css. Their visibility is controlled via state which is set to true once the client side data transformation has finished.
Why?
This change is intended to test the impact of lightweight, client-side personalisation on the homepage experience. The hypothesis is as follows
Personalising the pillar container by removing content a user has already engaged with will increase the relevance and freshness of the homepage, leading to improved click through rate compared to a static presentationTo be clear, the expectation is that the whole of this PR is removed once the test has been completed. This container is being used to facilitate the test in order improving our understanding of light weight personalisation. It is not the intention to make this container a permanent fixture.
Screenshots
Screen.Recording.2026-01-22.at.16.41.03.mov