- 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 HubSpot. 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 person, one record, across devices and identifiers.
- Bot and fraud filteringAutomated traffic never becomes a contact.
03 Activate
Delivered to HubSpot
Push identity-resolved events and contacts into HubSpot so CRM records match what actually happened.
See the HubSpot integration →
HubSpotWhat it receives emailthe contact keylifecycle propertiesstage and pipelinedeal / order valuerevenue on the record
The catch
Transaction state is the field that matters here and most CRM integrations do not carry it, so approved, declined and rebill collapse into one undifferentiated order stream.
Where to check in HubSpotRecords you can audit
HubSpot › the contact timeline
and the duplicate-management view, which should stop growing.
What changes
What changes when Phoenix Technologies feeds HubSpot. Two gains on the HubSpot side, two on the Phoenix Technologies side.
HubSpot
Server-side delivery
Events reach HubSpot through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
HubSpot
Identity-resolved events
Events sent to HubSpot 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, HubSpot included, is forwarded the same resolved events.
Upstack dashboardExample
Phoenix Technologies Data source Connected
HubSpot Destination Healthy
Read the full HubSpot 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 HubSpot destination
Under Destinations, add HubSpot. Every resolved Phoenix Technologies event is then forwarded to it.
-
03
Check delivery to HubSpot
Trace any property back to the event that set it.
FAQ
Questions about Phoenix Technologies and HubSpot.
How do I check that Phoenix Technologies events are reaching HubSpot?
Open HubSpot › the contact timeline, and the duplicate-management view, which should stop growing.
Will this create duplicate contacts?
No. One person, one record, across devices and identifiers.
How long does it take to connect Phoenix Technologies to HubSpot?
Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, HubSpot included.