- 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 Yotpo. 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 Yotpo
Enrich post-purchase touchpoints in Yotpo with identity-resolved order data.
See the Yotpo integration →
YotpoWhat it receives emailwho to ask for the revieworder_idwhich purchase the request is aboutproduct IDswhich product is being reviewed
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 YotpoDelivery you can audit
Yotpo › Reviews › the request queue
which should now contain the orders that previously had no email attached.
What changes
What changes when Phoenix Technologies feeds Yotpo. Two gains on the Yotpo side, two on the Phoenix Technologies side.
Yotpo
Server-side delivery
Events reach Yotpo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Yotpo
Identity-resolved events
Events sent to Yotpo 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, Yotpo included, is forwarded the same resolved events.
Upstack dashboardExample
Phoenix Technologies Data source Connected
Yotpo Destination Healthy
Read the full Yotpo 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 Yotpo destination
Under Destinations, add Yotpo. Every resolved Phoenix Technologies event is then forwarded to it.
-
03
Check delivery to Yotpo
Trace any request back to the order and customer it came from.
FAQ
Questions about Phoenix Technologies and Yotpo.
How do I check that Phoenix Technologies events are reaching Yotpo?
Open Yotpo › Reviews › the request queue, which should now contain the orders that previously had no email attached.
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 Yotpo?
Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, Yotpo included.