GitHub Start free

Integration · Messaging and marketing

Send subscription events to Intercom contacts

RevenueDot sends each subscription event to Intercom as a data event on the contact, named like rc_initial_purchase_event, with the product, entitlement, store, subscription_status and, on paid events, the price in cents. The contact is found by user id, which is your app user id. Anonymous customers need the $email attribute. It works in US, EU and Australia workspaces.

Start free on Cloud Setup guide →

What teams do with it

  • Start an Intercom series when a trial starts or a billing issue appears.
  • Segment contacts by subscription events for targeted in-app messages.
  • Show subscription history in a contact's activity.
  • Message customers who cancelled or whose subscription expired.

What RevenueDot sends

  • A data event per step through POST /events, named rc_initial_purchase_event, rc_trial_started_event, rc_renewal_event and so on, for 11 steps. Rename them under Event names.
  • The metadata holds up to 10 keys, such as product_identifier, entitlement, store, environment, subscription_status, expires_at, period_type and cancellation_reason.
  • Paid events with revenue above zero carry price as an amount in cents with currency usd. Refunds carry none.
  • The contact is the app user id as user_id. Anonymous app user ids use $email instead and are skipped without it.
  • Intercom answers 404 for a contact it does not have. Sandbox events go to the same workspace with environment: SANDBOX when the environment includes sandbox.

Setup

How to connect Intercom to RevenueDot

  1. 01

    Copy an access token

    In the Intercom Developer Hub, open your app's Authentication and copy the Access token.

  2. 02

    Open the integration

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

  3. 03

    Paste the token

    Paste it into Access token.

  4. 04

    Pick the region

    Choose Data hosting region: US (api.intercom.io), EU (api.eu.intercom.io) or Australia (api.au.intercom.io). Pick Sales reporting.

  5. 05

    Connect and test

    Click Connect Intercom, then Send test event for a customer whose user id exists in Intercom.

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

How RevenueDot delivers events to Intercom

  • Timeouts, rate limits (HTTP 429) and server errors (5xx) from Intercom 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.
  • Intercom returns errors as an error.list body. RevenueDot logs the first message.
  • Intercom deduplicates on contact, event name and created_at, so a retried event is not recorded twice.

FAQ

Intercom and RevenueDot

Does the Intercom 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 $email with the SDK's attribute call for anonymous customers, because Intercom finds contacts by user id or email.

Is it the same as RevenueCat's Intercom integration?

It sends the same rc_*_event names as Intercom data events. RevenueCat's version has years of production use behind it. RevenueDot's is newer, so run Send test event and check Intercom before you rely on it.

Is this the same as the Intercom inbox app?

No. This integration sends events to contacts. The separate Intercom inbox app shows each customer's subscription next to a conversation, and needs no access token.

Why did Intercom answer 404?

Intercom has no contact with that user id. Create the contact in Intercom with your app user id as its external id, then retry the event.

Sources: Intercom · Intercom data events API · RevenueCat Intercom integration. Intercom is a trademark of its owner, used to describe compatibility. RevenueDot is not affiliated with or endorsed by it.

Get started

Send Intercom 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