Zipify OCU → Branch · Conversion tracking
Connecting Zipify OneClickUpsell to Branch
Zipify's one-click post-purchase upsell adds a second charge to the same order without re-entering payment, which produces revenue that exists on the order but arrived after the conversion event. Branch's real job is the web-to-app seam — a person clicks a link in a browser, installs the app, and something has to carry the context across an install that destroys every cookie involved. The join between them succeeds or fails on one thing: whether the Branch link click identifier and the deferred deep link payload reaches the Zipify upsell order before the conversion happens, because Branch 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 Zipify OCU → Branch
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 Zipify OCU → Branch tracking rebuild — in their own words, on camera.
Why this join usually fails
The Branch link click identifier and the deferred deep link payload never reaches Zipify OCU
The single most common cause. The upsell flow runs after order creation, outside anything a checkout-time tag can see.
Two revenue numbers for one order
The checkout total and the settled total differ by whatever the upsell added. Reporting the first understates the campaign; reporting the second without noting the timing confuses anyone reconciling against the ad platform's window.
The install that erases the campaign
Someone clicks a paid ad on the mobile web, hits the app store, installs, and opens the app as a brand new anonymous user. Without deferred deep linking that campaign produced an organic install, and the ad account shows nothing for a conversion it genuinely caused.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. Branch shows the attributed link and campaign on the event in its dashboard. Check that the install carries a link click rather than showing as organic, which is the failure this product exists to prevent.
Architecture
How Zipify OCU and Branch actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Zipify OneClickUpsell holds the truth
Because the upsell charges the stored payment method, it becomes part of the same order rather than a new one. That makes the order total the right figure and the checkout total the wrong one.
Step 2
Branch needs a click to match
Branch needs the link click context matched to the app open, plus the event and its revenue. Without the deferred deep link payload there is nothing to join the install to.
Step 3
The identifier is the bridge
The Branch link click identifier and the deferred deep link payload, captured at the visit and carried into the Zipify upsell order. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send the final order total, with upsell take rate reported by campaign.
Step 5
Deduplication at the destination
Branch deduplicates on the event identifier you supply. Firing a purchase from both the SDK and your server without a shared identifier double-counts, and Branch forwards to downstream partners, so the duplicate propagates.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the Branch dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The Branch link click identifier and the deferred deep link payload present on the order
Visible on the record itself in Zipify OneClickUpsell, not merely captured somewhere on the site.
Sent from the Shopify order webhook
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
Branch deduplicates on the event identifier you supply. Firing a purchase from both the SDK and your server without a shared identifier double-counts, and Branch forwards to downstream partners, so the duplicate propagates.
Reconciles with the source
Branch's count and Zipify OneClickUpsell's records agree within a few percent over a closed window.
Actually broken
The Branch link click identifier and the deferred deep link payload missing on most records
The upsell flow runs after order creation, outside anything a checkout-time tag can see.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. The checkout total and the settled total differ by whatever the upsell added. Reporting the first understates the campaign; reporting the second without noting the timing confuses anyone reconciling against the ad platform's window.
Counted twice, or not at all
Someone clicks a paid ad on the mobile web, hits the app store, installs, and opens the app as a brand new anonymous user. Without deferred deep linking that campaign produced an organic install, and the ad account shows nothing for a conversion it genuinely caused.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Zipify OneClickUpsell. 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 orders carrying the Branch link click identifier and the deferred deep link payload
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Zipify OCU and into Branch.
- 3
Measure upsell take rate by traffic source
It varies enough by campaign to change which sources are genuinely most valuable.
- 4
Measure your organic install share and ask whether it is plausible
An implausibly large organic share is usually broken attribution rather than genuine word of mouth.
- 5
Read the match rate, not the success message
Branch shows the attributed link and campaign on the event in its dashboard. Check that the install carries a link click rather than showing as organic, which is the failure this product exists to prevent.
Source-of-truth validation
How it gets proven
Against Zipify OneClickUpsell's own records, not against either platform's dashboard.
- The Branch link click identifier and the deferred deep link payload confirmed present on a live order.
- A real conversion followed from click through Zipify OCU to Branch.
- Attributed installs and in-app purchases reconciled against your own user records, with the unattributed share stated.
- Final order totals reconciled against imported conversions, with take rate reported by source.
- 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 Branch already reports conversions that reconcile against Zipify OneClickUpsell'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 orders and count how many carry the Branch link click identifier and the deferred deep link payload. Ten minutes, free, and it tells you whether any of this is worth doing.
- Stores without post-purchase offers can report checkout value and skip the reconciliation timing question.
- If you have no app, or no web surface driving app installs, there is no seam here to bridge and the integration solves nothing.
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 Zipify OCU → Branch (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 Branch link click identifier and the deferred deep link payload on every order
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in Branch
8+ EMQThe event is attributed to the originating link and campaign, and forwarded to any configured downstream partners.
Reconciled against the source
DedupedZipify OneClickUpsell's own records are the reference, not either dashboard.
What gets built
Identifier capture into Zipify OCU
Send from the order webhook after the post-purchase sequence completes.
Event source: the Shopify order webhook
Send the final order total, with upsell take rate reported by campaign.
Dispatch to Branch
The Branch server-to-server events API, posted from your backend with the user identity and event data.
Reversals where they exist
Refunds reverse; upsell-only refunds should reduce rather than reverse the whole order.
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 Zipify OCU conversions showing in Branch?
Almost always because the Branch link click identifier and the deferred deep link payload never reached the Zipify upsell order. The upsell flow runs after order creation, outside anything a checkout-time tag can see. Measure coverage before debugging the dispatch.
02What identifier does Branch need?
Branch stores the click context and replays it into the app on first open, which is how a marketing campaign survives an install. That handoff is probabilistic on iOS and increasingly constrained, so the deep link data can arrive incomplete or not at all — and when it does not, the user looks organic.
03Where should the event come from?
The Shopify order webhook. Send the final order total, with upsell take rate reported by campaign.
04How do I know it worked?
Branch shows the attributed link and campaign on the event in its dashboard. Check that the install carries a link click rather than showing as organic, which is the failure this product exists to prevent.
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 yourZipify OCU → Branch 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 Zipify OCU → Branch 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 Zipify OCU and Branch 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
