Skip to main content

Troubleshooting Mixpanel connectivity

Connect docs via MCP
TL;DR

Learn about troubleshooting Mixpanel connectivity, including authentication, service-account permissions, and description write-back.

Why does test authentication fail?​

If the connection test fails when you provide your credentials, check the following:

  • The Service Account Username and Service Account Secret must be a valid, unexpired Mixpanel service account pair. The secret is shown only once when the account is created; if you didn't save it, create a new service account.
  • The service account must have access to the project identified by the Mixpanel Project ID you entered.
  • The Atlan Base URL must be your full tenant URL, for example https://your-tenant.atlan.com, with no trailing path.
  • The Atlan API Key must be a valid, unrevoked token. See setting up Mixpanel for the permissions it needs.

Why is my Mixpanel catalog incomplete after crawl?​

The crawl only returns the Lexicon entries the service account can see. If events, event properties, or user properties are missing:

  • Confirm the service account has access to the correct project and a role with project-wide Lexicon read access.
  • Confirm the entries exist in the project's Lexicon in Mixpanel—only Lexicon-registered events and properties are cataloged, not ad-hoc events that have never been added to Lexicon.

Why aren't my descriptions appearing in Mixpanel?​

Description write-back runs on the app's daily cadence, so a description you certify in Atlan appears in Lexicon after the next write-back run, not immediately. If descriptions still don't appear:

  • Confirm the Mixpanel service account has a role that can edit Lexicon—a read-only role catalogs metadata but can't write descriptions back. See creating a Mixpanel service account.
  • Confirm the description was set on the MixpanelEvent or MixpanelEventProperty asset in Atlan—write-back is keyed to those asset types.

What are known limitations of Mixpanel connector?​

Atlan currently doesn't support the following:

  • Write-back is descriptions only. Owners, tags, and status are set in Atlan for governance but aren't written back to Mixpanel Lexicon in this release.
  • Warehouse lineage. Lineage Process edges from upstream warehouse tables (Snowflake and others) into Mixpanel events aren't emitted in this release.
  • Individual user profiles. Per-user profile records are transactional, PII-bearing state and aren't cataloged. Atlan governs the profile-property schema, not the rows.
  • Reports, cohorts, and lookup tables aren't cataloged in this release.