Skip to content

Conversation

@Sewer56
Copy link
Member

@Sewer56 Sewer56 commented Feb 2, 2026

Summary

This PR adds Mixpanel analytics events to track the collection drafting workflow in Vortex.

Changes

  • Added 3 new Mixpanel events:
    • collection_drafted - Fired when a user creates a new collection draft
    • collection_draft_uploaded - Fired when a user uploads a new collection draft to Nexus Mods for the first time
    • collection_draft_updated - Fired when a user uploads an update to an existing collection

Testing

Prerequisites

1. Enable Telemetry

Telemetry must be enabled to test events:

  1. Open Vortex
  2. Go to SettingsVortex
  3. Check "Allow this app to collect usage data to improve your experience"
  4. Ensure you're logged into Nexus Mods (required for analytics)

Note: Telemetry was off on my machine. Not sure if defaults to off in development builds. AFAIK a consent dialog appears on first login, but I don't remember it 😅

2. Check DNS/Network

Important: DNS blockers like AdGuard Home, Pi-hole, or browser extensions may block Mixpanel events.

Whitelist these domains:

  • *.mixpanel.com
  • *.mxpnl.com

That's what I had to do on my end; was caught offguard.

How to Trigger Each Event

collection_drafted

Fires when creating a new collection draft:

Creation Method Steps
empty Collections tab → "Create New Collection" → Choose empty → Name it
from_profile Profiles tab → Select profile → "Create Collection from Profile"
quick_collection Use Quick Collection feature → Select mods → Complete workflow

collection_draft_uploaded

Fires on first-time upload:

  1. Create a collection (any method above)
  2. Configure with mods/rules
  3. Click Export to Nexus / Upload Collection
  4. Must be a new collection (no collectionId)

collection_draft_updated

Fires when uploading an update:

  1. Open previously uploaded collection
  2. Make changes (add/remove mods, update rules)
  3. Click Export to Nexus / Upload Collection
  4. Collection must already have a collectionId

Verification

  1. Run Vortex: yarn start
  2. Open Mixpanel → switch to Nexus Mods - Development project (top-left)
  3. Go to Events in sidebar
  4. Trigger actions in Vortex
  5. Verify events appear with correct properties

Files Modified

  • src/extensions/analytics/mixpanel/MixpanelEvents.ts - New event classes
  • extensions/collections/src/index.ts - Track empty collection
  • extensions/collections/src/util/transformCollection.ts - Track profile/quick collections
  • extensions/collections/src/collectionExport.ts - Track uploads/updates
  • src/util/api.ts - Export new events
  • etc/vortex_devel.api.md - API docs

@Sewer56 Sewer56 requested a review from a team February 2, 2026 12:48
@Sewer56 Sewer56 marked this pull request as ready for review February 2, 2026 12:49
@insomnious insomnious self-requested a review February 2, 2026 15:59
Mixpanel is already initialized with the user id, so sending it on individual events causes duplicate data.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants