Content Delivery Network (CDN) Server Side Setup Using CloudFlare
Learn step-by-step how to integrate Server Side CDN using CloudFlare and TAGGRS for an optimized user experience and more efficient content distribution. We explore the basics of a CDN and its benefits such as improved loading speed and reliability. Also important is the role of a Server Side CDN in the context of the latest iOS 16.4 update, where the use of CDNs provides a solution to the restrictions imposed on first-party cookies, important for effective marketing and analytics.
What is a Content Delivery Network (CDN)?
A Content Delivery Network, often abbreviated as CDN, is a network of servers spread across different geographical locations. The main purpose of a CDN is to efficiently and quickly deliver Internet content, such as Web pages, images, videos and other files, to users. By hosting content on servers closer to the end user, the load times of websites and other online services are significantly reduced.
Why should you use a CDN?
The main reasons to use a CDN are:
- Speed: Faster loading times for your website.
- Reliability: Less chance of website downtime during traffic spikes.
- Security: Better protection against cyber attacks.
Disney+ as a Practical Example of CDN Use
Disney+ demonstrates the power of CDN technology in the streaming world. When launching a new series, instantly accessible to a global audience, the CDN plays a crucial role. The content, hosted in the U.S., is almost immediately available to users in the Netherlands, thanks to local CDN servers. This approach eliminates long loading times and ensures a seamless viewing experience. The CDN reduces initial delays by storing content locally, making subsequent access attempts faster. This method highlights how CDNs increase the efficiency of content distribution in the streaming industry.
Taking advantage of CDN as a Webshop
The differences between web shops with and without the use of a Content Delivery Network (CDN) are:
Aspect | With CDN | Without CDN |
---|---|---|
Loading speed | Faster | Slower |
User Experience | Enhanced | May be reduced |
Server load | Reduced | Increased |
Performance during peak hours | High Quality | Can decrease |
Sales figures | Increased | May be lower |
This table highlights the benefits of using a CDN in terms of loading speed, user experience, and overall performance, especially during peak periods such as sales or special events.
Integrating CDN with Server Side Tracking.
Integrating a Content Delivery Network (CDN) with Server Side Tracking offers benefits to Web administrators. By using CDN functionality, it is possible to rotate your Server Side Google Tag Manager's (sGTM) custom domain. This allows sGTM traffic to be routed through your website's DNS provider.
This method ensures that the IP addresses of your website and the custom sGTM domain match. This has the significant advantage that cookies set by the Server Side are treated as first-party cookies. At a time when third-party cookies are under increasing pressure due to privacy laws and browser restrictions (such as Safari's), this approach provides a more reliable way to collect and analyze user data.
For example, advanced adblockers block these third-party cookies. Since due to the integration of CDN with Server Side Tracking, Cookies are considered first party cookies they cannot be blocked by adblockers.
Choosing the Right CDN Service
There are several CDN providers available, each with their own characteristics. We often see the following among our customers:
CloudFlare is known for its fast content delivery and strong security measures. This makes it a good choice for companies looking for an effective and secure CDN solution.
Setting up CDN using CloudFlare and TAGGRS
What do you need before you can begin:
1. Find DNS Settings subdomain within TAGGRS
Start by finding your subdomain's DNS settings in TAGGRS. These are available during container creation or can be found in your dashboard if you have already created a container. You will need these settings for the next steps in CloudFlare.
2. Website add CloudFlare part 1
If you already have a website operational on CloudFlare, proceed directly to step 6. If you haven't added a website yet, follow these steps: First, create an account with CloudFlare and then add a new website by clicking Get started.
3. Website add CloudFlare part 2
After entering the website name, click Continue. Then choose the desired plan (you can start for free) and click Continue again to continue.
4. DNS Records review main website
After selecting a plan, it's time to check the DNS Records. CloudFlare automatically collects the DNS Records known to them for your website. Check that these match the records within your own domain hosting. Are any records missing? If so, add them.
5. Name servers change within own hosting
The third step in the process of adding a Web site in CloudFlare is to find the nameservers within your hosting and change them for the new one. Nameservers are systems that link domain names to IP addresses, allowing Internet users to find your website. Replace these nameservers with the new ones from CloudFlare that you see in step 4. This will ensure that your domain is forwarded correctly through CloudFlare. Ready? Then click Done, check nameservers.
6. u003cstrongu003eExisting website selection on CloudFlareu003c/strongu003e
Then go back to your dashboard and select the website. If you already have a website running on CloudFlare, navigate to the Websites section and select that website.
7. DNS settings CloudFlare
Navigate to your DNS settings by clicking DNS in the overview.
8. Records subdomain creation CloudFlare
Then navigate to your DNS settings by clicking on DNS within your overview.
9. Add records subdomain CloudFlare
We are going to add the Records of the subdomain to CloudFlare. You do this by first clicking on Add record.
10. Validating DNS within TAGGRS
As you can see in step 1, next to the DNS settings is a button that says validate. Click this to validate the custom DNS. If the status changes to Validated, everything is set up correctly! Are you getting an error? Then check out our support page for more information.
11. Activate proxy status subdomain records
The last step is to reactivate the proxy status, which completes the DNS activation. You do this by clicking Edit and then setting the proxy status back to active. Then save the record and you have set up DNS Server Side via CloudFlare.
Server Side CDN in practice
Flowhub added a CDN to their Server Side Tracking, which led to a +4.02% increase in additional measured data. This is on top of the additional measured data due to Server Side Tracking. For more information, check out our Server Side CDN Case Study on this.
Conclusion
We've covered the steps for setting up a Content Delivery Network (CDN) with CloudFlare. This setup improves the speed, reliability and security of your Web site. Integrating a CDN with Server Side Tracking, as implemented with TAGGRS and CloudFlare, optimizes the user experience and increases the efficiency of your online presence. Curious about even more ways to improve your website? Then check out all our tools and solutions.
Happy Tagging!
Frequently asked questions CDN in combination with Server Side Tracking
Which server location should I choose within TAGGRS, given that our client operates globally and has users from different countries?
For Server Side Tracking, it is advisable to choose the server location in the country where the company is officially located. This helps in complying with the local privacy laws of that country. When you use a CDN you ensure that the servers load quickly wherever you are in the world.