Skip to main content
  1. Home
  2. Integrations
  3. Loop Subscriptions
Upstack Data

Loop Subscriptions integration: every charge captured server-side and resolved to a person

Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.

Role
Source
Category
Payments & subscriptions
Pre-built connectors
34 destinations
Plans
All plans

What Upstack captures

Every Loop Subscriptions event leaves resolved to a person. Captured on the server, resolved to a person, then sent.

In: from Loop SubscriptionsWhat it carries
  • subscription_idthe Loop subscription across its whole life
  • email / phonesubscriber contact
  • event_typerenewal, swap, skip, pause, cancel or save
  • line_itemsproducts after any swap
  • total / intervalcharge amount and billing cadence

Subscription state, not just revenue.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to Meta Conversions API1 of 34 destinations
  • em, ph (SHA-256)raise Event Match Quality
  • fbclid / _fbpcredit the click that drove it
  • external_idstable person across sessions
  • event_iddedupe against the browser pixel
  • value / currencyvalue-based bidding

Conversions API with higher Event Match Quality.

About Loop Subscriptions

Upstack forwards each event as its own thing, so a save is distinguishable from a renewal and a cancellation from a pause.

Downstream, flows respond to what actually happened, and acquisition campaigns stop counting retained subscribers as new customers.

What Loop Subscriptions is

Loop Subscriptions manages subscription programs for Shopify brands, with retention tooling built around cancellation flows and swaps.

Retention events carry the most information about a customer and are the least likely to be tracked.

How Loop Subscriptions works

Loop handles renewals, swaps, skips, pauses and cancel-flow outcomes. A customer offered a discount instead of canceling produces a state change that is neither a new order nor a lost one. Standard order tracking has no representation for most of these.

What you can do with it

Three jobs Loop Subscriptions does once it is connected.

01

Capture every order server-side

Loop Subscriptions events are captured from the server rather than the shopper’s browser, so ad blockers and ITP stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.

02

Resolve each event to a person

Every Loop Subscriptions event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognized as returning.

03

Retention events, not just orders

Swaps, pauses and saves are forwarded as distinct states, so downstream tools respond to a retention outcome rather than inferring it from silence.

Pre-built connectors

Loop Subscriptions forwards to 34 destinations. Connect Loop Subscriptions once. Every destination is already wired.

See all 34 Loop Subscriptions connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Loop Subscriptions as a source.

FAQ

Loop Subscriptions integration questions.

What does Upstack capture from Loop Subscriptions?

Capture Loop Subscriptions events server-side (new subscriptions, renewals, swaps and cancellations), each as what it actually is.

Which plans include the Loop Subscriptions integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which destinations can Loop Subscriptions send to?

34 destinations, including Meta Conversions API, Google Ads Conversions, TikTok Events API, Pinterest, Snapchat and Reddit. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other sources to connect.

See all integrations

Get Loop Subscriptions tracking right.

A 15-minute walkthrough tailored to your stack and channels.