IMPROVEMENT: Added meta.queueTimeMillis to network request to record time between event creation and sent #1416
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
carterworks
reviewed
Dec 16, 2025
jonsnyder
reviewed
Dec 16, 2025
packages/core/test/integration/specs/Command Logic/queueTimeMillis.spec.js
Show resolved
Hide resolved
…hen request is sent
jonsnyder
approved these changes
Jan 7, 2026
Contributor
jonsnyder
left a comment
jonsnyder
left a comment
There was a problem hiding this comment.
Looks good. Be sure to manually test it with an assurance session to make sure the queuedTimeMillis is applied to the event when xdm.timestamp is deleted.
Spencer-Smith
changed the title
carterworks
approved these changes
Jan 9, 2026
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.
Description
Removes event timestamp during event finalization and adds a
metaproperty to determine the amount of time the event was enqueued.Related Issue
Jira
Motivation and Context
Timestamps from the WebSDK are dependent on user device settings and so can be inaccurate. In order to avoid TIME DRIFT in Konductor, we should no longer send event timestamps in the SDK. Instead, Konductor will insert the timestamp when the request is received. Because send event commands can be queued (while they wait for script load, consent, identity, etc.), we need to track the delta between when the command is enqueued and when it is actually sent to determine in Konductor when the event occurred.
Screenshots (if appropriate):
N/A
Checklist: