We have observed that the Forge event payloads for Confluence page and blog post events (specifically avi:confluence:viewed:page
, avi:confluence:updated:page
, and their blog equivalents) do not include a timestamp
field that indicates when the event occurred.
In comparison, the same events in Atlassian Connect include a timestamp
field at the root level, which is crucial for event tracking and analytics use cases.
For example, in the Connect page viewed
event:
"timestamp": 1749544536154
Whereas, in the Forge avi:confluence:viewed:page
event, this field is completely missing. This makes it difficult to determine the precise time the view or update event occurred, especially when handling large volumes of activity data across spaces.
Additionally, while the createdDate
is available in Forge events for page/blog creation, there’s no equivalent field for viewed or updated actions.
This discrepancy reduces parity between Connect and Forge event payloads and limits observability and event correlation across systems.
I have created ECOHELP-73609 ticket for tracking the same.
We request that the timestamp
field (or equivalent) be added to all Forge Confluence events to maintain consistency and enable accurate temporal tracking.
Cheers
Ajay