Skip to main content
The Changelog provides a chronological timeline of every content operation in your workspace — who changed what, when, and what impact it had. Navigate to Reports → Changelog to access this report.

Reading the Timeline

The changelog shows events in reverse chronological order. Each entry includes:
  • Timestamp — When the event occurred
  • Event type — Created, updated, published, status changed, etc.
  • Asset — Which content asset was affected (linked to the asset detail view)
  • Author — Which team member performed the action
  • Summary — What specifically changed (e.g., “Headline updated”, “Published to WordPress”, “CTA replaced”)

Event Types

EventIconDescription
Created+New asset added to the registry
Updated~Content revised, fields edited, or AI regeneration applied
PublishedContent pushed to WordPress or other platform
Status ChangedDraft → Review → Published transitions
OptimizationScore change, objective assignment, or scoring rule update
Deleted×Asset removed from the registry

Filtering

Narrow the timeline using:
  • Content type — Show only blog posts, only landing pages, etc.
  • Author — See what a specific team member changed
  • Date range — Focus on a specific week, month, or quarter
  • Event type — Show only publications, only revisions, etc.
  • Asset — See the full history of a single content piece

Use Cases

Audit Trail

When you need to know who changed what and when — for compliance, team accountability, or debugging an unexpected change.

Regression Investigation

If performance drops suddenly on a content asset, check the changelog to see what changed around that time. Correlate with the Revision Impact report for metric-level details.

Team Productivity

Track publishing velocity across the team:
  • How many pieces were published this week vs. last week?
  • Who’s generating the most content?
  • Are assets sitting in draft status too long?

Stakeholder Reporting

Export a filtered view (e.g., “all publications this month”) to share with stakeholders or clients as a content operations summary.