- 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 Okendo. 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 Okendo
Send resolved customers and orders to Okendo so review requests reach the right person.
See the Okendo integration →
OkendoWhat it receives emailwho to surveyorder_idthe purchase in questionproduct IDswhat to ask about
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 OkendoDelivery you can audit
Okendo › the review request schedule
checked against the same day's orders.
What changes
What changes when Phoenix Technologies feeds Okendo. Two gains on the Okendo side, two on the Phoenix Technologies side.
Okendo
Server-side delivery
Events reach Okendo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Okendo
Identity-resolved events
Events sent to Okendo 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, Okendo included, is forwarded the same resolved events.
Upstack dashboardExample
Phoenix Technologies Data source Connected
Okendo Destination Healthy
Read the full Okendo 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 Okendo destination
Under Destinations, add Okendo. Every resolved Phoenix Technologies event is then forwarded to it.
-
03
Check delivery to Okendo
Trace any request back to the order and customer it came from.
FAQ
Questions about Phoenix Technologies and Okendo.
How do I check that Phoenix Technologies events are reaching Okendo?
Open Okendo › the review request schedule, checked against the same day's orders.
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 Okendo?
Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, Okendo included.