Osano → PartnerStack · Conversion tracking
Connecting Osano to PartnerStack
Osano handles consent alongside vendor risk and data subject requests, which means a deletion request arriving through it has consequences for data you already sent to ad platforms. PartnerStack commissions partners on recurring subscription revenue rather than on a single order, which makes it the one destination here where a conversion you send creates a payment obligation that repeats every month. The join between them succeeds or fails on one thing: whether the PartnerStack referral key reaches the Osano consent and subject request record before the conversion happens, because PartnerStack can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Osano → PartnerStack
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Osano → PartnerStack tracking rebuild — in their own words, on camera.
Why this join usually fails
The PartnerStack referral key never reaches Osano
The single most common cause. Identifier capture is gated on consent, and a later deletion request means the identifier must be removed from your own records as well.
Deletion requests that stop at your database
The data was sent onward. A subject request handled only internally leaves hashed identifiers sitting in several ad platforms, which is the part an audit asks about and the part almost nobody has built.
A commission that recurs on revenue that stopped
The mirror of the usual problem. If cancellations are not reported back, partners keep earning on subscriptions that churned months ago. Every conversion pipeline needs reversals; this one needs them because real money leaves the building otherwise.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. PartnerStack shows attributed customers and accruing commission per partner. Reconcile the commissionable revenue against your billing system's active subscriptions, not against its historical sales.
Architecture
How Osano and PartnerStack actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Osano holds the truth
A subject deletion request is not just a database operation. Conversions already sent to platforms carrying hashed identifiers may need deletion requests raised there too, and most implementations never wire that path.
Step 2
PartnerStack needs a click to match
PartnerStack needs the referral key, the customer identifier and the subscription value. Recurring commission also needs the ongoing revenue reported, not just the first payment.
Step 3
The identifier is the bridge
The PartnerStack referral key, captured at the visit and carried into the Osano consent and subject request record. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send consented conversions, and raise platform-side deletion requests when a subject request is received.
Step 5
Deduplication at the destination
Deduplication is on your customer identifier. Reporting the same subscription twice creates two commissionable relationships against one paying customer, and the error compounds monthly rather than once.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the PartnerStack dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The PartnerStack referral key present on the consent record
Visible on the record itself in Osano, not merely captured somewhere on the site.
Sent from your order system, gated on consent
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Deduplication is on your customer identifier. Reporting the same subscription twice creates two commissionable relationships against one paying customer, and the error compounds monthly rather than once.
Reconciles with the source
PartnerStack's count and Osano's records agree within a few percent over a closed window.
Actually broken
The PartnerStack referral key missing on most records
Identifier capture is gated on consent, and a later deletion request means the identifier must be removed from your own records as well.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. The data was sent onward. A subject request handled only internally leaves hashed identifiers sitting in several ad platforms, which is the part an audit asks about and the part almost nobody has built.
Counted twice, or not at all
The mirror of the usual problem. If cancellations are not reported back, partners keep earning on subscriptions that churned months ago. Every conversion pipeline needs reversals; this one needs them because real money leaves the building otherwise.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Osano. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count consent records carrying the PartnerStack referral key
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Osano and into PartnerStack.
- 3
Trace where a single customer's data actually went
List every destination that received it. That list is what a deletion request has to reach, and producing it is usually the first time anyone has.
- 4
Check whether churn events reach PartnerStack at all
In most implementations the new-subscription path was built and the cancellation path was not, because only one of them is exciting.
- 5
Read the match rate, not the success message
PartnerStack shows attributed customers and accruing commission per partner. Reconcile the commissionable revenue against your billing system's active subscriptions, not against its historical sales.
Source-of-truth validation
How it gets proven
Against Osano's own records, not against either platform's dashboard.
- The PartnerStack referral key confirmed present on a live consent record.
- A real conversion followed from click through Osano to PartnerStack.
- Commissionable recurring revenue reconciled against active subscriptions in billing, with cancellations proven to reverse.
- Consented conversions reconciled, plus a demonstrated deletion path to every destination that received customer data.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If PartnerStack already reports conversions that reconcile against Osano's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred consent records and count how many carry the PartnerStack referral key. Ten minutes, free, and it tells you whether any of this is worth doing.
- If you send no customer identifiers to any platform, the deletion propagation problem does not arise — and that is worth confirming rather than assuming.
- If you run no partner or affiliate programme, there is nothing to send here. If you run one on one-off sales rather than subscriptions, the recurring-commission complexity does not apply to you.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Osano → PartnerStack (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
The PartnerStack referral key on every consent record
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in PartnerStack
8+ EMQThe customer is attributed to a partner, and commission accrues against the recognized revenue on the schedule you configured.
Reconciled against the source
DedupedOsano's own records are the reference, not either dashboard.
What gets built
Identifier capture into Osano
Capture after consent, store the identifier where a deletion request can reach it, and wire the downstream deletion path before you need it.
Event source: your order system, gated on consent
Send consented conversions, and raise platform-side deletion requests when a subject request is received.
Dispatch to PartnerStack
Server-side reporting from your billing system, with the referral key, customer identifier and the recurring revenue as it is recognized.
Reversals where they exist
Deletion requests should propagate to every destination that received the customer's data.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Osano conversions showing in PartnerStack?
Almost always because the PartnerStack referral key never reached the Osano consent and subject request record. Identifier capture is gated on consent, and a later deletion request means the identifier must be removed from your own records as well. Measure coverage before debugging the dispatch.
02What identifier does PartnerStack need?
PartnerStack attributes through a referral key carried on the link and stored against the customer. Because commissions are frequently paid on recurring revenue for the life of the subscription, losing the key does not cost a partner one commission — it costs them the whole relationship's worth, and produces a dispute you cannot resolve after the fact.
03Where should the event come from?
Your order system, gated on consent. Send consented conversions, and raise platform-side deletion requests when a subject request is received.
04How do I know it worked?
PartnerStack shows attributed customers and accruing commission per partner. Reconcile the commissionable revenue against your billing system's active subscriptions, not against its historical sales.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourOsano → PartnerStack setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Osano → PartnerStack setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Osano and PartnerStack joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
