How to set up First-Party, Cookieless Tracking with Wicked Reports

On This Page

• Introduction
• How to Set Up Cookieless Tracking
• FAQ
  

With increasing privacy regulations (like GDPR and iOS updates) and browsers moving away from third-party cookies, first-party and server-relayed tracking methods have become essential for reliable attribution. By using our cookieless tracking method, you remove cookie dependence from the standard script and support stronger alignment with today’s strict privacy requirements.

Below are three reasons to use a DNS based, cookieless tracking solution instead of our traditional tracking code.

1. Stronger Privacy Alignment
   Events are captured in the browser and sent through your branded first-party domain. This removes the cookie dependence from our standard script and supports stronger compliance with modern privacy rules.
   
   
2. Increased Event Deliverability
   Because the event request uses a first-party domain, it is less likely to be blocked by browsers, privacy tools, or extensions. More tracking events successfully reach Wicked’s servers, which improves attribution quality.
   
   

3. Lightweight and Reliable Tracking
   Your first-party tracking setup avoids the heavy complexity of a strict, full server side implementation (these are rare). The browser still captures the event using a script, then relays it to our servers for processing. There, we can stitch it together with other event data passed into our server. Think of it as a server-side hybrid. This keeps the setup simple, stable, and easy to maintain while still improving consistency and accuracy.

How to Set Up Cookieless Tracking

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

Step 1: Contact Support

Reach out to our support team to request cookieless tracking setup.

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

• What to Mention:

  • Indicate that you would like to set up cookieless tracking for your domains.

  • Provide a list of domains where you want cookieless tracking enabled.
    Example: 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 cookieless 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 cookieless 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.