Skip to content
AppDues
Log in
Contact salesSign up

Send in-app purchase events to OneSignal

Connecting your subscription platform to OneSignal keeps each user's subscription state visible inside your messaging platform.

Every auto-renewing subscription event from the App Store, Google Play, or Stripe adds or updates a set of tags on that user in OneSignal, so campaigns can target people by trial status, plan, store, environment, and recent lifecycle event instead of guessing from app behavior alone.

Tag reference

The table below lists every tag written to OneSignal on an auto-renewing subscription event. Each row gives the tag name, its meaning, and the values it can take.

Worked example: one user across a trial and a cancellation

Consider a user who starts a free trial, converts to a paid plan, and later cancels. The tags change at each step, and the final state is what a win-back campaign would target.

  1. Trial start. The event is TRIAL_STARTED. Period Type is TRIAL, Active Subscription is true, Store is APP_STORE (or PLAY_STORE), Environment is PRODUCTION, and the Entitlement ID lists the entitlement the trial unlocked. Expiration holds the trial end date.
  1. Conversion. The event becomes TRIAL_CONVERTED. Period Type moves to NORMAL, Purchased At updates to the conversion time, and Expiration moves to the first paid renewal date. Active Subscription stays true.
  1. Cancellation. The event becomes CANCELLATION. Active Subscription remains true until access actually ends, because the flag only flips to false on EXPIRATION. A win-back campaign that fires on CANCELLATION can reach the user while they still have access, which is often the best moment to offer a reason to stay.
  1. Expiration. The event becomes EXPIRATION and Active Subscription flips to false. This is the clean signal for a reactivation message rather than a retention message.

Active Subscription vs. Last event type

These two tags are easy to confuse, and mixing them up produces campaigns that fire at the wrong time.

Active Subscription is a boolean that answers "does this user have access right now?" It is set to true on any purchase or renewal and to false on EXPIRATION. It does not flip to false on CANCELLATION, because a canceled subscription usually keeps access until the paid period ends.

Last event type is a string that answers "what was the most recent lifecycle event?" It can be INITIAL_PURCHASE, TRIAL_STARTED, TRIAL_CONVERTED, TRIAL_CANCELLED, RENEWAL, or CANCELLATION. Use it to trigger a specific message at a specific moment; use Active Subscription to decide whether the user should still be treated as a subscriber.

A practical rule: gate access-related messaging on Active Subscription, and choose the message content from Last event type.

Field map at a glance

A quick reference for the values each tag can hold:

  • Period Type: TRIAL, INTRO, or NORMAL.
  • Store: APP_STORE, PLAY_STORE, or STRIPE.
  • Environment: SANDBOX or PRODUCTION.
  • Last event type: INITIAL_PURCHASE, TRIAL_STARTED, TRIAL_CONVERTED, TRIAL_CANCELLED, RENEWAL, or CANCELLATION.
  • Active Subscription: true or false.
  • Purchased At and Expiration: epoch time in seconds.
  • Entitlement ID: a comma-separated string of entitlement identifiers the user unlocked.
  • Grace Period Expiration: sent when a billing issue occurs, carrying the grace period end date.

ConfigureTargetTest

Pre-launch checklist

Before you build campaigns on these tags, confirm the following:

  • The OneSignal integration is enabled in your subscription platform and the same user identity is used on both sides, so the App User Id tag matches the OneSignal user.
  • A sandbox purchase has been made and the resulting tags appear on the expected OneSignal user.
  • Your campaign logic uses Active Subscription for access decisions and Last event type for message selection, not the other way around.
  • Grace Period Expiration is handled explicitly if your store supports billing grace periods, so a billing issue does not look like a clean cancellation.
  • Expiration and Purchased At are read as epoch seconds, not milliseconds, when you compare them to campaign dates.

Related resources

The integration documentation covers setup and current tag behavior. A OneSignal case study describes how Rapchat used lifecycle subscription events for personalized messaging, and a recorded webinar discusses choosing OneSignal and your subscription platform together. The integration directory lists other tools that can receive subscription events. Any case study or webinar material should be reviewed for current relevance and usage rights before it is presented as supporting evidence.

Get started

To evaluate whether this integration fits your workflow, review the setup documentation and test the tag behavior in a sandbox environment before committing to a plan. Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

Tags written to OneSignal on each auto-renewing subscription event
TagMeaningValues
User IDThe App User Id that triggered the eventApp User Id string
Period TypeThe latest period type for the purchase or renewalTRIAL, INTRO, or NORMAL
Purchased AtEpoch time in seconds of the latest subscription purchase or renewalEpoch seconds
ExpirationEpoch time in seconds of the latest subscription expiration dateEpoch seconds
StoreThe store that processed the purchaseAPP_STORE, PLAY_STORE, or STRIPE
EnvironmentThe environment the event came fromSANDBOX or PRODUCTION
Last event typeThe latest event type from the userINITIAL_PURCHASE, TRIAL_STARTED, TRIAL_CONVERTED, TRIAL_CANCELLED, RENEWAL, or CANCELLATION
Product IDThe latest subscription product identifier that the user has purchased or renewedProduct identifier string
Entitlement IDComma separated string of Entitlement identifiers that the user unlockedComma-separated entitlement identifiers
Active SubscriptionSet to true on any purchase/renewal event, and false on EXPIRATIONtrue or false
Grace Period ExpirationIf a billing issue occurs, the date of the grace period expirationDate

Values reflect the tag definitions published with this integration page. Confirm the current tag behavior against the integration documentation before relying on these values in production campaigns.

Frequently asked questions

When do the OneSignal tags update?

On every auto-renewing subscription event tracked by your subscription platform. That includes initial purchases, trial starts and conversions, renewals, cancellations, and expirations. Each event adds or refreshes the full set of tags on the matching OneSignal user.

Does Active Subscription become false when a user cancels?

No. Active Subscription is set to true on any purchase or renewal and to false on EXPIRATION. A cancellation usually keeps access until the paid period ends, so the flag stays true until the expiration event arrives.

Which stores are covered?

The Store tag can be APP_STORE, PLAY_STORE, or STRIPE, so the connection covers purchases from Apple, Google, and Stripe-based web billing.

What happens if a subscriber has a billing issue?

Your subscription platform sends the Grace Period Expiration tag with the date the grace period ends. That lets you distinguish a temporary billing problem from a clean cancellation and time a payment-recovery message accordingly.

How are entitlements represented?

The Entitlement ID tag is a comma-separated string of the entitlement identifiers the user has unlocked. If a user has more than one entitlement, all of them appear in that single tag.