Home
Connectors
Recharge - Loops

Send every Recharge event to Loops, server-side

Q: What permissions does the Loops API key need?

The key must have permission to write events and contacts, so Upstack can send events and create or update contacts.

Q: Which events does Loops receive?

ViewContent as Viewed Product, AddToCart as Added to Cart, InitiateCheckout as Started Checkout and Purchase as Placed Order.

Q: Which customer parameters are sent to Loops?

When Upstack identifies a visitor, it attaches the contact’s email and other known properties, and syncs profile properties including name, email and location to Loops.

Q: How do I check that Recharge events are reaching Loops?

Trigger a test action on your store, such as viewing a product or adding to cart, and check Events in Loops. In Upstack, the Real-Time Events feed under System, Events Manager shows the events as delivered to Loops.

Q: How long does it take to connect Recharge to Loops?

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

Each event is resolved to a person against a 750M+ device graph before it reaches Loops, so records and reporting reflect the person, not the device.

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 Recharge event reaches Loops. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.

See the Recharge integration

RechargeWhat it sends

subscription_idthe subscription, not the order
charge_ideach recurring charge
email / phonesubscriber contact
statusactive, cancelled, paused, reactivated
is_first_chargenew subscription versus renewal
product / frequencywhat they subscribed to and how often

02 Understand

Resolved to one person before it leaves

Every Recharge 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 person, one record, across devices and identifiers.
Bot and fraud filteringAutomated traffic never becomes a contact.

A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.

03 Activate

Delivered to Loops

Send resolved customer events to Loops for lifecycle messaging.

See the Loops integration

LoopsWhat it receives

emailcontact key
event namewhat the lifecycle message reacts to
data variablespersonalization

Which events reach Loops

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

Upstack event	Sent to Loops as	Key data on the event
Product view	Viewed Product	ProductName, ProductID, Price, ImageURL
Add to cart	Added to Cart	ProductName, ProductID, Price, Quantity, CartValue
Checkout	Started Checkout	CartValue, ItemCount, CheckoutURL
Purchase	Placed Order	OrderID, Revenue, Items, DiscountCodes

When Upstack identifies a visitor, it attaches the contact’s email and other known properties, and syncs profile properties including name, email and location to Loops.

The catch

Subscription state is not a property of an order.

It changes between them. A CRM fed only order events shows a customer as active long after they canceled.

Where to check in LoopsRecords you can audit

Loops the contact's event history

What changes

What changes when Recharge feeds Loops. Two gains on the Loops side, two on the Recharge side.

Loops

Server-side delivery

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

Loops

Identity-resolved events

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

Recharge

Subscriptions as their own conversion

Send new subscriptions to the ad platforms as a distinct event, not lumped in with one-time orders.

Recharge

Renewals counted properly

Recurring charges are forwarded as real revenue, so LTV reporting reflects what the customer is actually worth.

Setup

Live in under 20 minutes.

You need a Loops account where you can create an API key with write access to events and contacts.

Upstack dashboardExample

Recharge Data source Connected

Loops Destination Healthy

Read the full Loops setup guide

01

Connect Recharge

Bring subscription events into the same resolved customer: new subscriptions, renewals, churn and reactivation.
02

Add the Loops destination

Under Destinations, add Loops with an API key created under Settings, API in your Loops account. It is the only credential the destination needs.
03

Check events in Loops

Trigger a test action on your store, such as viewing a product or adding to cart, and check Events in Loops. In Upstack, the Real-Time Events feed under System, Events Manager shows the events as delivered to Loops.

FAQ

Questions about Recharge and Loops.

What permissions does the Loops API key need?

The key must have permission to write events and contacts, so Upstack can send events and create or update contacts.

Which events does Loops receive?

ViewContent as Viewed Product, AddToCart as Added to Cart, InitiateCheckout as Started Checkout and Purchase as Placed Order.

Which customer parameters are sent to Loops?

When Upstack identifies a visitor, it attaches the contact’s email and other known properties, and syncs profile properties including name, email and location to Loops.

How do I check that Recharge events are reaching Loops?

Trigger a test action on your store, such as viewing a product or adding to cart, and check Events in Loops. In Upstack, the Real-Time Events feed under System, Events Manager shows the events as delivered to Loops.