Voluum and CheckoutChamp Events Tracking Integration

Accurate conversion tracking is the foundation of profitable media buying. There's not to much ways to send event postbacks in CheckoutChamp platform, so if you need simple way, it's better to use JavaScript code to send events from a user's browser(Client-To-Server) to your Voluum TDS.

When integrating Voluum with CheckoutChamp, one of the most common approaches is to use a JavaScript tracking code placed inside the checkout pages. This script captures user actions (such as page views, purchases and upsells) and sends them to Voluum as conversion events.

JavaScript Tracking Code for CheckoutChamp Pages

This code will send a begin_checkout and purchase events to your Voluum tracker. Make sure your Voluum events have appropriate names.

The code contains snippets that you need to add to the relevant pages of your CheckoutChamp platform.

Replace your-voluum.domain to your real Voluum domain.

Download code from Github Gist

We're using utm_medium=xo to tag our traffic and utm_term={clickid} for the user clickID, so in your Voluum offer you need to add this parameters and your offer link will look like https://store.url/product?utm_medium=xo&utm_term={clickid}

Also make sure, that all of your pages is using same domain, because the tracking code relies on a window.localStorage browser feature.

Upsides of Using JavaScript Tracking Code

• Quick Implementation. Easy to set up directly in CheckoutChamp without server-side development. Works by simply inserting the script snippet in the page.
• Event Flexibility. Can fire multiple event types (purchase, upsell, rebill) based on page triggers or button clicks. Allows custom event naming for better reporting in Voluum.
• Real-Time Tracking. Events are passed to Voluum immediately once the user action happens. Useful for fast optimization decisions and A/B testing.
• Client-Side Data Enrichment. JavaScript can capture browser data, referrer and UTM parameters, then forward them to Voluum. Helpful for deep attribution and granular reporting.

Downsides of Using JavaScript Tracking Code

• Reliance on Browser Execution. If the user disables JavaScript, blocks scripts with ad blockers, or the page fails to load fully, events may not fire. Can lead to partial underreporting of conversions.
• Less Reliable Than Server-to-Server (S2S) Tracking. Browser-side tracking depends on cookies and scripts, which can be blocked or cleared. S2S postbacks are generally more accurate because they fire from CheckoutChamp’s server.
• Data Manipulation Risks. Since the code runs client-side, advanced users could theoretically tamper with event firing. This is rare but possible, unlike with server-to-server events.

When to Use JavaScript

• Best suited for fast setup and testing when you need to start tracking quickly.
• Works well for small to medium campaigns where some margin of error in reporting is acceptable.
• For long-term scaling, adding server-to-server postbacks alongside JavaScript tracking is recommended to ensure maximum accuracy.

JavaScript tracking is easy to deploy and flexible, but it is less reliable than server-side integrations. For CheckoutChamp + Voluum, many media buyers start with JS tracking and later combine it with S2S postbacks for complete data accuracy.