The Profile Tracking JavaScript gathers browser attributes and distinguishes visitors by initiating HTTP network requests to the Experian servers. However, because fingerprinting can be sometimes used to compromise customers' privacy, ad blockers and browsers emphasizing privacy may obstruct these requests, hindering our ability to recognize visitors and potentially fraudulent activities.
Blocking tools such as Adblock or uBlock Origin, as well as privacy-focused browsers, actively block such requests. These tools keep a record of domains hosting the fingerprint API used for Profile Tracking, identifying and blocking browser requests associated with those domains. Certain VPN providers may also implement measures to block Profile Tracking domains at the DNS level.
The most effective method to prevent the blocking of JS agent requests is to route them through your own domain. Instead of directly accessing the Profile Tracking APIs, you invoke a proxy function hosted on your domain or subdomain, such as x2y.yourdomain.com. This proxy function then forwards the request to the Profile Tracking API.
By adopting this approach:
This strategy enhances both the efficiency and precision of visitor identification.
A subdomain may only consist of a combination of letters, numbers and hyphens.
Example of valid subdomains:
If you operate with several brands and multiple countries, it is sufficient for you to align the subdomains with the brands.
Example:
In this case, you can assign exactly 3 subdomains (1 subdomain for each brand) and use the corresponding subdomain for the respective countries.
Please create a CNAME entry (e.g. (string).(yourdomain).com) that points to the Experian server with the following URL - whm.asip.cloud.
Notes:
Experian uses the Let’s Encrypt automated service and carries out the necessary configuration activities. You will be informed after the configuration activities are finished.
