Server-side tracking
Browser-side pixels lose events to ad blockers, tracking prevention, and people who close the tab too fast. Soran records purchases from the server, so the conversions that matter arrive whatever the browser did.
browser
server
Blockers, tracking prevention, and a tab closed before the script runs each take their cut of what a browser can send. Purchases recorded server-side are not subject to any of it, so the events your budget depends on are the ones that always arrive.
There is one tracker for your site and Soran sets it up. There is no second copy to keep in step.
Checkout and thank-you page events come with the connection. The storefront needs the theme app embed switched on.
Setup shows how many events came in over the last 24 hours. That number, and not a status light, is what tells you the tracking is live, and it is the first thing worth reading when a conversion rate looks impossible.
Signal loss
Orders go straight from your store, so nothing can block them. Soran attaches every match key it holds and forwards them onward.
Ad blockers, tracking prevention, a declined consent banner. The event never sends, and the platform treats what is left as the truth.
Coverage depends on what you collect, not on what a browser allowed. Soran shows the gaps for every destination.
The loudest ad looks cheapest, so it takes your next increase. Soran ties spend to the ad that actually earned it.
Connect your store
Shopify authorizes in a click and checkout tracking installs itself.
Pick a goal
The conversion you actually get paid for. Soran credits every touch that led to it.
Read your first report
Spend against the revenue it earned, on all ten attribution models.