Skip to main content
Upstack Data

Custom stack to Loops

Forward every Custom stack event to Loops server-side, resolved to a person against a 750M+ device graph — so records and reporting reflect the person, not the device.

What changes

What changes when Custom stack feeds Loops.

Server-side delivery

Events reach Loops through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.

Identity-resolved events

Every event sent to Loops carries a resolved customer, matched against a 750M+ device graph.

Any stack, any framework

Headless, custom checkout, native app or a platform we haven’t listed — if it can make an HTTP request, it can send to Upstack.

The same event schema

Custom events are resolved, filtered and forwarded exactly like a Shopify order.

What actually moves

What Custom stack carries, and what Loops needs.

Custom stack and Loops describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Custom stack can put on an event, the right is what Loops can actually use.

Custom stack sends

event_name
whatever you choose to call it
user identifiers
any of email, phone, external ID
value / currency
if the event carries revenue
custom properties
any attribute in your own schema

Loops receives

email
contact key
event name
what the lifecycle message reacts to
data variables
personalisation

Records you can audit

How you know it is working.

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

  • Per-record inspection

    Trace any property back to the event that set it.
  • Deduplication

    One person, one record, across devices and identifiers.
  • Bot and fraud filtering

    Automated traffic never becomes a contact.

Where to check in Loops

Loopsthe contact's event history.

Get Custom stack talking to Loops.

A 15-minute walkthrough of this connector on your own account.