One of the most important things to be able to get any value from June is to get data flowing into June.
Sometimes because of small setting errors, we see users struggle to get started. This article is a step-by-step guide that will help you get unblocked without talking to a human.
Basic data debugging
If you connected Segment (or one of the CDP options available) or installed our SDK and can't see your data coming in:
Open the developer tools and check if your events are coming in properly or not
If your data is coming in, you should be able to see it on this graph:
If the data is coming in but something seems to be missing, you can check the logs to see what exactly is sent through on the API call:
If no events show up after 2-3 minutes that they've been triggered, check your data source to understand whether or not events are being sent to June.
If you're using Segment you can check the "Delivery" tab in the June destination page. This will show you if there have been any errors in sending data to June.
If you're using the June SDK you may want to check if there are any problems with your setup. The things that usually go wrong are either the wrong API key is provided, or no network requests are being made. For instance, in serverless environments, you want to disable batching and async processing of events.
If you're still having trouble debugging your setup, feel free to reach out in the Intercom chat
Other possible reasons why your data isn’t showing up
If you're not seeing events in your June workspace, here are some common reasons and troubleshooting steps:
1. Events not appearing after setup
A common issue occurs when trying to test new tracking implementations in an existing development workspace. Even if your writekey is correct, events may not appear due to:
Time delay: June processes events in bulk, so they may take up to 2 minutes to appear in the events feed. Wait a few minutes and check again.
Serverless environment issues: If you're sending events from a serverless environment, batch processing may be causing issues. Try disabling it:
Node SDK: Set
maxEventsInBatchto1.Python SDK: Use
sync_mode = Trueto disable threading.
Data source issues: If you're using Segment, check the "Delivery" tab in your June destination settings for any errors.
2. Connection issues
If you see an error like:
vbnetCopyEditerror uploading: HTTPSConnectionPool(host='api.june.so', port=443): Max retries exceeded with url: /sdk/batch (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x11737c5c0>: Failed to establish a new connection: [Errno 8] nodename nor servname provided, or not known'))This usually indicates a connection issue, which might be caused by:
Network restrictions – Your development environment may not have access to June’s servers.
Incorrect workspace access – Ensure you're sending data to the correct workspace. If you have multiple workspaces, double-check which one you’re using.
3. Ad Blockers and Network Restrictions
Ad blockers and strict network settings can sometimes prevent events from being sent to June. If you're testing locally and your data isn't showing up, check for:
Ad blockers or privacy-focused extensions – Some browser extensions (like uBlock Origin or Brave’s built-in shields) can block tracking requests. Try disabling them and reloading your app.
Firewall or VPN restrictions – If you’re on a corporate network or using a VPN, outbound requests to June’s servers might be blocked. Switching networks or disabling your VPN temporarily can help identify the issue.
Browser console errors – Open your browser’s developer tools (F12 or right-click > Inspect > Console) and look for any blocked network requests to
api.june.so.
If you suspect an ad blocker is interfering, try using an incognito window (with extensions disabled) to test event tracking.
4. Still not working?
If none of these solutions resolve your issue, you can:
Use developer tools to inspect API calls and confirm if events are being sent.
Check the logs for errors.
Contact June support with details about your setup and any error messages you’ve encountered.
What should I do if I see the error message "Something went wrong on our side"?
If you encounter the error message "Something went wrong on our side", it could indicate an issue on our end. Here's what to do:
Reload the Page:
Start by refreshing the page. In most cases, this resolves the issue as the error might be caused by an edge case bug. This step works in about 90% of situations.
Contact Us:
If refreshing doesn't fix the problem, please reach out to us via chat.
Include the following details to help us investigate:
A link to the page where the error occurred.
A brief explanation of the steps that led to the error.
We'll look into the issue as quickly as possible to get you back on track.