In Mixpanel version v2.52.0, is the utm_id not registered as a super property?
Hi jtw, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> đź‘‹
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
Based on the knowledge sources provided, I can answer your question about Mixpanel version v2.52.0 and the utm_id
parameter.According to the Mixpanel SDKs: Javascript documentation, the JavaScript library automatically adds UTM parameters to events fired from a page load, including utm_id
. The documentation states:"The JavaScript library will automatically add any UTM parameters (utm_source
, utm_campaign
, utm_medium
, utm_term
, utm_content
, utm_id
, utm_source_platform
, utm_campaign_id
, utm_creative_format
, utm_marketing_tactic
) present on the page to events fired from that page load."This information suggests that utm_id
is indeed registered as a super property in Mixpanel version v2.52.0, along with other UTM parameters.However, it's worth noting that the documentation also mentions a new option introduced in this version::LBKS"Note:: UTM parameters are by default persisted as Super Properties. To disable this UTM persistence, use the SDK initialization option {stop_utm_persistence: true}
(refer to our Release Notes in GitHub)."This means that while utm_id
is registered as a super property by default, there is now an option to disable the persistence of UTM parameters as super properties in version v2.52.0.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.