How to troubleshoot Lookup Table return <not set>

How to troubleshoot Lookup Table return <not set> | Mixpanel Community

2 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Hi Yanisa S., 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
kapa.ai
APP
·
·
To troubleshoot Lookup Tables returning <not set> in Mixpanel, you can follow these steps: 1. Check for falsy values: Mixpanel treats null values as <not set> in the UI. Make sure your Lookup Table doesn't contain null values for the properties you're trying to use. Falsy Values documentation provides more details on how Mixpanel handles null and undefined values.2. Verify the join key: Ensure that the join key (usually the first column in your CSV) matches exactly with the event property you're using to join the Lookup Table. Any mismatch will result in <not set> values.3. Review CSV format: Make sure your CSV file is properly formatted. The first row should be the header with unique column names, and the first column should contain unique values for joining. Here's an example of a correct CSV format:
c994bb,Drake,Pop,True,Hotline Bling,2015-10-18T22:00:00Z d8d949,Gipsy Kings,Flamenco,False,Bamboleo,1987-07-12T05:00:00Z a43fb8,Daft Punk,House,False,Aerodynamic,2001-03-12T07:30:00Z ```LBKSLBKS [How do I upload a Lookup Table?](https://docs.mixpanel.com/docs/data-structure/lookup-tables#how-do-i-upload-a-lookup-table)LBKS4. Check for data types: Ensure that the data types in your Lookup Table match the expected types in Mixpanel. For example, make sure dates are in the correct format (RFC3339 timestamps).LBKS5. Verify the mapping: If you've created the Lookup Table globally using Lexicon, make sure it's correctly mapped to the right event or user profile property. Only project Owners and Admins can create global Lookup Table mappings.LBKS6. Consider local vs. global mapping: If you've uploaded the Lookup Table locally within a report, remember that this mapping is only available in that specific report and won't be accessible in other reports.LBKSIf you're still experiencing issues after checking these points, you may need to reach out to Mixpanel support for further assistance, as the provided knowledge sources don't contain more specific troubleshooting steps for this particular issue.
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
APP
·
·
Hi Yanisa S., 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
kapa.ai
APP
·
·
To troubleshoot Lookup Tables returning <not set> in Mixpanel, you can follow these steps: 1. Check for falsy values: Mixpanel treats null values as <not set> in the UI. Make sure your Lookup Table doesn't contain null values for the properties you're trying to use. Falsy Values documentation provides more details on how Mixpanel handles null and undefined values.2. Verify the join key: Ensure that the join key (usually the first column in your CSV) matches exactly with the event property you're using to join the Lookup Table. Any mismatch will result in <not set> values.3. Review CSV format: Make sure your CSV file is properly formatted. The first row should be the header with unique column names, and the first column should contain unique values for joining. Here's an example of a correct CSV format:
c994bb,Drake,Pop,True,Hotline Bling,2015-10-18T22:00:00Z d8d949,Gipsy Kings,Flamenco,False,Bamboleo,1987-07-12T05:00:00Z a43fb8,Daft Punk,House,False,Aerodynamic,2001-03-12T07:30:00Z ```LBKSLBKS [How do I upload a Lookup Table?](https://docs.mixpanel.com/docs/data-structure/lookup-tables#how-do-i-upload-a-lookup-table)LBKS4. Check for data types: Ensure that the data types in your Lookup Table match the expected types in Mixpanel. For example, make sure dates are in the correct format (RFC3339 timestamps).LBKS5. Verify the mapping: If you've created the Lookup Table globally using Lexicon, make sure it's correctly mapped to the right event or user profile property. Only project Owners and Admins can create global Lookup Table mappings.LBKS6. Consider local vs. global mapping: If you've uploaded the Lookup Table locally within a report, remember that this mapping is only available in that specific report and won't be accessible in other reports.LBKSIf you're still experiencing issues after checking these points, you may need to reach out to Mixpanel support for further assistance, as the provided knowledge sources don't contain more specific troubleshooting steps for this particular issue.
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.