Notification Read
Object Type / Action: Object Type: 12 (Notification) / Action: 12 (Read)
Total records analysed: 50,000 (out of 294,000 total)
Note on Account entity: In ExpoPlatform, Visitors, Team Members, and Speakers are all types of Accounts — Team Member and Speaker are roles that an Account can hold. The "Account" match group below consolidates all three into a single de-duplicated count. This is worth noting as the terminology can vary across the events industry.
Note on match percentages: Each field's values are checked independently against all entity ID sets. Since ID ranges overlap across entity types, a single value may match more than one entity — causing percentages to add up to more than 100%. The entry marked ← strongest indicates the highest match rate and is the intended entity for that field.
Note on
additional_id: Mirrors the same entity distribution asaccount_id, suggesting it also refers to the account that performed the action (the notification reader).
|
field_name |
type |
example |
description |
entity match |
|---|---|---|---|---|
|
|
|
|
Time of interaction in UTC |
— |
|
|
|
|
Always 12 for notification (from dictionary) |
— |
|
|
|
|
Always 12 for read (from dictionary) |
— |
|
|
|
|
ID of the account that read the notification |
Account: 79.1% ← strongest | Owner: 19.9% | Exhibitor: 3.5% |
|
|
|
|
Internal notification ID — not mapped to a known entity in the reference dataset (range: 7,616,666–10,171,261) |
— |
|
|
|
|
ID of the account that read the notification — mirrors |
Account: 79.3% ← strongest | Owner: 19.7% | Exhibitor: 3.5% |
|
|
|
|
Always |
— |
|
|
|
|
Always |
— |
|
|
|
|
Exhibitor ID of the reading account. Can be |
Exhibitor: 100.0% ← strongest | Product: 4.5% | Account: 3.1% |
|
|
|
|
Exhibitor ID associated with the notification context. Can be |
Exhibitor: 100.0% ← strongest | Product: 4.3% | Account: 2.9% |
|
|
|
|
User agent string of the client |
— |