How to set up Cookieless (Server-Side) Tracking with Wicked Reports

This document walks through the process of setting up Cookieless (Server-Side) tracking on your domains.

On This Page

• Introduction
• How to Set Up Server-Side Tracking
• FAQ
  

Introduction

With increasing privacy regulations (like GDPR and iOS updates) and browsers phasing out third-party cookies, server-side tracking has become useful for accurate marketing attribution.

Here are the Top 5 Reasons to use server-side tracking over traditional client-side tracking like Pixels and Javascripts:

1. Enhanced Data Quality: Since tracking events are sent directly from your server, they can’t be blocked by ad blockers, cookie restrictions, or browser crashes—giving you far more complete and reliable data.
2. Resilience to OS and Browser Changes: Server-side tracking keeps working even when browsers roll out new privacy features, so your attribution doesn’t break. Because events are sent from your server—not the browser—browser-based updates like iOS Link Tracking Protection or Safari’s ITP can’t block or strip your data..
3. Stronger Privacy Compliance: With server-side tracking, organizations can intercept, filter, and anonymize data before sending it to third-party platforms, making GDPR and CPRA compliance easier and more robust.
4. Greater Control and Security: Server-side tracking reduces your risk of exposing sensitive data to third parties. Because all data passes through your own server first, you decide exactly what to keep, strip out, or mask before sending it anywhere else.
5. Faster Website Performance: Shifting tracking tasks away from the browser reduces script load and device processing demands, speeding up websites and improving user experience and conversion rates.

How to Set Up Server-Side Tracking

We make the process of setting up server-side tracking straightforward. Follow these steps to get started:

Step 1: Contact Support

Reach out to our support team to request server-side tracking setup.

• How: Email support@wickedreports.com or submit a ticket.

• What to Mention:

  • Indicate that you would like to set up server-side tracking for your domains.

  • provide a list of domains where you want server-side tracking enabled
    • Example:

• • • • www.yourwebsite.com

      • shop.yourwebsite.com

      • landing.yourwebsite.com

Step 2: Receive CNAME Records from Support

Once your domains are provided, our support team will generate a set of CNAME records for you.

You will receive the following for each domain:

• CNAME Record Name

  • ex. abc123.yourwebsite.com

• CNAME Record Target

  • ex. yourclientname.track.wickedreports.com

Step 3: Update Your DNS Settings

Using the provided CNAME records, you or your web developer will need to update your domain's DNS settings.

• Access your domain provider's DNS settings (e.g., GoDaddy, Cloudflare, Namecheap, etc.).

• Add each CNAME record exactly as provided by support.

Step 4: Update Your Tracking Code

After your DNS records are set up, support will provide you with a new version of the Wicked Reports tracking script.

• Replace the existing Wicked Reports tracking script on your website with the new version.

• Ensure you update the script on every domain you provide.

Step 5: Validate Tracking

Once your DNS records are live and the new tracking script is installed, let our support team know.

• We will help verify that tracking is working correctly.

That's it. You've completed your server-side tracking! 

FAQ

What cookie does my standard tracking use?
The standard tracking code only stores UTM-related data in a single cookie.

What if I don’t update my tracking script after setting up server-side tracking?
Your tracking will not work properly, and Wicked Reports won’t be able to attribute conversions correctly.

What should I do if I encounter issues during setup?
Our support team is here to help. Contact us at support@wickedreports.com.