Timestamp Source Field Information on RUN3TV [2.1.0]
Timestamp
|
Status |
Data Layer Field |
Data type |
Where is the data coming from |
Description |
Data Example |
GTM Variable |
GA4 Dimension |
Data Studio |
IoT Agent Field Name |
|---|---|---|---|---|---|---|---|---|---|
|
REQUIRED |
|
EPOC unix timestamp in UTC |
Browser date time field in EPOC UTC (getTime() javascript) |
Records current time of the client |
|
|
|
Modified |
clientDT |
|
to be included |
|
Browser date time field including localization. |
Records timezone of the user |
|
|
|
|
clientISODT |
|
|
REQUIRED |
|
timestamp |
Browser date time field and deduct |
Describes the current time of the user in their respective zone. (Calculation to be done using the UTC offset and clientDT) |
|
|
|
|
clientDTZ |
|
REQUIRED |
|
string |
|
The pre-defined list includes timezone classification geographically across the United States |
America/Denver |
|
|
|
|
|
REQUIRED |
|
integer |
Browser’s getTimezoneOffset() to provide the number of mintues. |
Describes the gap between UTC timestamp value and timestamp of the client Zone in the number if minutes. Negative is behind UTC. |
|
|
|
|
utcOffset |
|
To Consider |
|
Receiver clock from the broadcast chain |
Records current time from the Broadcast Chain |
|
|
|
|
|
|
|
to be included |
|
|
Server stamps the real time data |
Server provides this value on all inbound posts |
|
|
|
|
|
Consider that the browser timestamp can be altered by the settings menus on most devices including the timezones
= not applicable
Heartbeats
|
Status |
Data Layer Field |
Data type |
Where is the data coming from |
Description |
Data Example |
GTM Variable |
GA4 Dimension |
Data Studio |
IoT Agent Field Name |
|
To Consider |
heartBeat |
Boolean |
Framework enabling posting |
Indicates that the application is still running. (Considering every 15mins) |
|
|
|
|
|