Send in-app purchase events to Intercom
When subscription status lives in Intercom alongside your customer conversations, support and marketing teams can act on what is actually happening in the app.
This integration passes subscription events into Intercom so you can build segments, answer billing questions with context, and launch campaigns tied to real purchase behavior.
What the Intercom connection enables
The integration is designed around three practical outcomes. First, you can create custom filters that group users into actionable segments based on in-app behaviors. Second, the connection is designed to let support teams view cross-platform customer purchase histories and grant promotional subscriptions. Third, marketing teams can trigger campaigns from in-app events to improve conversions and reduce churn. Each outcome depends on the same foundation: accurate, current subscription data reaching Intercom.
Subscription events you can send
The connection forwards a defined set of subscription lifecycle events. Each event marks a specific moment in the subscriber journey, and the wording matters when you build Intercom filters or campaign triggers.
Which events matter to which team
A simple way to plan your Intercom setup is to map each event to the team that will act on it. Support usually cares most about Billing Issues and Expiration, because those affect access and refund conversations. Marketing tends to focus on Trial Started, Trial Converted, Trial Cancelled, Renewal, Cancellation, and Uncancellation for lifecycle campaigns. Product and revenue teams often watch Product Change and Non Subscription Purchase to understand plan movement and one-off purchases.
Billing Issues is not the same as Expiration
These two events are easy to confuse, and confusing them can cause support teams to remove access too early. Billing Issues means a charge attempt ran into a problem. It does not mean the subscription has expired, particularly when a grace period is enabled. Expiration is the event that signals the subscription has ended and access should be removed. Build any automated access-change workflow around Expiration, and treat Billing Issues as a prompt for outreach or a payment-retry message.
Product Change does not mean immediate activation
When a subscriber moves to a different product, the Product Change event records that the change happened. It does not guarantee the new subscription is in effect right away. Upgrades, downgrades, and crossgrades can take effect on different timelines depending on the store and plan rules. If your Intercom messaging promises immediate access to the new plan, verify the effective date before sending it. The managing subscriptions documentation covers how updates, downgrades, and crossgrades are handled.
Setup checklist before you launch campaigns
Work through these checks so your Intercom automations reflect real subscription behavior rather than assumptions. Confirm the connection is active and events are arriving. Verify that each event you plan to use appears with the expected name. Test a segment filter against a known subscriber before attaching it to a campaign. Decide which events should trigger support notifications versus marketing messages. Confirm that any access-removal workflow listens to Expiration rather than Billing Issues. Review how Product Change timing affects any message that promises new plan access. Finally, confirm with your team how promotional subscription grants are recorded so support can trace them later.
Frequently asked questions
Does a Billing Issues event mean the subscriber has lost access?
No. Billing Issues means a charge attempt failed. The subscription has not necessarily expired, especially if a grace period is enabled. Access should be removed on Expiration, not on Billing Issues.
If I see a Product Change event, is the new plan already active?
Not always. Product Change records that the subscriber moved to a different product, but the new subscription may not be in effect immediately. Upgrades, downgrades, and crossgrades can follow different timing rules.
Can support agents see purchase history across platforms?
The connection is designed to let support teams view cross-platform customer purchase histories and grant promotional subscriptions. Confirm the exact workflow in your own Intercom setup before relying on it.
What can I build with custom filters?
Custom filters let you group users into actionable segments based on in-app behaviors, so campaigns and support queues can target subscribers by what they have actually done.