Netlify deploy history, on a timeline the whole company can read.
Netlify lists every deploy — but it’s per site, in the dashboard, where only engineers ever look. CoNote will log each publish and rollback onto a shared timeline, beside the campaigns and config changes from the same day.
Published deploy of marketing site (main → 9f2c1a4)
Netlify· 09:41
Spring sale — daily budget raised to $450
Google Ads· 10:12
Finding your history
Your Netlify deploy history: today, and once CoNote is live
The manual way · inside Netlify
Where to find it today
It’s all there — if you go digging:
- 1
Open the site in Netlify
Pick the site whose history you need — each site keeps its deploys entirely separately.
- 2
Open the Deploys tab
Every deploy is listed with its status — Published, Failed, or Skipped — the branch and commit, who triggered it, and the time.
- 3
Spot the published one
Only one deploy is live at a time; the list marks which is Published, so you scroll to find the one users actually saw.
- 4
Open a deploy for the log
Click a deploy to read its build log, or use “Publish deploy” to roll back to an earlier one — which itself becomes a new event to track.
- 5
Stitch it together across sites yourself
More than one site? Repeat for each and reconcile the timestamps by hand — nothing lines deploys up against marketing or analytics.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect Netlify once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Every publish will be waiting — no dashboard access, no site hopping, readable by anyone.
- 2
Jump to the day it moved
Scan the day the number shifted; the publish will be stamped there to the minute.
- 3
See it beside everything else
The deploy will sit next to that day’s campaigns, config changes, and incidents — the cause is obvious.
Sound familiar?
Netlify’s history is perfect — for engineers.
Nadja14:05
Tom14:08
Nadja14:10
Tom14:14
Site by site, scrolling for the published deploy.
It answers “what published to this site?” — never the question the rest of the company has: “what changed across every team around the day the number moved?”
- One site at a time — no single view across sites
- Locked in the dashboard, where marketing and leadership never look
- Never lined up against the campaign or config change from the same day
- Rollbacks blur which version was live when
Once Netlify is connected, the publish will already be on the timeline — “Published deploy of marketing site” at 09:41 — sitting right beside the spike, readable by anyone, on one page.
How it works
Connect once. Then it’ll log itself.
- 01
Add a deploy notification
Point a Netlify deploy notification at CoNote’s webhook URL — no SDK, no build changes, no engineering sprint.
- 02
Every publish logs itself
From then on, each published deploy and rollback lands on the timeline with a readable title — “Published deploy of marketing site” — the moment it happens.
- 03
Read it in context
The deploy sits beside that day’s campaigns, config changes, and incidents. When a metric moves, you scan one page instead of four tools.
What lands on your timeline
- Every published deploy — site, branch, and commit
- Rollbacks, when an earlier deploy is re-published
- A readable title and the moment it went live
In your week
What teams will use it for.
Deploy or campaign — which moved it?
Sign-ups jump on Tuesday. The publish at 09:41 and the ad budget bump at 10:12 sit side by side, so you stop guessing which one to credit.
Give marketing a deploy they can read
No dashboard access, no commit-speak. Marketing sees “Published deploy of marketing site” in plain language, beside their own work.
Catch the rollback that confused everyone
When the page “changes back”, the re-published older deploy is right there on the timeline — dated, so nobody argues about what’s live.
One deploy log across every site
Several sites, one timeline. Every publish lands in the same place, in order.
Side by side
Native history vs. your logbook.
See publishes and rollbacks
Netlify deploy log
CoNote
Readable by marketing and leadership
Netlify deploy log
CoNote
Lined up against campaigns, config, incidents
Netlify deploy log
CoNote
One view across every site
Netlify deploy log
CoNote
Clear record of which deploy was live when
Netlify deploy log
CoNote
Setup
Netlify deploy log
CoNote
On the timeline
The deploy in context.
A publish on its own is a commit hash. Next to the campaign and the drop from the same morning, it’s an explanation.
Tuesday, June 9
Published deploy of marketing site (main → 9f2c1a4)
Netlify· 09:41
Spring sale — daily budget raised to $450
Google Ads· 10:12
Form submissions dropped to zero
Uptime· 11:30
Questions
Netlify deploy tracking, answered.
Open the site and click the Deploys tab — every deploy is listed with its status (Published, Failed, Skipped), the branch and commit, who triggered it, and the time. The list marks which deploy is currently published, and you can re-publish an earlier one to roll back.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch Netlify on automatically the day it ships.
Only once, briefly. Connecting Netlify will be pointing a deploy notification at CoNote’s webhook URL — no SDK and no changes to your build.
It focuses on published deploys — the ones users actually saw — so the timeline reads as a record of what shipped, not every build attempt.
Each published deploy and rollback as a plain-language entry — for example “Published deploy of marketing site (main → 9f2c1a4)” — with the time it happened. CoNote never reads or stores your source code.
Netlify’s log lives in the dashboard, one site at a time, where only people with access ever look. CoNote will put your publishes on a shared timeline next to campaigns, config changes, and incidents.
Only your team. Every entry is scoped to your team, and connecting Netlify won’t expose your site 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