Server-side tracking gives you the most reliable way to attribute revenue and conversions to the right marketing sources. Instead of relying solely on the visitor's browser, key details about a purchase are captured by your server during checkout and sent securely to EazyData. This means your attribution remains accurate even when ad blockers or privacy extensions try to prevent scripts from running in the browser. If client-side tracking is like observing a visitor as they browse, server-side tracking is like your back-office accounting system confirming exactly what was sold, when it happened, and which campaign brought the customer in the first place.
The end result is simple but powerful: every sale is connected to a specific visit and traffic source, so you know which campaigns truly drive revenue. This is especially valuable for e‑commerce, SaaS subscriptions, and any business where understanding return on ad spend matters. Server-side tracking works alongside client-side tracking — the two complement each other. Client-side gives you rich behavioral context in real time; server-side ensures the final transaction is recorded and attributed with maximum accuracy.
When someone visits your site, EazyData creates anonymous identifiers for the visitor and their session. These are stored as secure cookies in the browser. Later, when the visitor starts checkout, your server reads these identifiers and includes them with the payment request (for example, as metadata in Stripe or LemonSqueezy). Because the data is attached on the server, it cannot be blocked by browser tools. After payment succeeds, EazyData receives a webhook from your payment provider and links the transaction to the original session and traffic source.
You can think of this as a simple chain: visit ➝ session ➝ checkout ➝ purchase ➝ attribution. The visit and session identifiers tell us who browsed (anonymously), the checkout code passes those identifiers along with the order, and the webhook confirms the purchase. EazyData stitches this together automatically, so your revenue reporting reflects the full customer journey from first click to completed payment.
Importantly, no personal details are required for this to work. The identifiers are random tokens used only to connect a purchase back to the correct session. This approach keeps your analytics privacy‑friendly while providing the business accuracy you need.
For server-side tracking, EazyData focuses on the essentials required for accurate attribution: anonymous visitor and session identifiers, basic order details (such as amount, currency, and items), and timing information that tells us when the transaction happened. Combined with the marketing source recorded during the visit (for example, a campaign, social platform, or referrer), this lets you see which channels reliably generate actual revenue — not just clicks.
Because the connection is made on your server, you avoid gaps caused by ad blockers, disabled JavaScript, or network conditions that might interfere with client‑side tracking. The outcome is a clear, trustworthy view of performance that your finance and marketing teams can both rely on.
Setup is straightforward. First, ensure the EazyData client-side script is installed on your site so visitor and session identifiers are created during browsing. Next, in your server-side checkout code, read the ED_visitor_id and ED_session_id cookies and pass them along with the payment request (for instance, as metadata fields). Finally, verify that webhooks from your payment provider are reaching EazyData so purchases can be confirmed and attributed.
After this is in place, make a test purchase. In your EazyData dashboard, you should see the transaction appear shortly after, connected to the correct session and traffic source. From there, your revenue dashboards will continue to update automatically as real purchases happen.
EazyData supports popular payment providers such as Stripe and LemonSqueezy, with more being added over time. The pattern is always the same: read the anonymous identifiers on the server, include them with the order, and let EazyData link the dots via webhooks.
Server-side tracking is designed to be both accurate and respectful. The identifiers used are random and anonymous. Only the order details necessary for attribution are processed, and data is transmitted securely between your server, your payment provider, and EazyData. If your compliance requirements call for consent, you can structure your checkout so identifiers are included only after consent is granted.
Many teams use server-side tracking alongside client-side tracking to get the best of both worlds: rich, real‑time behavior data as people browse, and bulletproof attribution when money changes hands. If you’re starting from scratch, we recommend enabling client-side tracking first and adding server-side tracking when you’re ready to measure revenue with total confidence.