If you’re using the Releasit COD & Upsell app and keep seeing duplicate events, don’t worry, you are not alone. This is one of the most common frustrations merchants bring to us. What starts as a small glitch can quickly snowball into a real threat to your data quality. When an event fires twice, your ads optimize against inaccurate signals, your reports stop reflecting reality, and every decision you make for your store becomes harder. That’s why fixing duplicate events isn’t just a technical tweak. It’s an essential act for running profitable, data-driven campaigns.

So why do duplicate events happen? How do they affect your store? And how can you use Zotek together with Releasit without running into this problem?

In this blog, we’ll walk you through the main reasons duplicate events occur and show you the correct way to set up both apps. You’ll also learn how Zotek’s server-side tracking keeps your data clean, accurate, and reliable – helping you optimize ads and make better decisions with confidence.

How Releasit COD & Upsell Sends Tracking Events

Releasit tracks customer actions using both browser-based and form-based events.

1. Browser-based Purchase Event

For standard online payments, Releasit triggers a Purchase event directly from the customer’s browser.

This event is sent immediately to your connected tracking tools, capturing the transaction as soon as it happens.

2. COD Form Submission Event

For Cash on Delivery (COD) orders, Releasit automatically triggers a Purchase event when the customer submits the COD form.

This ensures that even offline payment orders are captured in your analytics.

3. Unified Tracking

Together, these mechanisms ensure that every transaction – whether paid online or via COD – is tracked reliably and sent to your analytics platforms in real time.

How Zotek Tracks Events Differently (Server-Side)

1. Server-Side Events (CAPI)

Unlike traditional browser-based tracking, Zotek sends events directly from your server to analytics platforms using Conversions API (CAPI).

This means actions like purchases, add-to-cart, or form submissions are recorded reliably, independent of the customer’s browser.

2. Bypassing Browser Blockers

Since server-side events do not rely on the user’s browser, they bypass ad blockers, cookie restrictions, and browser limitations.

This ensures that your data is captured accurately, even when client-side tracking fails.

3. Strengths of Server-Side Tracking

• Clean Data: Reduces noise from duplicate or blocked events
  
• Stable Values: Revenue, order IDs, and event parameters remain accurate
  
• No Over-Reporting: Only genuine customer actions are tracked
  

Using Zotek’s server-side tracking provides a more reliable view of your store’s performance, so your ad spend is guided by accurate, trustworthy data, not inconsistent tracking.

Why Zotek + Releasit COD Can Cause Duplicate Purchases

When using both Releasit and Zotek, duplicate Purchase events can occur due to the way each system tracks transactions:

• Browser Purchase from Releasit: Triggered directly from the customer’s browser when a purchase or COD form is submitted.
  
• Server Purchase from Zotek: Triggered from the server via Zotek’s server-side tracking (CAPI), recording the same order again.
  

Common Issues Merchants See:

• Orders appearing twice in analytics
  
• Revenue numbers being doubled
  
• Confusion in ad optimization and reporting

How duplication affects your ad performance

Duplicate Purchase events can cause:

• Inflated ROAS (looks higher than reality)
  
• Incorrect CPA
  
• Overreporting conversions
  
• Optimization issues because platforms think you’re getting more purchases than you actually are

Advertisers usually panic when they see duplicated events, but the solution is simply to control which app is allowed to send Purchase events.

How to Use Both Apps Together Without Duplication

What to Disable Inside Releasit

Inside Releasit, turn off all tracking options, especially its built-in Purchase event.
Releasit should only handle the COD form; it should not send any tracking events.

---

Where to Keep Tracking Enabled Inside Zotek

Keep all core events enabled in Zotek, including ViewContent, AddToCart, InitiateCheckout, Purchase, and any upsell-related events.
Zotek will act as the single, clean tracking source (server-side).

---

Recommended Settings for Accurate BFCM Tracking

For high-traffic periods like BFCM, make sure the following are enabled:

• Zotek server-side Purchase (CAPI)
  
• Zotek browser events (optional but recommended for remarketing)
  
• Releasit tracking OFF
  

This combination ensures no duplication while keeping data stable during scaling.

---

How to Verify Your Configuration

For Facebook (Meta)

• Go to Events Manager → Test Events.
  
• Trigger a COD order and confirm you see only one Purchase event, labeled as server-side.
  
• Ignore Pixel Helper – it cannot read Zotek’s server events.
  

For TikTok

• Go to Events Manager → Test Events
  
• Trigger a COD order
  
• You should see one Purchase event on Tiktok screenshot, coming from Zotek’s server-side tracking
  

If you see exactly one Purchase per order, your setup is configured correctly.

Final thoughts

Using Zotek together with Releasit COD & Upsell can deliver powerful, accurate tracking, as long as the setup is configured correctly. By letting Zotek handle all tracking server-side and keeping Releasit focused solely on the COD form, you ensure clean data, stable reporting, and zero duplicate Purchase events.

Whether you’re preparing for BFCM or scaling your ads year-round, this setup gives you a reliable foundation for optimization. With accurate events flowing into Meta, TikTok, and Google, your campaigns can finally perform based on real data – not inflated numbers.

Clean tracking isn’t just a technical upgrade; it’s a competitive advantage.