- 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 Gorgias. 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 lifeemail / phonesubscriber contactevent_typerenewal, swap, skip, pause, cancel or saveline_itemsproducts after any swaptotal / 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 purchase, one request, even when the order is amended.
- Bot and fraud filteringFraudulent orders never enter the request queue.
03 Activate
Delivered to Gorgias
Give support the resolved customer: every order and touchpoint attached to one profile.
See the Gorgias integration →
GorgiasWhat it receives email / phonematch the ticket to a customerorder historygive the agent contextexternal_idone profile, not three
The catch
A subscriber who swapped products has reviewed the wrong item unless the swap is carried through, because the review request references the original line item.
Where to check in GorgiasDelivery you can audit
Gorgias › open any ticket
The customer sidebar should show the full order history rather than a single order.
What changes
What changes when Loop Subscriptions feeds Gorgias. Two gains on the Gorgias side, two on the Loop Subscriptions side.
Gorgias
Server-side delivery
Events reach Gorgias through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Gorgias
Identity-resolved events
Events sent to Gorgias 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, Gorgias included, is forwarded the same resolved events.
Upstack dashboardExample
Loop Subscriptions Data source Connected
Gorgias Destination Healthy
Read the full Gorgias 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 Gorgias destination
Under Destinations, add Gorgias. Every resolved Loop Subscriptions event is then forwarded to it.
-
03
Check delivery to Gorgias
Trace any request back to the order and customer it came from.
FAQ
Questions about Loop Subscriptions and Gorgias.
How do I check that Loop Subscriptions events are reaching Gorgias?
Open Gorgias › open any ticket. The customer sidebar should show the full order history rather than a single order.
Will a customer be asked twice about one order?
No. One purchase, one request, even when the order is amended.
How long does it take to connect Loop Subscriptions to Gorgias?
Most brands are live in under 20 minutes. Once Loop Subscriptions is connected, every destination receives the same resolved events, Gorgias included.