Integration events

Every subscription event Subrise sends to Klaviyo, Attentive, Mailchimp and Zapier, when it fires and the fields it carries.

Subrise sends the 11 events below to every connected Klaviyo, Attentive, Mailchimp and Zapier account. A few more go to some of the tools only. See Other events. This page lists when each event fires and what it contains.

Each tool receives them a little differently:

Tool	How the event arrives
Zapier	The JSON below, posted to your webhook URL.
Klaviyo	A metric named after `metric`, with every field under a property named `data`. Klaviyo also gets its own lifecycle events.
Attentive	A custom event with the Attentive name and these fields as properties.
Mailchimp	An event named after `metric` on the contact's activity.

Shopify Flow and webhooks have their own payloads.

Events

`metric`	Fires when
`subrise_new_subscription`	A subscription is created: at checkout, in the admin or by a migration.
`subrise_new_subscriber`	A customer's first ever subscription places its first order.
`subrise_prepaid_subscription`	An order for a prepaid subscription is placed, at checkout or on renewal.
`subrise_addon_purchase`	An order includes one-time add-ons, or an add-on is added to a subscription.
`subrise_upcoming_invoice`	Before each order, on the schedule of your upcoming order email. Plans with their own upcoming order setting don't send it.
`subrise_successful_payment`	A renewal is charged and its order is created.
`subrise_failed_transaction`	A renewal charge fails.
`subrise_subscription_modified`	A subscription changes, including when its next billing date moves forward after a renewal.
`subrise_pause_subscription`	A subscription is paused.
`subrise_reactivate_sub`	A paused or cancelled subscription is resumed.
`subrise_subscription_cancelled`	A subscription is cancelled.

Other events

`metric`	Sent to	Fires when
`subrise_prepaid_sub`	Klaviyo, Attentive, Mailchimp, Zapier	A customer buys a gift from a Multi-order option. Attentive gets it as Prepaid Subscription.
`subrise_trial_started`	Klaviyo, Attentive, Zapier	A subscription starts a trial period.
`subrise_trial_ending_soon`	Klaviyo, Attentive, Zapier	A trial period ends in 2 days.
`subrise_trial_converted`	Klaviyo, Attentive, Zapier	A trial period ends and the subscription moves to its full price.
`subrise_cancellation_attempt`	Klaviyo, Attentive, Zapier	A customer starts to cancel and is shown a cancellation flow.
`subrise_cancellation_saved`	Klaviyo, Attentive, Zapier	A customer accepts a cancellation flow offer and keeps the subscription.
`subrise_multi_order_prepaid_shipment_order`	Klaviyo	Subrise creates the order for one shipment of a Multi-order gift.

The trial and cancellation flow events are not sent yet. Trial periods and cancellation flows are not yet available in the Subrise admin.

Fields on every event

Field	Type	What it holds
`metric`	string	The event name from the table above.
`customer_first_name`, `customer_last_name`	string	The subscriber's name.
`customer_email`	string	The subscriber's email.
`customer_phone`	string	The subscriber's phone number, or `"undefined"` when none is saved.
`customer_id`	string	The Shopify customer ID as a plain number, such as `"7212345678901"`, not a `gid://` ID.
`subscription_id`	string	The subscription contract ID, such as `"28845637871"`.

Text fields that have no value can arrive as the string "undefined" or "null". Check for these before you use a field in a message.

Most events also carry:

Field	Type	What it holds
`total_subscription_orders`	number	Orders this subscription has placed.
`total_subscription_spend`	number	What the customer has paid across this subscription's orders.
`customer_total_shop_spend`	number	What the customer has spent in your store in total.
`addon_count`	number	One-time add-ons on the subscription.
`customer_portal_link`	string	The customer's link to manage the subscription.

subrise_upcoming_invoice and subrise_failed_transaction don't carry these.

Fields by event

`metric`	Extra fields
`subrise_new_subscription`	`total_subscription_price`, `subscription_started_date`, `order_id`, `subscription_line_items`
`subrise_new_subscriber`	`subscription_total`, `subscription_started`, `order_id`, `subscription_line_items`
`subrise_prepaid_subscription`	`total_subscription_price`, `order_id`, `subscription_line_items`
`subrise_addon_purchase`	`total_subscription_price`, `addon_line_items`
`subrise_upcoming_invoice`	`subscription_invoice_date`: when the order bills
`subrise_successful_payment`	`total_subscription_price`, `payment_date`, `order_id`
`subrise_failed_transaction`	`total_subscription_price`, `failed_billing_error_message`, `card_info` (the card's last digits)
`subrise_subscription_modified`	`total_subscription_price`, `subscription_modified_date`, `update_body` (the change as JSON text), then `updatedField1` and `updatedValue1`, `updatedField2` and `updatedValue2`, and so on for each changed field
`subrise_pause_subscription`	`pause_reason`, `pause_details`, `subscription_paused_date`
`subrise_reactivate_sub`	`total_subscription_price`, `subscription_updated_date`
`subrise_subscription_cancelled`	`reason`, `reason_details`, `subscription_cancelled_date`
`subrise_trial_started`	`trial_start_date`, `trial_end_date`, `trial_duration_days`, `trial_price`, `original_price`
`subrise_trial_ending_soon`	`trial_end_date`, `days_remaining`, `original_price`
`subrise_trial_converted`	`conversion_date`, `trial_price`, `full_price`
`subrise_cancellation_attempt`	`flow_id`
`subrise_cancellation_saved`	`flow_id`, `reason_id`, `offer_type`, `saved_date`

The trial and cancellation flow events don't carry customer_phone or the fields in "Most events also carry".

subrise_prepaid_sub and subrise_multi_order_prepaid_shipment_order come from the gift order, not a subscription contract. They carry the customer's name, email and phone but no customer_id or subscription_id:

subrise_prepaid_sub: total_subscription_price (the order total) and prepaid_line_items, a list of items with variant_title, price and quantity.
subrise_multi_order_prepaid_shipment_order: gift_subscription_id, shipment_sequence, order_id, order_name, total_subscription_price (always 0), multi_order_prepaid_line_items and payment_date.

total_subscription_price and subscription_total are the price of one order. Dates are ISO 8601, such as 2026-10-18T14:02:11.512Z.

Line items

subscription_line_items and addon_line_items are objects that hold a list of the same name:

json

{
  "subscription_line_items": {
    "subscription_line_items": [
      { "variant_title": "Coffee - 1lb", "price": "19.95", "quantity": 2 }
    ]
  }
}

Each item has variant_title, price and quantity. On subrise_new_subscription and subrise_new_subscriber items also have discounted_price. Prices are strings.

Example

A subrise_failed_transaction event, as Zapier receives it:

json

{
  "metric": "subrise_failed_transaction",
  "customer_first_name": "Jane",
  "customer_last_name": "Doe",
  "customer_email": "jane@example.com",
  "customer_phone": "+15555550123",
  "customer_id": "7212345678901",
  "subscription_id": "28845637871",
  "total_subscription_price": 39.9,
  "failed_billing_error_message": "Your card was declined.",
  "card_info": "4242"
}