Limits Worth Knowing

Real constraints in the current build. Knowing them saves you misreading a screen.

Updated

These are real constraints, not caveats.

The Heatmaps table reads a window, not everything
Up to 5,000 identified users and 5,000 anonymous visitors per site, with per-person facets computed from that site's most recent 20,000 events in the selected range. Shorter ranges are complete.
Country is empty in local development
It comes from edge request headers, which are absent when running locally.
Notification read state is per-browser
It does not sync across devices.
Google and Microsoft sign-in are not offered
Connect Gmail over IMAP/SMTP with an app password. Outlook.com and Hotmail addresses can't connect, and a Microsoft 365 mailbox can send only with SMTP AUTH turned on, without its replies syncing to Behavly.
Replies to email-service sends aren't read
An email service has no inbox for Behavly to read, so replies go to the sending address and never reach the Behavly Inbox or a path's replied branch.

Still stuck? Ask Behavly Agent from inside the app — it can explain any part of Behavly, though it cannot see your data. Or email hello@behavly.io.