Segments are live rules on events and attributes: signed up and never activated, quiet after day three, trial ending. They update as your product changes.
signed_upexistsactivated_atis emptylast_emailed_atmore than30 days agoConnect GitHub and the agent instruments the repo with a pull request, or connect analytics if you already track usage. Either path gets behavior into Ranla.
signed_upWiredactivatedWiredinvited_teammateRecommendtrial_endingRecommendOpens a PR when the repo is connected
A GitHub install opens a PR that instruments signup and activation. Or connect analytics if those events already exist. Either way, segments follow real behavior — not a CSV you have to keep updating.
Segments update from product events (PostHog, Amplitude, Mixpanel, or events wired via a GitHub PR), not a CSV you keep refreshing.
Yes. Build segments on real behavior: signed up, never invited a teammate, hit a feature once then went quiet. Audiences stay live as events arrive.
Yes. The same events power goals on Conversions. Segments and the primary goal share one event model. Large audiences still need your approval before send.
Connect a GitHub repo, or analytics. Then talk in the agent window: templates, campaigns, automations. It still asks before it sends.