CivitAI Tracker v10.0 — Collection Tracking

This release adds a new collection tracking layer to CivitAI Tracker.

The tracker can now detect when your images are added to collections and correlate those events with known images and posts in the local database. This expands the dashboard beyond basic post/reaction statistics and adds a better view of which images are being saved by other users.

Added

• Added collection tracking for images.
• Added incoming content engagement storage.
• Added a new local database table: content_engagement_events.
• Added image-to-post correlation for collection events.
• Added a new Collections section to the dashboard.
• Added collection-focused summaries:
• Added to collections
• Affected images
• Affected posts
• Last collection event
• Added collection event tables:
• Recent collection adds
• Top posts by collection adds
• Top images by collection adds

Changed

• Dashboard now includes collection-focused analytics without duplicating the existing reaction statistics.
• Collection data is presented as user-facing content analytics, not as raw internal transaction data.
• Documentation now clearly explains API key behavior and limited public mode.

API Key / Limited Public Mode

The tracker can start and collect basic public statistics without an API key.

However, without an API key, the tracker runs in limited public mode:

• Collection tracking is unavailable.
• User-scoped transaction data is unavailable.
• Restricted / PG-13+ / NSFW posts may be missing or incomplete.
• Dashboard statistics may not represent the full account history.

For full functionality, including collection tracking and better restricted-content visibility, provide a CivitAI API key in Settings.

Notes

• Collection tracking uses authenticated account data internally.
• API keys are stored locally according to the selected configuration method.
• Private runtime files are excluded from the release package:
• config.json
• api_key.txt
• *.db
• logs/
• csv/
• dashboard.html
• runtime_status.json

Recommended upgrade path

1. Download and extract the new release.
2. Copy or recreate your config.json.
3. Make sure your API key is configured if you want collection tracking.
4. Run the tracker once.
5. Open dashboard.html and check the new Collections section.

Status

This version has been tested in both source/script mode and EXE mode.