Home
Connectors
Phoenix Technologies - StackAdapt

Send every Phoenix Technologies event to StackAdapt, server-side

Q: How do I check that Phoenix Technologies events are reaching StackAdapt?

Open StackAdapt › Conversions › Conversion tracking. Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

Q: Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

Q: How long does it take to connect Phoenix Technologies to StackAdapt?

Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, StackAdapt included.

Each event is resolved to a person against a 750M+ device graph before it reaches StackAdapt, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial

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 StackAdapt. 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 reference
email / phonecontact from the order record
line_itemsinitial purchase and any upsells
total / rebill_amountfirst charge separated from recurring
transaction_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.
DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

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.

03 Activate

Delivered to StackAdapt

Server-side conversions to StackAdapt with hashed identifiers attached, so multi-channel programmatic is measured on your orders.

See the StackAdapt integration

StackAdaptWhat it receives

hashed email / phoneidentity matching on arrival
sa_click_idcredit the click that drove it
external_idstable person across sessions
event_iddedupe against the browser pixel
value / currencyvalue-based bidding

The catch

Rebills look exactly like new orders to an ad platform.

Forwarding them as conversions teaches the algorithm to bid for customers you already have, and inflates acquisition performance by the entire recurring base.

Where to check in StackAdaptDelivery you can audit

StackAdapt Conversions Conversion tracking

Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

What changes

What changes when Phoenix Technologies feeds StackAdapt. Two gains on the StackAdapt side, two on the Phoenix Technologies side.

StackAdapt

Server-side delivery

Events reach StackAdapt through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

StackAdapt

Identity-resolved events

Events sent to StackAdapt 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, StackAdapt included, is forwarded the same resolved events.

Upstack dashboardExample

Phoenix Technologies Data source Connected

StackAdapt Destination Healthy

Read the full StackAdapt 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 StackAdapt destination

Under Destinations, add StackAdapt. Every resolved Phoenix Technologies event is then forwarded to it.
03

Check delivery to StackAdapt

Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Phoenix Technologies and StackAdapt.

How do I check that Phoenix Technologies events are reaching StackAdapt?

Open StackAdapt › Conversions › Conversion tracking. Server-side conversions are labeled by source, so a deduplicated pair is visible as one.

Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

How long does it take to connect Phoenix Technologies to StackAdapt?

Most brands are live in under 20 minutes. Once Phoenix Technologies is connected, every destination receives the same resolved events, StackAdapt included.