Added timestamp to wzrk.id #201
Merged
Conversation
This file contains 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
|
@PraveenCTzen Please update the description with the below template - JIRA Issue: JIRA_TICKET_ID |
|
@PraveenCTzen Also test if the notification viewed and clicked events are getting raised with the right information. |
Yes notification viewed and clicked events are getting raised properly |
AmeeParsania
approved these changes
Mar 28, 2024
KambleSonam
approved these changes
Apr 2, 2024
kkyusuftk
approved these changes
Apr 2, 2024
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.
JIRA Issue: WEB-2664
Background
In this PR, we address an issue encountered when multiple web push notifications with distinct deeplinks were sent from the same campaign. Previously, clicking on an older notification redirected users to the latest deeplink instead of the corresponding one, causing inconsistencies.
Implementation
This fix ensures that each notification correctly redirects to its respective deeplink.
Testing Strategy
Successfully tested the solution using a campaign that sends out varied push notifications, each with a distinct deeplink tailored to different profile properties. Verified that all push notifications redirect correctly. Assistance is now required to replicate and test these scenarios with API campaigns.
Impact Areas
The impacted areas primarily include scenarios involving web push notifications with deeplinks. The issue arises when a campaign includes multiple push notifications, each with its own unique deeplink. This setup may lead to inconsistent redirection.