Skip to main content
Magistry
Start free

// tracking & attribution

Bid on profit, not on a leaky pixel.

Browser pixels lose a fifth of your conversions before the platforms ever see them. Magistry tracks server-side on your own domain, stitches identities across devices, delivers conversions to four ad platforms at once — and turns verified margins into POAS bidding.

Start free
How POAS works
Server-side · first-party 4-platform CAPI delivery POAS gated on verified costs
app.magistry.io/dashboard/tracking
Trackingserver-side · first-party
pixel-loss proof
event stream · live
  • purchase$86.00identity · 3 touchpointsevt_8f31
  • add_to_cart$129.00identity · 1 touchpointevt_8f2e
  • page_view—new visitorevt_8f2b
conversion delivery
  • Googledelivered
  • Meta CAPIdelivered
  • TikTokdelivered
  • Pinterestqueued
profit on ad spend
2.1poasROAS 3.4
bidding on margin, not revenue

// the pipeline

From click to attributed profit.

Four stages, all running on your store's own data. No third-party cookie roulette, no attribution windows that change under you with every platform policy update.
01

First-party event ingest

A server-side pixel captures page views, carts, and purchases on your own domain — immune to ad blockers and browser tracking prevention that silently eat 20–40% of pixel events.

02

Identity graph

Events stitch into one customer identity across sessions, devices, and channels. The purchase that started on a phone and finished on a laptop counts as one journey, not two strangers.

03

Multi-platform delivery

Every conversion is delivered server-to-server to Google, Meta, TikTok, and Pinterest at once — deduplicated, enriched, and matched. The platforms bid on complete data instead of a leaky pixel.

04

Attribution modeling

An active attribution model assigns credit across touchpoints, so channel reports agree with your bank account instead of each platform claiming the same sale.

// poas

The number that actually pays your bills.

Revenue-based bidding rewards selling low-margin products at scale. Profit-based bidding rewards selling the right products. Magistry computes POAS per SKU from the same cost ledger the Catalog Agent prices against.

Profit, not revenue

ROAS treats a $80 sale with $8 margin the same as one with $40 margin. POAS feeds verified cost data into the bid signal, so spend chases contribution — not vanity revenue.

Gated by cost confidence

POAS bidding only activates on SKUs with Tier-A verified costs. No invented margins, no optimizing on guesses — the same cost-confidence gates the Catalog Agent uses.

poas · SKU-2231 · 14d window
revenue        : $2,840
ad_spend       : $836
roas           : 3.4

cost_tier      : A  (Shopify cost_per_item)
cogs           : $1,082
fees+shipping  : $312
contribution   : $1,446

poas           : 1.73   (profit ÷ spend)
bid_signal     : contribution-weighted value
delivered_to   : google · meta · tiktok · pinterest

// same spine

Tracking lives on the audit plane too.

Conversion deliveries are logged, attribution model changes are versioned, and the POAS inputs trace back to cost rows you can inspect. When a number looks off, you can see exactly where it came from.
Identity data stays in your tenant — RLS-isolated Vault-encrypted platform credentials Delivery retries are idempotent Attribution model is inspectable, not a black box

// get started

Stop bidding blind.

Install Magistry, connect your ad accounts, and watch the event stream fill — server-side, first-party, profit-aware.

Start free
Book a demo

Free plan · No credit card · First 24 hours run in dry-run