Issue Summary
When exporting content & settings as JSON, the filename includes the blog name (e.g. myblog.ghost.YYYY-MM-DD.json), which makes it easy to identify the source site.
However, when exporting analytics data as CSV, the filename does not follow the same convention — it lacks the blog name, making it harder to identify which site the data comes from when managing multiple Ghost instances.
Steps to Reproduce
- Go to Settings → export content/settings → JSON file is named with the blog name ✅
- Go to Analytics → export data as CSV → filename does not include the blog name ❌
Expected Behavior
The analytics CSV export should follow the same naming convention as the JSON export, e.g. <site-name>.ghost.analytics.YYYY-MM-DD.csv.
Why
Consistency across exports and easier file management when handling multiple Ghost sites.
Issue Summary
When exporting content & settings as JSON, the filename includes the blog name (e.g.
myblog.ghost.YYYY-MM-DD.json), which makes it easy to identify the source site.However, when exporting analytics data as CSV, the filename does not follow the same convention — it lacks the blog name, making it harder to identify which site the data comes from when managing multiple Ghost instances.
Steps to Reproduce
Expected Behavior
The analytics CSV export should follow the same naming convention as the JSON export, e.g.
<site-name>.ghost.analytics.YYYY-MM-DD.csv.Why
Consistency across exports and easier file management when handling multiple Ghost sites.