- 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 Phoenix Technologies event reaches Gorgias. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Phoenix Technologies
Capture Phoenix Technologies orders from the server, including the upsell sequence, so the complete order value reaches every downstream tool.
See the Phoenix Technologies integration →
Phoenix TechnologiesWhat it sends order_idPhoenix order referenceemail / phonecontact from the order recordline_itemsinitial purchase and any upsellstotal / rebill_amountfirst charge separated from recurringtransaction_stateapproved, declined or rebill
02 Understand
Resolved to one person before it leaves
Every Phoenix Technologies 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
High order volume with guest checkout produces many partial customer records, so review requests go to fragments of a person rather than to the person.
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 Phoenix Technologies feeds Gorgias. Two gains on the Gorgias side, two on the Phoenix Technologies 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.
Phoenix Technologies
Every event, server-side
Storefront and checkout events are captured from Phoenix Technologies on the server, independent of the browser.
Phoenix Technologies
One setup, every destination
Connect Phoenix Technologies once and forward to every ad platform, email tool and warehouse you run.
Setup
Live in under 20 minutes.
Connect Phoenix Technologies once and every destination, Gorgias included, is forwarded the same resolved events.
Upstack dashboardExample
Phoenix Technologies Data source Connected
Gorgias Destination Healthy
Read the full Gorgias setup guide → -
01
Connect Phoenix Technologies
Capture Phoenix Technologies orders from the server, including the upsell sequence, so the complete order value reaches every downstream tool.
-
02
Add the Gorgias destination
Under Destinations, add Gorgias. Every resolved Phoenix Technologies 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 Phoenix Technologies and Gorgias.
How do I check that Phoenix Technologies 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 Phoenix Technologies to Gorgias?
Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, Gorgias included.