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, feed lifecycle email, and sync to Google Ads as a matched audience.

Segment previewSigned up, never activated

signed_upexists
activated_atis empty
last_emailed_atmore than30 days ago

4,120people match right now

Connect GitHub and Ranla adds the events with a pull request you review, or connect analytics if you already track usage. Either path gets behavior into Ranla.

Events to wire

signed_upWired
activatedWired
invited_teammateRecommend
trial_endingRecommend

Opens a PR when the repo is connected

Get events in

Wire the product, or connect what you already track.

A GitHub install opens a pull request that tracks 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. The same segment is what a campaign mails and what Google Ads matches.

Connect analytics → Events → Try a public repo →

Questions

Audiences questions

How do Ranla audiences work?

Segments update from product events (PostHog, Amplitude, Mixpanel, or events wired via a GitHub PR), not a CSV you keep refreshing.

Can I target people who signed up but never activated?

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.

Do audiences connect to conversion goals?

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.