June

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.

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

1. If your data is coming in, you should be able to see it on this graph: 

2. 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. ​

1. 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. ​
2. 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

1. Open the developer tools and check if your events are coming in properly or not
 ​
 Open the developer tools
 
 1. If your data is coming in, you should be able to see it on this graph: 
 
 2. 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: 
 
 
2. 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. ​
 1. 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. ​
 2. 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.
 
3. If you're still having trouble debugging your setup, feel free to reach out in the Intercom chat

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:

- 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.

- 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.

1. 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.
2. 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.

Basic data debugging

What should I do if I see the error message "Something went wrong on our side"?