Global CDN and server location¶
Two parts of the infrastructure matter for your container's performance: where it runs and how the content reaches the visitor. They are independent — processing happens in one place, delivery in another.
Server location¶
Containers run in SA East (Brazil).
That means tag processing — the part that decides what to send, where and with which data — happens in Brazil. For a mostly Brazilian audience, that cuts the time between your site and the server.
The value appears on the container page, in the Infraestrutura section, as Localização do servidor.
Global CDN¶
All containers on the shared hostname are delivered by Cloudflare. The CDN spreads delivery across the network edge, closer to the visitor, which improves page speed and SEO optimizations.
The CDN is standard and cannot be disabled. There is no setting, dashboard or plan that turns it off.
What the CDN delivers
The CDN handles the delivery of the files. Processing still happens on the server in SA East. A request leaves the Cloudflare edge and travels to the server to be processed — the two roles do not replace each other.
Custom domains use your provider's network¶
When you connect a custom domain, traffic goes through the network of your own DNS provider — not through the AdPulse CDN.
The dashboard shows this in the connected-domain section: "Seu domínio usa a rede do seu provedor de DNS."
| You use | Where traffic goes |
|---|---|
| The platform's shared hostname | Cloudflare |
| A custom domain | Your DNS provider's network |
This is not a limitation imposed by AdPulse: it is how routing on your own hostname works. If your provider also uses a CDN, traffic goes through it.
Plan the hostname before connecting
The hostname choice affects two things at once: where the traffic flows and the chance of ad blocker blocking. It is worth deciding both together.
What this is not¶
- It is not a region choice. The server location is the same for every container on the platform.
- It is not a tag cache. The CDN speeds up delivery; it does not store tag results nor replace execution on the server.
- It is not configurable per container. There is no per-container, per-plan or per-environment option.