subscription_recurring_purchase Event

Automatically generated for Shopify — Upstack creates this event from Shopify subscription orders, so Shopify stores don’t fire it manually. On other platforms, fire it yourself.

Overview

The subscription_recurring_purchase event is generated for each recurring subscription renewal — all orders after the initial subscription purchase.

How It Works

Upstack checks every purchase event it processes. It generates subscription_recurring_purchase as a copy of the purchase when either of these is true:

The order’s source is subscription_contract or subscription_contract_checkout_one.
The order has the tag Subscription Recurring Order or Subscription Recurring Order Loop.

For these orders, Upstack doesn’t send the purchase, nc_purchase or rc_purchase events server-side to TikTok, Reddit, Google Ads, Microsoft Ads, AppLovin, Outbrain, Taboola or NewsBreak, so renewals don’t count as new conversions there. subscription_recurring_purchase itself is still sent wherever the table below says.

Properties

This event includes all properties from the original purchase event:

Property	Type	Description
orderId	string	Shopify order ID
value	number	Order total value
currency	string	ISO 4217 currency code (e.g., `USD`)
items	array	Products purchased
email	string	Customer email (hashed for destinations)
phone	string	Customer phone (hashed for destinations)

Destination Mapping

Destination	Event name	Sent by default
Meta	`subscriptionRecurringPurchase` (custom event)	Yes
TikTok	`SubscriptionRecurringPurchase`	Yes
Klaviyo	`Subscription Recurring Order - Upstackified`	Yes
Omnisend	`Subscription Recurring Order - Upstackified`	Yes
Sendlane	`subscription-recurring-purchase-upstackified`	Yes
Pinterest	`custom`	Yes
Microsoft Ads	`subscription_recurring_purchase` (custom event)	Yes
Google Ads	The conversion action you map it to	No. Map it to a conversion action
GA4, Reddit	Your choice	No. Add a destination event mapping
Snapchat, LinkedIn, AppLovin	Not sent	No

Meta needs each custom event approved before you can optimize on it. See How to approve Meta custom events.

Fire it manually (non-Shopify)

On platforms other than Shopify — for example a SaaS app billing through Stripe — Upstack can’t detect subscription orders, so fire this event yourself. Shopify stores shouldn’t fire it manually, or it will be counted twice.

window._upstack('track', 'subscription_recurring_purchase', {
  subscriptionId: 'sub_def456',
  accountId: 'acct_abc123',
  planId: 'plan_pro_monthly',
  planName: 'Pro Plan',
  value: 99.00,
  currency: 'USD',
  billingInterval: 'month',
  renewalNumber: 6
});

Property	Type	Required	Description
subscriptionId	string	No	Subscription identifier
accountId	string	No	Account identifier
planId	string	No	Plan identifier
planName	string	No	Plan display name
value	number	No	Payment amount in currency units (`99.00`, not `9900`)
currency	string	No	ISO 4217 currency code
billingInterval	string	No	`month` or `year`
renewalNumber	number	No	Which renewal this is (2nd, 3rd, etc.)

Fire it when:

Each recurring billing charge succeeds (for Stripe, when invoice.paid fires for an existing subscription — not the first invoice)

Metrics Available

Metric	Description
Subscription Recurring Purchases	Renewal orders
Cost per Subscription Recurring Purchase	Cost attributed to renewals
Subscription Recurring Purchase Value	Recurring subscription revenue

For other subscription lifecycle events (trials, plan changes, cancellations), see SaaS Events.

purchase — The base purchase event
subscription_initial_purchase — First-time subscription purchases
rc_purchase — Returning customer purchases

​Overview

​How It Works

​Properties

​Destination Mapping

​Fire it manually (non-Shopify)

​Metrics Available

​Related Events

Overview

How It Works

Properties

Destination Mapping

Fire it manually (non-Shopify)

Metrics Available

Related Events