Content delivery networks
This article explains what a CDN is and how to configure an SSL certificate for all links.
Content Delivery Networks (CDNs) are an effective way to serve content quickly and easily across multiple platforms and manage security certificates. We recommend CloudFlare for Content Delivery Networks with Wooxy.
Additionally, Wooxy provides the option to automatically generate an SSL certificate. More information is available in the specific article.
CDN setup with CloudFlare
These instructions require an existing Cloudflare account using either a Full DNS or CNAME setup. A comparison of these two configurations is available here. Note! The CNAME setup is restricted to Cloudflare Business or Enterprise plans.
Additionally, a valid branded link must be configured on the account before proceeding, as this step is essential for the subsequent process to function correctly.
Step-by-step instructions
The process begins by logging into the Cloudflare account and navigating to the DNS settings for the required domain.
A new CNAME record must be added, pointing the configured branded link domain to the value of the first CNAME record used for domain verification, see here. The proxy status must be enabled.
The next step is to navigate to the Page Rules section for the domain. A new Page Rule must be created for the branded link domain, setting the SSL mode to “Full”. This configuration is required for Cloudflare to properly validate the certificate on the origin server. Detailed information regarding various SSL options is available here.
The Page Rule status must be set to 'On' for the configuration to take effect.
Upon completion of these steps, contact Wooxy Support to request activation of SSL click and open tracking. After verifying the configuration, the setting will be enabled for the account.
A final validation of the CDN settings by the Wooxy Support team is required to finalize the activation of SSL-based tracking.
Custom SSL setup
If using a CDN for SSL is not preferred, a custom SSL setup can be used instead to ensure click- and open-tracking.
Steps to сonfigure a сustom SSL
A proxy must be prepared to receive all inbound traffic from link.yourdomain.com and forward it to the value of the first CNAME record used for domain verification. Such a proxy can be implemented using services and tools such as NGINX, Amazon API Gateway, or similar alternatives.
The proxy must be configured to use either HTTP or HTTPS. For HTTPS, a valid SSL certificate for the branded link domain must be provided to the proxy.
Forwarding traffic from inbound emails requires configuring the Host HTTP header with the corresponding branded link domain.
The CNAME record at the hosting provider must be pointed to the proxy server. For example: CNAME mailing.example.com -> proxy.example.com.
