Ad blockers are dropping Croct calls from our React SPA, how do people fix it?
a slice of our visitors never fire any calls to Croct. I sat in the network tab on a machine with a blocker on and the requests to the evaluate, track and content endpoints just never leave, they match common blocklists.
So those users get default content and no tracking. How do others keep this working for people running ad blockers?
1 answer
That is blocklists like EasyList and EasyPrivacy matching the evaluate, track and content endpoints by pattern. The standard remedy is first-party proxying: route the requests through your own domain using baseEndpointUrl and cidAssignerEndpointUrl so they no longer look like third-party calls to a blocker.
<CroctProvider appId="..." baseEndpointUrl="https://yourdomain.com/_croct" cidAssignerEndpointUrl="https://yourdomain.com/_croct/cid"> <App /></CroctProvider>Worth stressing this is a configuration change plus a proxy on your side, not a rewrite of any personalization logic. The slots and audiences stay exactly as they are.