.svg?fit=max&auto=format&n=mBaWmVpTOpDBIB6_&q=85&s=36c7989ebe591de9ac7d3618f0a04a28)
.svg?fit=max&auto=format&n=mBaWmVpTOpDBIB6_&q=85&s=5afe473ba3ef2469d3e839045bcb099c)
subscription.subscribed) fires when a store’s paid subscription to your app becomes active for the first time. This is the conversion moment: trial to paid, free to paid, or a straight purchase.
When it fires
When Shopify reports the store’s app subscription as active and that subscription had never been active before. Three cases deliberately don’t fire it:- An unfreeze. A subscription returning to active from frozen fires Unfrozen instead. That store was already a customer.
- A repeat activation of a subscription that has been active before.
- An approval that lands after an uninstall. When a store approves a subscription and uninstalls your app before Shopify’s approval reaches Meridian, the uninstall has already cancelled that subscription, so the late approval is ignored. This holds for subscriptions your app creates outside Plan Builder too: Meridian compares Shopify’s time of the approval with Shopify’s time of the uninstall and records the subscription as cancelled. A store that reinstalls and approves a new subscription keeps it, even when the uninstall reaches Meridian after the approval.
What it carries
Beyond the store’s own variables, two event variables from the subscription’s payload:
Both are available to email templates and to a variable condition, so a flow can branch on which plan was bought.
Building on it
- Send the onboarding email for the plan the store just bought, branching on
subscription_plan. - Record the conversion date in a custom field.
- Notify your team on high-value plans by addressing the send to specific people.