This documentation URL will be retired soon. Start using the Ranla API at https://api.ranla.ai. Docs: docs.ranla.ai.

SuperSend TXDocs

Connect PostHog, Amplitude, or Mixpanel

Use the analytics you already run so Ranla can segment, automate, and send on product moments — without opening a GitHub pull request for every event.

Prefer wiring events in your app? See Instrument your product. You can use both paths: GitHub for missing first-party events, analytics for moments you already track.

What you get

  1. Read — Ranla can list which events your project already fires and inspect one person.
  2. Actable moments — You pick which events matter. Ranla copies those events for people who have an email into its own ledger.
  3. History + live — About the last 30 days of allowlisted history lands quietly (ingest only). New events can trigger automations after you mark them actable.

Ranla does not run vendor query languages as segments, and it does not treat every event in the project as actable until you choose.

Prerequisites

  1. A Ranla account on app.ranla.ai
  2. A read-only (or appropriate) API key / credentials from PostHog, Amplitude, or Mixpanel
  3. Events that include an email or that can be tied to a contact Ranla already knows

Connect in the dashboard

  1. Open Settings → Integrations.
  2. Choose PostHog, Amplitude, or Mixpanel.
  3. Paste the credentials Ranla asks for (for PostHog, a personal or project API key with read access is typical).
  4. Save. Ranla can now read your project’s event taxonomy.

You can connect more than one analytics tool; mark moments actable per source.

Mark moments actable

  1. Review the events Ranla discovered (or ask the agent which moments matter for activation, trial, or paid).
  2. Allowlist the events you want copied into Ranla’s ledger.
  3. Confirm people have email on those events (or that contacts already exist).

Until a moment is actable, Ranla may read it for inspection but will not copy it for sends or automations.

Use the moments

Once actable events land:

  • Build segments and audiences on those event names and properties
  • Trigger automations on new occurrences
  • Ask the agent to draft campaigns against the same ledger

Transactional mail (POST /emails) and lifecycle flows share suppressions — a marketing unsubscribe does not block password resets.

API and Events ledger

Copied analytics events join the same product-event surface as Events. You can still POST /events from your app when you want first-party emission.

Common questions

Do I need GitHub to use analytics with Ranla?

No. Connect PostHog, Amplitude, or Mixpanel in Settings → Integrations, pick actable moments, and Ranla copies those events for people with email into its own ledger. GitHub instrumentation is the other on-ramp when you want first-party events in the app.

Does Ranla sync every event from my analytics project?

No. You allowlist the moments that matter. Until a moment is actable, Ranla may read it for inspection but will not copy it for segments, automations, or sends.

Can historical analytics events trigger automations?

Backfill from the last about 30 days is ingest-only. New occurrences of actable events can trigger automations after you mark them actable.