Events
Grow → Events is the live inventory of product moments, plus in-flight wiring as a pull request you merge. The other jobs cannot run without this.
The API resource page at Product events is how you emit events yourself. This how-to is the dashboard desk.
What you see
- Live: events already arriving, with volume and recent activity
- In flight: instrumentation Ranla has proposed or already opened a pull request for
A long wiring list no longer buries what is actually firing.
What to connect
| Need | Where |
|---|---|
| First-party events | GitHub so Ranla can open a PR, or the SDK / REST yourself |
| Analytics copy | Settings → Integrations → PostHog, Amplitude, or Mixpanel, then mark moments actable |
| Tracking on the site | Instrument your product |
Connect order does not matter. Live fills as events arrive.
In flight is a pull request
- Open Grow → Events.
- Read Live for what already fires.
- In flight shows recommended events and open PRs.
- Review and merge. Ranla does not push to your default branch.
Next steps
- Instrument your product: snippet, GitHub, SDK
- Connect analytics: copy moments you already track
- Product events: REST resource
- Modes: Draft, Propose, Autopilot