# Recovering data with a CDN in front

Flowhub put a CDN in front of its Server-side Tracking and recovered 11.3% more data.

Source: https://taggrs.io/success-stories/flowhub/

## At a glance

- Story: Brand
- Business: B2B software
- Sector: B2B and lead gen
- Location: Netherlands

## A CDN in front of Server-side Tracking recovered more data

- **+11.3%** tracked data, after adding the server-side CDN
- **+4.02%** tracked data (vs the period before the CDN)

Source: The TAGGRS dashboard

## From a dashboard finding to a CDN

The fix started with a look at who the visitors were.

1. **Analyze the visitors** The TAGGRS dashboard showed that many of Flowhub's visitors use Safari, whose browser restrictions limit cookies.
2. **Put a CDN in front** A CDN routes the traffic of the server-side Google Tag Manager custom domain through the website's DNS provider, so the IP addresses line up.
3. **Compare in the dashboard** The tracked data after the CDN was compared with the period before it.

## Many visitors on Safari

Flowhub already ran Server-side Tracking with TAGGRS. An analysis in the TAGGRS dashboard then showed that many of its visitors use Safari.

That matters because Safari restricts cookies more than other browsers. Server-side Tracking alone does not remove every restriction: when the server that sets a cookie runs on IP addresses that differ from the website's own, Safari limits that cookie. Visitors who return after the limit look like new visitors, and part of the data is lost.

## Aligning the IP addresses with a CDN

To work around these restrictions, a Content Delivery Network (CDN) was added in front of the server-side setup. A CDN is a network of servers that sits between the visitor and the origin and passes requests on. Here it is used for where the tracking requests appear to come from.

The CDN routes the traffic of the server-side Google Tag Manager (sGTM) custom domain through the website's DNS provider. The tracking requests then come from the same place as the website itself, so the IP addresses line up and Safari's cookie restrictions have less effect.

## The result

After the server-side CDN went live, the TAGGRS dashboard showed 11.29% additional tracked data. That is 4.02% more than in the period before the CDN was implemented, when the server-side setup ran without it.

The comparison is made in the same dashboard that first showed the share of Safari visitors, so the before and after are measured the same way.

For a site where a large share of visitors browse with Safari, routing sGTM through a CDN is a small change in the setup that recovers data the server-side setup alone could not.

## About Flowhub

**B2B software from the Netherlands** Flowhub is a Dutch B2B software company. A large share of the visitors to its website use Safari.

## More success stories

- [Robey Sportswear records 57% more purchases](https://taggrs.io/success-stories/robey-sportswear/)
- [More of the funnel measured, from page view to purchase](https://taggrs.io/success-stories/flitsmeister/)

[All success stories](https://taggrs.io/success-stories/)
