Client Unique Identifier Source Field Information on RUN3TV
Client Unique Identifiers
An exported table access of registered clients cloud be provided.
|
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 |
|---|
|
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 |
|
text |
GUID randomly generated by the IoT Agent |
Pseudonymously identifies a device instance |
|
|
User Scope |
|
|
|
TO DO |
|
EPOC unix timestamp |
Server updates the field when new records are received |
Timestamp of the last activity of the client. |
|
|
|
|
|
|
TO DO |
n/a |
EPOC unix timestamp |
Server adds a creation field for a new client. |
Timestamp of the created device |
|
|
|
|
|
|
Modification Required |
|
string |
A/344 deviceinfo.deviceId |
A/344 receiver api providing a deviceId,
Not all receivers support providing this information . |
|
|
|
|
|
|
to be included |
|
boolean |
User opted out/in of tracking from the framework |
do-not-track set by the user via the RUN3TV APP true - do not track false - allow tracking |
|
|
|
|
|
|
to be included |
|
integer |
http dnt header |
do-not-track set by the user via the native settings menu 0 - allow tracking 1 - do not track null - no preference has been set. |
|
|
|
|
|
Client Identifiers are being regenerated per domain of the application - R3TV-32: Framework 1.8.1 (TBC) support new ID method inc Validation Tool.Resolved
Multiple clientId’s included for a device.
Action : provide the description of the future effects.