Contentful change history, on a timeline beyond the entry.
Contentful versions every entry — but the history lives entry by entry, in the web app, where only editors and developers look. CoNote will put each publish on one shared timeline, beside the deploys and campaigns from the same day.
Published homepage hero entry — new headline
Contentful· 10:50
Brand campaign launched — $300/day
Google Ads· 12:00
Finding your history
Your Contentful change history: today, and once CoNote is live
The manual way · inside Contentful
Where to find it today
It’s all there — entry by entry:
- 1
Open the space in Contentful
Pick the space and environment you need — content and its history are scoped per environment.
- 2
Open an entry
Each entry shows its status — draft, changed, or published — and which version is currently live.
- 3
Check the entry’s versions
An entry keeps a version history, so you can see and compare past versions and when each was published.
- 4
Open the entry’s activity
The entry’s activity shows who changed it and when — but only for that one entry.
- 5
Stitch the publishes together yourself
There’s no single feed of every publish across the space, and nothing lines them up against your deploys or campaigns — so you reconstruct that by hand.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect Contentful once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Every publish across the space will be in one feed — no entry-by-entry digging.
- 2
Jump to the day it moved
Scan the day a page changed or traffic shifted; the publish will be stamped right there.
- 3
See it beside everything else
The content publish will sit next to that day’s deploys, campaigns, and SEO events — the cause is obvious.
Sound familiar?
Contentful versions the entry — not the day.
Sara09:15
Mia09:19
Sara09:22
Mia09:26
Each entry holds its own history, and only its own.
It answers “what changed in this entry?” — never the question you actually have: “what was published across the space around the day my page or metric moved?”
- Entry by entry — no single feed of every publish
- Per environment — production content history separate from the rest
- Locked in the web app, where marketing and leadership rarely look
- Never lined up against the deploy or campaign from the same day
Once Contentful is connected, the publish will already be on the timeline — “Published homepage hero entry — new headline” — stamped to the minute, next to every other change from that day.
How it works
Connect once. Then it’ll log itself.
- 01
Add a Contentful webhook
Point a Contentful webhook at CoNote — no SDK, no content-model changes, no engineering sprint.
- 02
Every publish logs itself
From then on, each entry publish lands on the timeline with the entry and the moment it went live — “Published homepage hero entry — new headline”.
- 03
Read it in context
The publish sits beside that day’s deploys, campaigns, and SEO events. When a page or metric moves, you scan one page instead of entry by entry.
What lands on your timeline
- Entry publishes — the entry and content type
- The environment it was published to
- The moment it went live, to the minute
In your week
What teams will use it for.
Content publish broke the page
The site changes with no deploy. The entry publish is on the timeline at the minute it went live — the change you’d otherwise hunt entry by entry.
Did content lead or follow the campaign?
The publish sits next to the ad launch, so you can confirm the campaign content went live first — no guessing.
Give marketing a publish log they can read
No Contentful access needed. Everyone sees “Published homepage hero entry” in plain language, beside the rest of the company’s work.
One feed across every editor and type
Many entries, many editors, one timeline. Every publish lands in the same place, in order.
Side by side
Native history vs. your logbook.
See entry publishes
Contentful entry history
CoNote
A single feed of every publish
Contentful entry history
CoNote
Lined up against deploys, campaigns, SEO
Contentful entry history
CoNote
Readable by marketing and leadership
Contentful entry history
CoNote
One view across environments
Contentful entry history
CoNote
Setup
Contentful entry history
CoNote
On the timeline
The publish in context.
An entry publish on its own is a version bump. Next to the campaign and the bounce-rate change from the same day, it’s an explanation.
Tuesday, June 9
Published homepage hero entry — new headline
Contentful· 10:50
Brand campaign launched — $300/day
Google Ads· 12:00
Homepage bounce rate climbed 14%
Uptime· 13:10
Questions
Contentful change tracking, answered.
Open an entry — it shows its status (draft, changed, published), a version history you can compare, and an activity log of who changed it and when. This is per entry; there’s no single feed of every publish across the space.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch Contentful on automatically the day it ships.
Only once, briefly. Connecting Contentful will be adding a webhook — no SDK and no changes to your content model.
No — it logs publishes, the moment content actually goes live, not every draft save, so the timeline stays a record of what reached your site.
Each entry publish as a plain-language entry — the entry, its content type, the environment, and the time it went live. CoNote reads the events you send it; it never changes your content.
Contentful’s history is entry by entry, per environment, in the web app. CoNote will put every publish on one shared timeline next to your deploys, campaigns, and SEO events — so the team can line a content change up against the day a metric moved.
Only your team. Every entry is scoped to your team, and connecting Contentful won’t expose your space to anyone outside it.
Keep digging
Track the rest of your stack.
Open the logbook.
Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.
Start your logbook