Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start extracting true_tstamp from querystring #1968

Closed
alexanderdean opened this issue Aug 17, 2015 · 3 comments
Closed

Start extracting true_tstamp from querystring #1968

alexanderdean opened this issue Aug 17, 2015 · 3 comments

Comments

@alexanderdean
Copy link
Member

Quick points:

  • true_timestamp is for when the instrumentor knows the real timestamp for the events being sent
  • true_timestamp != device_created timestamp
  • There should be a flag in a given tracker to specify whether a user-specified timestamp should be the true timestamp or device-created
  • If true_timestamp is set, this should be used for the derived timestamp
@alexanderdean alexanderdean added this to the Release 71 [HAD] Bird TBC milestone Aug 17, 2015
@fblundun
Copy link
Contributor

Would this be a new field in atomic.events, or would the true timestamp just go directly into the derived_tstamp field?

@alexanderdean
Copy link
Member Author

I think it would be a new field and fed into derived_tstamp

@alexanderdean
Copy link
Member Author

Note on this:

There should be a flag in a given tracker to specify whether a user-specified timestamp should be the true timestamp or device-created

When a tracker has an event builder pattern, we can make the specification of true timestamp versus device-created on a per track() basis, which will be more elegant.

@alexanderdean alexanderdean changed the title Placeholder for adding true_timestamp Start extracting true_tstamp from querystring Sep 5, 2016
oguzhanunlu pushed a commit to snowplow/common-enrich that referenced this issue May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants