Home
Connectors
Loop Subscriptions - Sendlane

Send every Loop Subscriptions event to Sendlane, server-side

Q: What happens if a contact doesn’t exist in Sendlane?

Upstack only sends events for contacts that already exist in Sendlane. If the visitor’s email isn’t found in your account, the event is skipped, which keeps your account clean and targets only real subscribers.

Q: Which events does Sendlane receive?

ViewContent as product-viewed-upstackified, AddToCart as added-to-cart-upstackified, InitiateCheckout as checkout-started-upstackified and Purchase as order-placed-upstackified.

Q: Which customer parameters are sent to Sendlane?

Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.

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

Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.

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

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

Each event is resolved to a person against a 750M+ device graph before it reaches Sendlane, so flows trigger on a known profile rather than an anonymous session.

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 Sendlane. 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.
DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.

03 Activate

Delivered to Sendlane

Forward resolved customer events to Sendlane for retention and lifecycle flows.

See the Sendlane integration

SendlaneWhat it receives

email / phonecontact key across email, SMS and reviews
event propertiesautomation triggers
order valueattribution

Which events reach Sendlane

Each Upstack event is mapped to the Sendlane event below before it is sent.

Upstack event	Sent to Sendlane as	Key data on the event
Product view	product-viewed-upstackified	product_id, product_name, product_img_url, variant_id
Add to cart	added-to-cart-upstackified	line_items, subtotal, total, currency
Checkout	checkout-started-upstackified	checkout_id, line_items, subtotal, total, currency
Purchase	order-placed-upstackified	order_id, line_items, total, currency, discounts

Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.

The catch

A save (a customer offered a discount instead of canceling) is the highest-signal retention event there is, and it is invisible to any flow triggered on orders alone.

Where to check in SendlaneSending you can audit

Sendlane the contact record

where the event should appear against one person rather than creating a second contact.

What changes

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

Sendlane

Server-side delivery

Upstack sends events to Sendlane from its servers only, so ad blockers and browser privacy settings can’t block delivery.

Sendlane

Identity-resolved events

Events sent to Sendlane 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.

You need a Sendlane account where you can generate an API Access Token and create a Custom Integration.

Upstack dashboardExample

Loop Subscriptions Data source Connected

Sendlane Destination Healthy

Read the full Sendlane 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 Sendlane destination

Under Destinations, add Sendlane with two credentials: an API Access Token from Settings, API, and the Integration Token from a new Custom Integration under Integrations in Sendlane.
03

Check the contact’s activity feed

Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.

FAQ

Questions about Loop Subscriptions and Sendlane.

What happens if a contact doesn’t exist in Sendlane?

Upstack only sends events for contacts that already exist in Sendlane. If the visitor’s email isn’t found in your account, the event is skipped, which keeps your account clean and targets only real subscribers.

Which events does Sendlane receive?

ViewContent as product-viewed-upstackified, AddToCart as added-to-cart-upstackified, InitiateCheckout as checkout-started-upstackified and Purchase as order-placed-upstackified.

Which customer parameters are sent to Sendlane?

Upstack looks up each contact in Sendlane by email or Sendlane contact ID, and sends the event only if the contact already exists.

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

Trigger a test action on your store, such as adding a product to cart, and check the contact’s activity feed in Sendlane. Events are sent only for contacts that already exist in Sendlane.

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

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