Skip to main content
Upstack Data

Loops integration: identity-resolved events and contacts

Send resolved customer events to Loops for lifecycle messaging.

Role
Destination
Category
Analytics & CRM
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every event reaches Loops attached to one person. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

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.
  • DeduplicationOne person, one record, across devices and identifiers.
  • Bot and fraud filteringAutomated traffic never becomes a contact.
Out: to LoopsOn every event
  • emailcontact key
  • event namewhat the lifecycle message reacts to
  • data variablespersonalization

Lifecycle messaging on resolved customers.

About Loops

Loops keeps the tooling simple, which puts the weight on the event feed.

Upstack supplies a resolved contact and a clean event stream, so lifecycle messages fire against the right person at the right stage, with personalization variables that are actually populated.

What Loops is

Loops is a lifecycle email platform built for modern product and ecommerce teams, focused on transactional and behavioral messaging.

Lifecycle messaging depends on knowing where a person actually is in their lifecycle, which requires their events to resolve to one record.

How Loops works

Loops is built around contacts and events. A contact is keyed on email; events sent through the API trigger loops: sequences of messages with delays and conditions between them. Data variables sent alongside the event are available for personalization in the message body. It is deliberately simpler than a full marketing-automation suite, which puts more weight on the event feed being correct.

What you can do with it

Three jobs this connector does inside Loops.

01

Send complete conversions

Conversions reach Loops through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion Loops receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Lifecycle that knows the stage

Messaging fires against a resolved customer, so lifecycle stage reflects everything the person has done rather than what one device saw.

Pre-built connectors

12 sources connect to Loops. Whichever of these you run, Loops is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Loops as a destination, next to the Loops developer docs.

FAQ

Loops integration questions.

What does Upstack send to Loops?

Send resolved customer events to Loops for lifecycle messaging.

How do I connect Loops to Upstack?

Under Destinations, add Loops with an API key created under Settings, API in your Loops account. It is the only credential the destination needs. You need a Loops account where you can create an API key with write access to events and contacts.

How do I check that 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.

Which plans include the Loops integration?

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

How is this different from connecting Loops directly to Shopify?

Standard Shopify integrations only see visitors Shopify has identified, typically logged-in customers or shoppers who entered an email at checkout. Upstack matches anonymous sessions to known customer profiles and sends those events to Loops with the contact’s email attached, so your workflows fire for many more visitors.

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.

Similar integrations

Other destinations to send to.

See all integrations

Get Loops tracking right.

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