Backend meets browser.
Send events through one ingestion API. Keep production and development separate, with write keys for each source.
PRODUCT ANALYTICS / B2B SAAS
Your customers work in teams. Your analytics should too. Bring backend and browser events together, and see which accounts are active and what they use.
Account-first. API-first. Built with privacy in mind.
// the event, with its account context
{
"event": "Report Created",
"properties": {
"report_type": "adoption"
}
}Illustrative payload from our synthetic demo. No customer data.
FROM EVENTS TO UNDERSTANDING
Start with trustworthy events. Then look at the people and accounts behind them.
Send events through one ingestion API. Keep production and development separate, with write keys for each source.
Inspect events in Live, check refused requests and organise event names in the catalogue. Find tracking problems before trusting the numbers.
Measure active accounts and users over time. See which accounts used an event and how widely that behaviour has been adopted.
YOUR DATA, WITH BOUNDARIES
The application is hosted in Germany. Browser keys can write but cannot read. Connection IP addresses are not stored, and event properties stay out of application logs.
Workspace owners can export and erase data for a named user or account. Raw events are kept for 400 days.
Understand the current scope ↓A FEW STRAIGHT ANSWERS
datalove is in a closed pilot. Public signups are not open. Existing pilot members can sign in; wider availability will follow the remaining reliability and integration checks.
The ingestion API accepts Segment-shaped identify, group, track, page and screen calls. Trusted identify and anonymous-to-user alias calls can link earlier visits without rewriting raw events. Merging two known users is not supported. Full compatibility with real SDKs is still being verified, so a drop-in replacement is not promised.
An account is the company, team or group using your product. A user is a person using it. Segment’s groupId maps to the account and userId maps to the user. These are separate from the members who sign in to datalove.
Funnels, behavioural retention and destination forwarding are not available yet. Our first-party browser collection is being exercised in the closed pilot. Session recordings of signed-in users are in the closed pilot. Experiments, feature flags, heatmaps, a mobile SDK, marketing attribution and audience activation are outside the first release.
We count page views on our own server, without cookies, scripts or anything stored in your browser: the page, the site that linked to it and campaign tags. To count visitors, we compute a code from your IP address and browser with a random value that we replace and delete every day; tomorrow the code is different, so nothing connects visits across days. From the same address and browser we note your country, region and city (IP geolocation by DB-IP) and your browser, operating system and device type; the address and the browser string themselves are never stored. These anonymous page views are kept for 24 months. When you are signed in, we record which pages you open and what you do in datalove (for example creating a source), with your member and workspace, to improve the product. There are no third-party analytics trackers or external font requests. Raw events expire after 400 days. You can object at any time by writing to stefan@datalove.io; we then stop recording for you and erase what was recorded.
CURRENT AVAILABILITY
Already part of the pilot? Your workspace is ready for you.