- 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 Attentive. 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 order produces one event, so a single purchase cannot trigger the same flow twice.
- Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.
03 Activate
Delivered to Attentive
Feed resolved customer profiles into Attentive so SMS journeys trigger on people, not sessions.
See the Attentive integration →
AttentiveWhat it receives phonethe subscriber keyemailsecondary identifier for cross-channelevent propertieswhat the journey triggers on
The catch
A declined charge and a successful one are different states, but flows triggered on order events treat both as revenue and message accordingly.
Where to check in AttentiveSending you can audit
Attentive › the subscriber's timeline
where the event appears against the profile rather than as an unattached activity.
What changes
What changes when Phoenix Technologies feeds Attentive. Two gains on the Attentive side, two on the Phoenix Technologies side.
Attentive
Server-side delivery
Events reach Attentive through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Attentive
Identity-resolved events
Events sent to Attentive 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, Attentive included, is forwarded the same resolved events.
Upstack dashboardExample
Phoenix Technologies Data source Connected
Attentive Destination Healthy
Read the full Attentive 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 Attentive destination
Under Destinations, add Attentive. Every resolved Phoenix Technologies event is then forwarded to it.
-
03
Check delivery to Attentive
Trace any event to the profile it resolved to, and see why.
FAQ
Questions about Phoenix Technologies and Attentive.
How do I check that Phoenix Technologies events are reaching Attentive?
Open Attentive › the subscriber's timeline, where the event appears against the profile rather than as an unattached activity.
Can one purchase trigger the same flow twice?
No. One order produces one event, so a single purchase cannot trigger the same flow twice.
How long does it take to connect Phoenix Technologies to Attentive?
Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, Attentive included.