June supports two types of data:
CDP (Customer Data Platforms): With tools like Segment, you can send data by flipping a switch. We partner with a growing number of CDPs (Segment, Rudderstack, Freshpaint) to seamlessly integrate analytics into any tech stack.
SDK: You can stream data directly from any digital product using a June SDK. Our developer documentation will guide you in choosing the best option for your infrastructure.Browser, React, NodeJS, Python, Ruby, HTTP.
CDPs and SDKs imply installing some code in your codebase to collect useful data. The technical complexity is the same. If you don't have any of these sources and you're not sure which one is the best for you keep reading.
What data source is the best for you?
These are the most common scenarios:
You want to push and leverage data in many different tools
You're getting started with data and you're sure that in the next 1-2 years you'll use behavioral data in many places (emails, onboarding automation, in-product engagement etc)
You want a single source of truth on which both your product and revenue team align
You don't need yet the flexibility of a database to run your operations. If you think a CDP is the best option for you but you're not sure which one to pick have a look at this
If you wonder here is a comparison between Segment and Rudderstack
June SDK is the best option if:
You're a medium size business and all your operations are already relying on the data from your database and the only tool you want to feed with event data is June. In this case, using our SDK will make you save money and buy only 1 tool instead of 2
You're super early and you don't have much cash/needs. You just want to have analytics and you don't need to send transactional emails/product tours etc.
Your current tracking plan is very messy and you want to start from a clean canvas without having to pay for another tool
If you already implemented a data source here is how to collect data in your product.