Troubleshooting Mixpanel Event Queries with projectKey Issues | Mixpanel Community

Mixpanel Community Icon

Troubleshooting Mixpanel Event Queries with projectKey Issues | Mixpanel Community

kapa.ai
APP
·
·
Based on the information you've provided, there are a few potential reasons why you're not seeing the expected results in your API queries. Let's go through some possible issues and solutions: 1. Date Range: The date range you're querying (2014-10-01 to 2014-10-31) is quite old. Make sure you're querying a date range that matches when your events were actually sent. If your events are more recent, adjust the from_date and to_date parameters accordingly. 2. Event Name: Ensure that "My Event" is exactly the name of the event you're trying to query. Event names in Mixpanel are case-sensitive. 3. Property Name: Confirm that "projectKey" is the exact name of the property you're querying. Property names are also case-sensitive. 4. Inactive Events and Properties: Mixpanel hides events and properties that haven't been fired in the last 30 days from dropdown menus, but they should still be queryable via API. However, it's worth checking if your event or property might be inactive. As mentioned in the [Mixpanel documentation](https://docs.mixpanel.com/docs/tracking-best-practices/debugging#check-for-hidden-events-and-properties): "Mixpanel's report dropdown menus hide events that have not been fired within the last 30 days. [...] Event properties and property values that have not been sent to your project in the last 28 days will also be hidden from dropdowns." 5. Hidden Events or Properties: Check if the event or property might be hidden in Lexicon. As per the [Mixpanel documentation](https://docs.mixpanel.com/docs/tracking-best-practices/debugging#check-for-hidden-events-and-properties): "Project Owner and Admin users can hide events, event properties, and user profile properties in your Mixpanel project through Lexicon. Check Lexicon to review if the event or property may be hidden." 6. API Host: Ensure you're using the correct API host for your project's data residency. According to the [Mixpanel documentation](https://docs.mixpanel.com/docs/tracking-best-practices/debugging#ensure-you-are-using-the-api-host-that-matches-your-projects-data-residency): - US Data Residency: api.mixpanel.com (default) - EU Data Residency: api-eu.mixpanel.com - India Data Residency: api-in.mixpanel.com 7. Project Token: Verify that you're using the correct project token. You can find your project token in the Mixpanel project settings, as described in the [Mixpanel documentation](https://docs.mixpanel.com/docs/orgs-and-projects/managing-projects#find-your-project-tokens). For the segmentation query, your approach looks correct. The on parameter properties["projectKey"] == "abc-123" should work if the property and value exist in your data.
kapa.ai
APP
·
·
If you've verified all these points and are still not getting results, I recommend enabling debug mode in your Mixpanel implementation to ensure the events are being sent correctly. You can find instructions for enabling debug mode in various SDKs in the Mixpanel documentation.If the problem persists after checking these points, you may want to contact Mixpanel support for further assistance, as they can look into your specific project setup and data.
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.