Missing timestamp field in Forge Confluence Events for Page Viewed and Page Updated

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

2 Likes

Hi @ajay,

We’re planning to add the event creation datetime in some form (probably ISO) into all events very soon.

Created date is available for all content events, including :viewed. You can read it from content.history.createdDate field.

We’re also planning to add a version number, and, for :updated events, an update trigger and suppress notifications flag.

Please let us know if you’re interested in any other fields.

Thanks,
Roman

1 Like

Thanks for the update, @RomanToropov. We’ll wait for the creation datetime to become available.

We also noticed that the trashed and restored events don’t appear to be working yet, even though the changelog indicates they have been released:

Hi @ajay, trashed and restored events were indeed released last week. I can receive them in my test app. Please make sure that your app has write:confluence-content scope to receive trashed events, as per the documentation: https://developer.atlassian.com/platform/forge/events-reference/confluence/#pages--live-docs--and-blog-posts. We may remove this requirement in the future.

Is there a particular use case where you don’t receive trashed and restored events?

Thanks,
Roman

This topic was automatically closed after 30 days. New replies are no longer allowed.