Get your Sellfy tracking to 95%+ accuracy guaranteed in writing.
Sellfy is built for creators, but its native pixel integrations leave half your iOS customers invisible to Meta and Google. We add a server-side CAPI gateway driven by Sellfy webhooks so every download, every POD purchase, every iOS user gets attributed.
Free30 minutesNo obligation
Sellfy · what breaks
Sellfy tracking issues
- 01
iOS gap is total
Browser-only Pixel.
- 02
Digital products break advanced matching
Default integration skips most params.
- 03
POD margins are tight
Wasted ad spend kills profitability fast.
Sellfy · the fix
Outcomes — Sellfy
Webhook-driven CAPI
100% reliable Purchase events.
EMQ 8+
Full advanced matching.
GA4 e-com clean
All events typed.
Sellfy · architecture
How a Sellfy order should reach the ad platforms
Sellfy sells digital products through a hosted checkout, which means the buying moment happens somewhere you cannot put a script and the delivery moment happens with no browser at all.
- 1
Click identifiers captured at first touch
Click IDs are captured on the store or embed page at landing and written to a first-party cookie, because Sellfy's hosted checkout does not carry your query parameters forward.
- 2
The browser sends the fast, fragile copy
Store page and embed code fire the browsing and checkout-start events. The hosted checkout is closed, so the browser path stops there.
- 3
The order itself is the source of truth
The Sellfy order — and specifically the successful payment — is the truth. The buyer often goes straight to a download link and never renders a confirmation page you control.
- 4
A server container sends the authoritative event
The Sellfy webhook posts the completed order to a GTM server container on your own subdomain, keyed on the Sellfy order ID.
- 5
Customer identity raises match quality
The order carries buyer email, which for a digital product is usually the only identity field that exists. Hashed server-side, it is what carries match quality here.
Sellfy · events
The event set we build on Sellfy, and where each one comes from
Digital-product funnels are short. The event set is correspondingly small, and the purchase is doing nearly all the work.
| Event | Fires when, on Sellfy | Key parameters | Sent from |
|---|---|---|---|
| view_item | A product or embed page renders | item_id, value, currency, event_id | Browser + server, deduped |
| begin_checkout | The hosted checkout opens | value, currency, num_items, event_id | Browser + server, deduped |
| purchase | The Sellfy webhook confirms a completed payment | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
| refund | A refund is issued | order_id, value, currency | Server only |
Sellfy · normal or broken
Digital-product tracking realities — Sellfy
Digital selling removes the shipping step and with it most of the funnel you would normally measure.
Normal, not a fault
A very short funnel with few events
There is no cart, no shipping and no address step. Fewer events is the product working, not tracking missing.
No script access inside the hosted checkout
Expected — and the reason the webhook does the real work.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.
Actually broken
Purchase tracked from a thank-you page the buyer skips
Digital buyers frequently go straight to the download. Those sales are never counted.
Click IDs never reaching the order
The hosted checkout drops them unless they are captured and passed deliberately.
Refunds never reported back
Digital products have high refund rates in some categories, and reported return stays permanently inflated.
Sellfy · prove
How we prove the Sellfy build is correct
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
Sellfy order records
- The Sellfy webhook confirmed delivering for a real completed payment.
- Click IDs confirmed present on the order record.
- Refunds confirmed reversing the conversion in at least one platform.
- Purchase count within a few percent of sellfy order records for a fully closed week, matched on order ID rather than on totals.
- No order ID appearing twice in any platform's event log.
- Deduplication confirmed at every destination that supports it.
- Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
- The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.
Sellfy · free audit
What we check in the free audit
- iOS gap is total
- Digital products break advanced matching
- POD margins are tight
Sellfy · when not to buy
When a Sellfy rebuild is not what you need
We would rather say this now than three weeks into an engagement.
- You sell a single product at low volume with minimal ad spend.
- You are using Sellfy to test an idea rather than run a business on it.
- You are moving to a platform with a checkout you control.
Sellfy · what we deliver
Deliverables — Sellfy
Sellfy webhook gateway
1st-party server-side GTM
Meta CAPI + Google EC
Verified
QA + handover
Notion runbook
Written guarantee
95%+ tracking accuracy
Measured against Sellfy order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Foundation pixel install for your Sellfy store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.
- One-time fee · zero monthly · zero SaaS lock-in
- Sellfy dataLayer (clean spec)
- GA4 e-commerce events
- Meta Pixel · Google Ads tag
- TikTok Pixel · Microsoft UET
- Consent Mode v2 banner integration
- QA test orders + 7-day support
- No CAPI · no iOS recovery
1st-party server-side
Recommended$800One-time fee · most popular
The done-for-you package every Sellfy store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.
- One-time fee · save vs SaaS subscriptions over 5 years
- Fully recovered + built in 2–4 days · accurate data in 7 days
- Everything in browser-side starter
- 1st-party server-side GTM (your subdomain)
- Meta CAPI · full advanced matching · 8+ EMQ
- Google Enhanced Conversions (Web + Leads)
- TikTok Events API · Microsoft UET server
- Deterministic browser ↔ server deduplication
- Live EMQ verification + screenshots
- Notion runbook + 30-day support · zero recurring
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel running 1st-party server-side, end-to-end. For Sellfy brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.
- One-time fee · save 6-figure SaaS subscriptions over 5 years
- Everything in 1st-party server-side tier
- Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
- Klaviyo identity stitching (if used)
- BigQuery export (server logs + GA4)
- Looker Studio attribution dashboard (branded)
- Multi-region / multi-currency / EU residency
- GDPR-audit-ready Consent Mode v2 wiring
- 60-day support · optional retainer · no lock-in
FAQ
Sellfy questions, answered
Probably not yet — start with browser-side. We'll tell you straight if it's not the right time.
More on Sellfy
- GuideServer-Side Tracking Explained: What It Is, How It Works, and Who Actually Needs It (2026)
- GuideServer-Side Tracking for Shopify: The 2026 Setup That Actually Works
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
WhatsApp