Mixpanel: Javascript SDK UTM persistence behavior change
Timeline of updates
- resolved
Version v2.51.0 of our Javascript SDK included a change to the default behavior of UTM tracking which disabled the persistence of UTM properties as super properties. This resulted in events only having the UTM information tracked on them if that UTM information was present on the URL the event was triggered from unless the initialization option {stop_utm_persistence: false} was set. We've reverted this change so that UTM information is persisted as a super property in v2.52.0 which was released 6/7/2024 12PM PT. We recommend the {stop_utm_persistence: true} initialization option if you use multi-touch attribution models in Mixpanel. Please refer to our attribution documentation (https://docs.mixpanel.com/docs/features/attribution (opens in new tab)) for how to properly attribute data sent in during this time or reach out to our support team with further questions.
From Mixpanel’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.mixpanelstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Mixpanel, started 2024-05-29 04:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Javascript SDK UTM persistence behavior change
- Vendor
- Mixpanel
- Date
- URL
- https://rewindex.com/company/mixpanel/incidents/z703x0lmct03
Mixpanel profileRecent Mixpanel incidentsAll outages on May 29, 2024Mixpanel in May 2024MarkdownJSON