feat(EventBuilder): support overriding timestamp at user property and event level #2246
Conversation
| onChange={e => setTimestamp(e.target.value)} | ||
| onBlur={() => setParamTimestamp(parseInt(timestamp, 10))} | ||
| label="timestamp micros" | ||
| helperText="The timestamp to be applied to the user property. Optional." |
There was a problem hiding this comment.
Could we make it easier for the user to populate this field by giving them a date/time widget where they can select a value and we'll convert it to micros for them?
Many users of the Event Builder aren't necessarily developers, so the whole concept of timestamp micros might be confusing.
| variant="outlined" | ||
| size="small" | ||
| value={timestamp} | ||
| onChange={e => setTimestamp(e.target.value)} |
There was a problem hiding this comment.
Can we warn them if the timestamp is invalid, or show them what their value translates to in terms of a standard date/time format? This would help them visually verify that the value is what they intended.
Also, I've seen confusion from users due to the fact that engagement_time_msec is in millis, but timestamp_micros is in micros. If a user accidentally used a millis value, for example, it'd be great if we could show them that it translated to the beginning of the current epoch. :)
Support overriding timestamp at the user property and event level (already supported at request level).
event validated with request level timestamp
event validated with user property level timestamp
event validated with no user property level timestamp