Mixpanel Super Properties and Default Properties: What They Do and When They Hurt

Super properties are one of those Mixpanel features that feel like magic in week one and become a mystery by month six. You set them once, they ride along on every event, and then one day you notice a plan_type of trial attached to someone who upgraded three months ago.

Used well, they save hundreds of lines of tracking code. Used carelessly, they spread stale data across your whole project.

What super properties are

Mixpanel defines super properties as global event properties you set once and that then attach to every event the SDK sends. Instead of adding app_version or plan_type to every track() call, you register it once.

mixpanel.register({
  plan_type: 'pro',
  app_version: '4.2.0'
});

mixpanel.track('report_exported');
// Sent with plan_type and app_version automatically

In the browser, they’re stored in the Mixpanel cookie for your domain, which by default lasts 365 days. That persistence is both their strength and their main risk.

The methods you need to know

  • register() sets super properties and overwrites existing values.
  • register_once() sets them only if they don’t exist yet. Mixpanel suggests it for values like initial referrer or first campaign, which should never change.
  • unregister() removes one super property.
  • reset() clears all super properties along with the user’s stored identity. It’s what you call on logout.

Newer versions of the JavaScript SDK also accept a persistent: false option on register(), which keeps the property only for the current page load instead of saving it to the cookie. That’s useful for page-level context you don’t want leaking into the next session.

Default properties: what Mixpanel adds for you

On top of your own super properties, the client SDKs automatically attach default properties: browser, operating system, device, screen size, current URL, referrer, city and country, and more. Mixpanel lists them in its default properties reference.

Two points matter for implementation:

  • Default properties come from the client. If you track from a server, you lose them and have to add the important ones yourself (see post 1).
  • UTMs are persisted as super properties by default in the JavaScript SDK. That’s why post 5 recommends turning persistence off for attribution.

When super properties are the right tool

I use them for context that is true for every event in a session and changes rarely:

  • App or release version
  • Platform (web, ios, android)
  • Logged-in state
  • Account or workspace ID in B2B products
  • Experiment variant, if you set it at session start
  • The user’s ID, which Mixpanel recommends as a troubleshooting aid for identity issues

When they hurt

The problems all come from the same root cause: a super property is a snapshot, and snapshots go stale.

  • Values that change mid-life. Plan type, subscription status, cart value. If you register plan_type: trial and forget to update it on upgrade, every future event carries the wrong plan.
  • Values that belong to one event. Order ID or search query as a super property means every later event inherits it.
  • Shared devices. Without reset() on logout, the next person inherits the previous user’s super properties.
  • Server-side events. Super properties live in the browser. Server events don’t get them unless you send them explicitly, so reports mixing client and server events can show blanks.

Best practices

  1. Keep a short, documented list of super properties in your tracking plan, with who sets them and when they update.
  2. Update them at the moment the underlying value changes. Plan upgrade handler? Call register() there.
  3. Use register_once() for anything “first”: first referrer, first campaign, signup date.
  4. Mirror changing user attributes as profile properties too. For “what plan is this user on now?”, a profile property is often the better source; the super property records the plan at the time of each event.
  5. Call reset() on logout.
  6. Use the same snake_case naming as your other properties, and never prefix with $ or mp_.

How to audit super properties

Open a user’s activity feed in Mixpanel and expand a few recent events. Look for properties you don’t recognize, values that look outdated, or one-off values (an order ID on a page view) that shouldn’t be global. Then search your codebase for register( and check every call against your tracking plan.

Final thoughts

Super properties are a convenience, not a database. Keep the list small, update values at the moment they change, and reset on logout. Your reports will thank you.

Sources

GET EXPERT ANALYTICS HELP

Need help getting reliable answers from Mixpanel?

Tell us about your tracking, funnels, retention, or reporting challenge. Optizent can help you implement, audit, and use Mixpanel with confidence.

We will use these details to respond to your request. Please do not include passwords, account access, or customer data.