GitHub Start free

Integration · Product analytics

Send in-app subscription events to Segment

RevenueDot sends each purchase, trial, renewal, cancellation and refund to Segment as a track call named like rc_renewal_event, plus an identify call that sets rc_subscription_status. Events carry revenue in US dollars, product, store, entitlements and transaction ids. They go to your Segment HTTP API source as they happen, and messageId lets Segment drop retried duplicates.

Start free on Cloud Setup guide →

What teams do with it

  • Fan subscription revenue out to every Segment destination, such as your warehouse, ad networks and email tool.
  • Join app behavior and subscription status in one customer profile.
  • Trigger lifecycle campaigns from rc_billing_issue_event or rc_trial_cancelled_event.
  • Keep the RevenueCat event names your downstream dashboards already use.

What RevenueDot sends

  • A track call per event, named rc_initial_purchase_event, rc_trial_started_event, rc_trial_converted_event, rc_renewal_event, rc_cancellation_event and so on. Rename any of them under Event names.
  • The properties include revenue in US dollars, currency (USD), price_in_purchased_currency, purchased_currency, store, product_id, entitlements, transaction_id and the customer's attributes.
  • An identify call sets the traits rc_subscription_status, last_seen_app_user_id and aliases.
  • userId is the app user id. Turn on Send anonymous app user ids as anonymousId to send $RCAnonymousID: customers as anonymousId.
  • messageId is the event id (the identify call adds -identify), so Segment deduplicates retries. context.environment is production or sandbox.
  • The three web funnel events (rd_funnel_viewed, rd_funnel_step_completed, rd_funnel_purchase) are opt-in.

Setup

How to connect Segment to RevenueDot

  1. 01

    Add a Segment source

    In Segment, add an HTTP API source and copy its write key.

  2. 02

    Open the integration

    In RevenueDot, open Integrations in the project sidebar and choose Segment.

  3. 03

    Enter the key and region

    Paste the key into Write key and pick the Region: US (api.segment.io) or EU (events.eu1.segmentapis.com).

  4. 04

    Set identity and revenue

    Turn on Send anonymous app user ids as anonymousId if you want it, and pick Sales reporting.

  5. 05

    Connect and test

    Click Connect Segment, then Send test event and look for rc_test_event in the source's Debugger.

The Segment integration page in the RevenueDot dashboard, with its settings form
Captured from the RevenueDot dashboard with demo data.

How RevenueDot delivers events to Segment

  • Timeouts, rate limits (HTTP 429) and server errors (5xx) from Segment retry on the webhook schedule: after 5, 10, 20, 40 and 80 minutes.
  • Any other 4xx answer fails at once, because sending the same request again cannot work. Fix the setting, then click Replay failed.
  • The delivery log keeps each request with every secret replaced by [redacted], the answer, the time taken and, for skipped events, the reason.
  • Credentials are sealed with AES-256-GCM on the server. After you save a key, the dashboard shows only its last four characters.

FAQ

Segment and RevenueDot

Does the Segment integration work with the RevenueCat SDK?

Yes. RevenueDot speaks the RevenueCat SDK protocol, so your app keeps the RevenueCat SDK and only the server address changes. Set the customer's $email and other attributes with the SDK's attribute calls if you want them on the Segment profile.

Is it the same as RevenueCat's Segment integration?

It sends the same rc_*_event names and the same rc_subscription_status trait, so dashboards built on RevenueCat's Segment events keep working. RevenueCat's version has years of production use behind it. RevenueDot's is newer, so run Send test event and check Segment before you rely on it.

Does Segment receive sandbox purchases?

Sandbox events go to the same source with context.environment set to sandbox. Set the integration's environment to production to leave them out.

Can I use the EU region?

Yes. Pick EU under Region and RevenueDot calls events.eu1.segmentapis.com instead of api.segment.io.

Sources: Segment · Segment HTTP Tracking API · RevenueCat third-party integrations. Segment is a trademark of its owner, used to describe compatibility. RevenueDot is not affiliated with or endorsed by it.

Get started

Send Segment every subscription event.

Start free on RevenueDot Cloud, free up to $10,000 a month in tracked revenue. Integrations are included on every plan.

Start free on Cloud Migrate from RevenueCat →

Already have an account? Sign in · Prefer your own servers? Self-host free