Home > Tracking Campaigns > Voluum

---

Voluum Custom domain + Namecheap + Cloudflare Question (7)

---

Hey STM'ers

I was wondering if anyone could chime in on whether it even makes a difference in speed or security to connect cloudflare's DNS to a namecheap domain and then point to the dedicated tracking url through cloudflare?

Currently, have my custom domain setup directly from namecheap to Voluum. I have 3 SSL's in Voluum so i dont need cloudflare for a free SSL so im just looking to see if theres another reason to use cloudflare in addition to the current setup.


& if it does make a difference are there any settings that would need to be switched on cloudflare so that it works optimally?

I think the only ones i know of are "ignore query string" & "flexible SSL" but theres some that are already toggled ON such as brotoli compression & always https which im not sure would even be necessary.

---

Do you want to only use Cloudflare DNS, or Cloudflare DNS+Proxy (cache/security)?

---

Honestly, i'm not even sure which one , if any that i want to use.
I noticed that others were using that setup & was curious if it was even worth it to use cloudflare for my click url if im using cloudflare on my landing page urls.
I could see where it would make a difference with a self hosted tracker but im just not sure if its something that would be a best practise to do with a Voluum click url for speed.

Ive seen people who have had good experience using cloudflare cause Namecheaps DNS's are "slow" and it also adds security if youre running bh/gh. On the other hand, ive seen situations where cloudflare is causing issues and is making the domain show as an unsafe domain or cache is too long and is causing clicks to go unaccounted for etc(maybe with self hosted trackers im not sure).

So i was wondering if it would be a best practise to use cloudflare for my click url & some best practise settings

---

I use CloudFlare for the DNS only, because it is fast. The other option of having a proxy will probably not work, as the SSL certificate issued by CloudFlare will not work with Voluum.
If you want to be faster, the best option is to use the Direct Pixel / Redirectless method.

---

i see , thanks @jeremie . Yeah i dont need cloudflare's SSL since i have 3 with Voluum anyways so no need for the proxy.

would you mind sharing your DNS only cloudflare settings?
These are what i have that are "on" the rest are off
https://prnt.sc/u9vs2i
https://prnt.sc/u9vs7u
https://prnt.sc/u9vsog
https://prnt.sc/u9vsxd
https://prnt.sc/u9vt5z
https://prnt.sc/u9vtah
https://prnt.sc/u9vtgt
https://prnt.sc/u9vu2b

i know some of these settings are not important whatsoever, but if theres something that can potentially cause any issue id rather be safe than sorry.

Also i noticed a firewall message https://prnt.sc/u9vsgg even though there are no firewall rules. if i'm not mistaken the 503 error is probably because only the subdomain path is pointing to my dedicated Voluum domain, i think to fix that id have to url redirect the customurl.com to the subdomain.customurl.com ... but i just dont know how to fix that in cloudflare lol

do these settings look similar to yours?

thanks again

---

As soon as you select DNS only (first screen), all the others settings are irrelevant as they relate to proxy. I have the same settings: DNS Only.
When you call directly your tracker URL, without any parameters and referrer, it returns 404 (most of the time), or 451 (when the user has opted-out from voluum tracking). Runnind a speed test therefore does not make a lot of sense,

---

ohh that makes sense now! hence why voluums instructions dont include changing any other settings!

Thanks @jeremie for the help!

---

Home > Tracking Campaigns > Voluum