Phoenix Technologies to X
Forward every Phoenix Technologies event to X server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Phoenix Technologies to X with Upstack Data
Phoenix Technologies
Capture Phoenix Technologies orders from the server, including the upsell sequence, so the complete order value reaches every downstream tool.
Phoenix Technologies integration
X
Server-side conversions to the X Conversions API, resolved to a person and deduplicated against the browser pixel.
X integrationWhat changes
What changes when Phoenix Technologies feeds X.
Server-side delivery
Events reach X through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to X carries a resolved customer, matched against a 750M+ device graph.
Every event, server-side
Storefront and checkout events are captured from Phoenix Technologies on the server, independent of the browser.
One setup, every destination
Connect Phoenix Technologies once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Phoenix Technologies carries, and what X needs.
Phoenix Technologies and X describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Phoenix Technologies can put on an event, the right is what X can actually use.
Phoenix Technologies sends
- order_id
- Phoenix order reference
- email / phone
- contact from the order record
- line_items
- initial purchase and any upsells
- total / rebill_amount
- first charge separated from recurring
- transaction_state
- approved, declined or rebill
- customer_type
- new or returning, resolved before send
X receives
- hashed email / phone
- identity matching on arrival
- twclid
- credit the click that drove it
- external_id
- stable person across sessions
- event_id
- dedupe against the browser pixel
- value / currency
- value-based bidding
Delivery you can audit
How you know it is working.
Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in X
X AdsToolsEvents Manager. The events table separates browser and server events, so a deduplicated pair shows as one conversion.
Related connectors
Other places Phoenix Technologies can send to.
- Phoenix TechnologiesMeta Conversions API
- Phoenix TechnologiesGoogle Ads Conversions
- Phoenix TechnologiesTikTok Events API
- Phoenix TechnologiesPinterest
- Phoenix TechnologiesSnapchat
- Phoenix TechnologiesReddit
- Phoenix TechnologiesMicrosoft Ads
- Phoenix TechnologiesAppLovin
Other sources that feed X.
- ShopifyX
- WooCommerceX
- BigCommerceX
- Checkout ChampX
- RechargeX
- Custom stackX
- FunnelishX
- Lasso CommerceX
- SkioX
- Loop SubscriptionsX
- StripeX
- Everything X can take12 sources feed X, and the setup is the same for each one.X integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Phoenix Technologies talking to X.
A 15-minute walkthrough of this connector on your own account.