Introduction

Setting up a DNS reverse proxy on a WAF such as CloudFlare is an easy and reliable way of tracking first.

Unlike Third Party Tracking, which relies on cookies and scripts from third parties to track user behaviour on several sites, First Party Tracking enables a company to better control and secure the data collected.

Benefits of First Party Tracking

1. Regulatory compliance: By using first-party data, companies can better comply with privacy regulations such as the GDPR in Europe or the CCPA in California.

2. Data reliability: Data collected directly is often more accurate and reliable, as it comes from direct interactions between the user and the company.

3. Greater control: Companies have total control over how data is collected, stored and used, reducing the risks associated with using third-party services.

4. Enhanced user experience: Insights gained from First Party Tracking can be used to personalise and improve the user experience on corporate platforms.

First Party Hosting

We recommend using First Party Hosting to host the container. This involves modifying the cdn.commanders domain by creating two CNAMEs.

First Party Tracking methods

CNAME

• Description: The CNAME (Canonical Name) is a type of DNS record used to redirect a domain to another domain. This method is often used to mask the origin of requests, by making the tracking appear to be first party.

• Limitation with ITP: Intelligent Tracking Prevention (ITP), a feature found in browsers such as Safari, detects redirects via CNAME and blocks them to prevent unwanted tracking. This limitation reduces the effectiveness of the CNAME method for tracking users.

A Record

• Description: The A Record is a DNS record that redirects a domain to a specific IP address. Unlike CNAME, this method redirects directly to an IP and was not detected by ITP until recently.

• Limitation with ITP: ITP has evolved and applies new rules by comparing the locations of the two IPs. If the IPs are too far apart geographically, ITP can cut the connection, making this method less effective too. With this solution, the user has to create his own Master ID (CAID).

Proxy

• Description: The Proxy acts as an intermediary where requests first pass through the customer's server before being redirected to our server. This makes it possible to mask the origin of the requests and pass them off as first-party traffic.

• Implementation :

  • Customer development: Requires technical intervention by the customer to set up the proxy server capable of handling high traffic.

  • WAF Proxy (Web Application Firewall): The WAF manages the configuration and redirects requests to our servers. A common example is the use of Cloudflare, but other options such as CloudFront exist.

• Advantages :

  • Master ID: The proxy makes it possible to track visitors throughout their visit to the site, thanks to a cookie placed by the WAF. This Master ID can be generated by our system.

  • Reliability and control: The customer can configure a CNAME in the WAF (e.g. Cloudflare) to redirect requests securely.

Conclusion

First-party tracking methods via CNAME and A Record can no longer be used to circumvent the limitations imposed by ITP. Each method presents specific advantages and challenges, requiring careful evaluation to choose the solution best suited to each context. Proxy, with the use of a WAF, appears to be a robust option for maintaining reliable and secure user tracking.