Introduction
When managing your domain through Cloudflare, you might come across an issue while setting up custom links in Customer.io. Specifically, this problem might occur if you're using the Full (Strict) SSL setting in Cloudflare.
Problem
Your domain is managed through Cloudflare and you have the SSL set to Full (strict). However, when setting up custom links in Customer.io, it doesn't fully verify the domain even though the link appears by default.
Solution
Cloudflare's Full (Strict) encryption mode is not supported for HTTPS link tracking in Customer.io. The reason for this because the Full (Strict) settings in Cloudflare require both the origin and the CNAME record to share the same common name... which isn't possible in this context because the origin is ours and uses our domain (e.customeriomail.com). Because of this, you will need to use Full encryption instead if you plan to use Cloudflare's proxy for link tracking.