Home
Connectors
Custom stack - Gorgias

Send every Custom stack event to Gorgias, server-side

Q: How do I check that Custom stack events are reaching Gorgias?

Open Gorgias › open any ticket. The customer sidebar should show the full order history rather than a single order.

Q: Will a customer be asked twice about one order?

No. One purchase, one request, even when the order is amended.

Each event is resolved to a person against a 750M+ device graph before it reaches Gorgias, so every touchpoint lands against one customer, not a fragment of one.

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

01 Capture

Captured from Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.

See the Custom stack integration

Custom stackWhat it sends

event_namewhatever you choose to call it
user identifiersany of email, phone, external ID
value / currencyif the event carries revenue
custom propertiesany attribute in your own schema

02 Understand

Resolved to one person before it leaves

Every Custom stack 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.

Post-purchase timing is the whole product. These controls exist so requests go to the right person at the right point.

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 customer
order historygive the agent context
external_idone profile, not three

The catch

Post-purchase tools expect an order shape.

A custom event has to be mapped to one, or the request has nothing to reference.

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 Custom stack feeds Gorgias. Two gains on the Gorgias side, two on the Custom stack 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.

Custom stack

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.

Custom stack

The same event schema

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

Setup

Post directly from your backend so nothing depends on the browser.

Connect Custom stack once and every destination, Gorgias included, is forwarded the same resolved events.

Upstack dashboardExample

Custom stack Data source Connected

Gorgias Destination Healthy

Read the full Gorgias setup guide

01

Connect Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
02

Add the Gorgias destination

Under Destinations, add Gorgias. Every resolved Custom stack event is then forwarded to it.
03

Check delivery to Gorgias

Trace any request back to the order and customer it came from.