🐞 fix(sticky): Updating "sticky" view event emission behavior#174
Merged
Charles Hudson (phobetron) merged 1 commit intomainfrom Mar 12, 2026
Merged
Conversation
Charles Hudson (phobetron)
requested a review
from Alex Freas (akfreas)
as a code owner
Improve sticky view tracking so sticky payloads are sent only until the first successful personalization response, then suppressed for later updates on the same rendered instance/element. Also update core view tracking to always emit analytics for sticky views while still returning personalization data when available. - React Native: propagate `sticky` metadata through viewport tracking, guard in-flight sticky sends, reset dedupe state when identity changes, and add tests for success dedupe, retry behavior, and per-instance scope - Web: pass tracked elements through timed detectors and dedupe sticky sends per element with a `WeakSet`, with matching tests for success/retry/instance [[NT-2733](https://contentful.atlassian.net/browse/NT-2733)]
Charles Hudson (phobetron)
force-pushed
the
NT-2733_sticky-view-behavior-update
branch
from
cacb469 to
3079ef9
Compare
| const stickyInFlightRef = useRef(false) | ||
| const stickyIdentityRef = useRef<string | null>(null) | ||
|
|
||
| const stickyIdentity = `${componentId}::${experienceId ?? ''}::${variantIndex}::${sticky === true ? '1' : '0'}` |
Collaborator
There was a problem hiding this comment.
I think this should probably be extracted to a function or made cleaner somehow
Collaborator
Author
There was a problem hiding this comment.
What standard should we follow to ensure such a line would be "clean"? To me it appears to be a specially-formatted disambiguation ID, assembled using string interpolation, that would only add more boilerplate to move to a function.
Alex Freas (akfreas)
approved these changes
Mar 12, 2026
Charles Hudson (phobetron)
deleted the
NT-2733_sticky-view-behavior-update
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Improve sticky view tracking so sticky payloads are sent only until the first successful personalization response, then suppressed for later updates on the same rendered instance/element.
Also update core view tracking to always emit analytics for sticky views while still returning personalization data when available.
stickymetadata through viewport tracking, guard in-flight sticky sends, reset dedupe state when identity changes, and add tests for success dedupe, retry behavior, and per-instance scopeWeakSet, with matching tests for success/retry/instance[NT-2733]