Troubleshooting Undefined Result in UTM Customer Properties
why would I be getting "undefined" as a result when attributing by a customer property consisting of 4 different UTM's?
why would I be getting "undefined" as a result when attributing by a customer property consisting of 4 different UTM's?
Hi Bradley A., 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
You might be getting "undefined" as a result when attributing by UTM properties in a funnel for several reasons: 1. Property not defined at selected step: When using per-step attribution in funnels, if you select a specific step where the UTM property wasn't defined, you'll see "undefined" values. As mentioned in the documentation: > "You can choose to attribute a property value from any step to the whole funnel by selecting the step number. Note that with this option you may see an 'undefined' null value for the property, as this option is not tied to when the property value was defined." Mixpanel Funnels Documentation2. UTM parameters not present: If the user didn't arrive through a campaign with UTM parameters for that particular step, the value would be undefined.3. Case sensitivity issues: UTM tracking in Mixpanel is case sensitive and should be formatted in lowercase as shown in the documentation. If your UTM parameters are in a different case format, they might not be properly tracked. Mixpanel JavaScript SDK Documentation4. Server-side implementation challenges: If you're using server-side tracking, UTM parameters need to be manually extracted from the request, which could lead to undefined values if not properly implemented. Server-Side Attribution Documentation5. Attribution model settings: If you're using the recommended modern behavior with stop_utm_persistence: true, UTM parameters won't persist across events as super properties, which could result in undefined values in certain contexts. UTM Tracking DocumentationTo troubleshoot this issue, I recommend checking which attribution model you're using in your funnel (First Step Defined, Last Step Defined, or specific step) and verifying that the UTM parameters are actually present and properly formatted at the step you're attributing from.
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.
kapa.ai I am not using a funnel, I am getting these results in an Insights report
Let me check the knowledge base for you again. One moment! đ
I understand you're seeing "undefined" values in an Insights report rather than a Funnel report when attributing by UTM properties. This changes the context of the issue.In Insights reports, "undefined" values can appear for several reasons: 1. Missing UTM parameters: If users didn't arrive through a campaign with the specific UTM parameters you're analyzing, they would show as "undefined" in your breakdown. This is common when some users come through direct traffic or sources without UTM tagging.2. Case sensitivity: UTM tracking in Mixpanel is case sensitive and should be formatted in lowercase. As noted in the documentation:
"â ī¸UTM tracking is case sensitive and should be formatted in lowercase as shown in the examples above." Mixpanel JavaScript SDK Documentation3. Data discrepancies: When analyzing reports, it's important to check if there are any filters that might be affecting your results. As mentioned in the debugging documentation: "A good way to start is to remove all filtering from the reports to check if the underlying data is the same, then re-add them and see when the discrepancy occurs." Mixpanel Debugging Documentation4. Custom bucketing: If you're using custom bucketing for UTM sources, check if your configuration is correctly handling all possible values. You might need to adjust your custom property settings to properly categorize all UTM values. Insights DocumentationTo troubleshoot this issue in Insights, I recommend: - Verifying that UTM parameters are being properly tracked - Checking if the UTM properties exist for the events you're analyzing - Considering using custom properties to handle UTM grouping if you're combining multiple UTM parametersIf you're using a custom property that combines multiple UTM parameters, ensure that your property definition handles cases where some UTM parameters might be missing.
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.