Home
Connectors
Loop Subscriptions - StackAdapt

Send every Loop Subscriptions event to StackAdapt, server-side

Q: How do I check that Loop Subscriptions events are reaching StackAdapt?

Open StackAdapt › Conversions › Conversion tracking. Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

Q: Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

Q: How long does it take to connect Loop Subscriptions to StackAdapt?

Most brands are live in under 20 minutes. Once Loop Subscriptions is connected, every destination receives the same resolved events, StackAdapt included.

Each event is resolved to a person against a 750M+ device graph before it reaches StackAdapt, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a Loop Subscriptions event reaches StackAdapt. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Loop Subscriptions

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

See the Loop Subscriptions integration

Loop SubscriptionsWhat it sends

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

02 Understand

Resolved to one person before it leaves

Every Loop Subscriptions event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved 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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to StackAdapt

Server-side conversions to StackAdapt with hashed identifiers attached, so multi-channel programmatic is measured on your orders.

See the StackAdapt integration

StackAdaptWhat it receives

hashed email / phoneidentity matching on arrival
sa_click_idcredit the click that drove it
external_idstable person across sessions
event_iddedupe against the browser pixel
value / currencyvalue-based bidding

The catch

Swaps, pauses and saves produce state changes with no order attached.

Ad platforms receiving only orders see a paused subscriber as churned and start bidding to re-acquire someone who is still a customer.

Where to check in StackAdaptDelivery you can audit

StackAdapt Conversions Conversion tracking

Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

What changes

What changes when Loop Subscriptions feeds StackAdapt. Two gains on the StackAdapt side, two on the Loop Subscriptions side.

StackAdapt

Server-side delivery

Events reach StackAdapt through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

StackAdapt

Identity-resolved events

Events sent to StackAdapt carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Loop Subscriptions

Every event, server-side

Storefront and checkout events are captured from Loop Subscriptions on the server, independent of the browser.

Loop Subscriptions

One setup, every destination

Connect Loop Subscriptions once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

Connect Loop Subscriptions once and every destination, StackAdapt included, is forwarded the same resolved events.

Upstack dashboardExample

Loop Subscriptions Data source Connected

StackAdapt Destination Healthy

Read the full StackAdapt setup guide

01

Connect Loop Subscriptions

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

Add the StackAdapt destination

Under Destinations, add StackAdapt. Every resolved Loop Subscriptions event is then forwarded to it.
03

Check delivery to StackAdapt

Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Loop Subscriptions and StackAdapt.

How do I check that Loop Subscriptions events are reaching StackAdapt?

Open StackAdapt › Conversions › Conversion tracking. Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect Loop Subscriptions to StackAdapt?

Most brands are live in under 20 minutes. Once Loop Subscriptions is connected, every destination receives the same resolved events, StackAdapt included.