Home
Integrations
StackAdapt

StackAdapt integration: identity-resolved conversions, sent server-side

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

Request a demo Start free trial

Role: Destination
Category: Ad platforms
Pre-built connectors: 12 sources
Plans: All plans

What Upstack sends

Every conversion reaches StackAdapt with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources

order_idShopify order and checkout token
email / phonecustomer contact from checkout
customer_idShopify customer record, if they have one
line_itemsproducts, variants and quantities
total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

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.

Out: to StackAdaptOn every event

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

Programmatic conversions with identifiers.

See the set-up reference See all 12 sources How resolution works

About StackAdapt

Upstack forwards resolved conversions from the server with identifiers attached, so every channel StackAdapt buys is measured against the same order data.

Comparing display to CTV becomes a real comparison rather than an artifact of which one the browser could track.

What StackAdapt is

StackAdapt runs programmatic buying across display, native, video, connected TV and audio from one platform.

Running one campaign across five surfaces makes consistent conversion measurement the hard part.

How StackAdapt works

StackAdapt attributes conversions through its pixel and server-side integrations, across channels with very different attribution characteristics. A connected-TV impression and a display click cannot both be measured well by a browser tag.

What you can do with it

Three jobs this connector does inside StackAdapt.

Send complete conversions

Conversions reach StackAdapt through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

Optimize on the customer you want

Map any order attribute to the conversion StackAdapt receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

One measurement basis across channels

Every surface is judged against the same resolved orders, so budget moves between channels on merit rather than on tracking quality.

Pre-built connectors

12 sources connect to StackAdapt. Whichever of these you run, StackAdapt is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for StackAdapt as a destination.

FAQ

StackAdapt integration questions.

What does Upstack send to StackAdapt?

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

Which plans include the StackAdapt integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to StackAdapt?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.