Custom Domains & Cloudflare

Connect a domain

Add the domain in your website's Domains settings, then create this DNS record at your DNS provider:

Type:   CNAME
Name:   www  (or @ / your subdomain)
Target: domains.escalateflow.com

SSL is issued automatically. DNS changes usually apply within minutes (up to 48 h). For the root domain (example.com), use CNAME flattening or an ALIAS/ANAME record if your provider supports it.

EscalateFlow caches the pages that look the same for every visitor and serves them from a server close to each visitor. Personal pages (A/B tests, members' areas, logged-in visitors, cart and checkout, campaign URLs with utm_*/fbclid) are never cached. Edits are published to the cache within seconds.

If your domain's DNS is in your own Cloudflare account

If you are not using Cloudflare for this domain, you can skip this section. If you are, your Cloudflare zone's settings apply before ours. With Cloudflare's default settings everything works; check these points:

Required

• SSL/TLS → Edge Certificates → Always Use HTTPS: On. Without it, a visitor who types http:// can get a cached copy instead of being redirected to https://.
• The CNAME record to domains.escalateflow.com must be Proxied (orange cloud) for caching to work. With DNS only (grey cloud) your site works, but without caching.

Do not use

• "Cache Everything" with an Edge TTL that ignores the origin's cache-control (Cache Rules or Page Rules). This would cache personal pages and show them to other visitors (A/B variants, members' areas, carts).
• A fixed Browser Cache TTL (Caching → Configuration). Keep Respect Existing Headers, otherwise visitors do not see your edits.
• Workers that rewrite your pages or their headers.
• Blocking POST /_ef/pv with WAF rules, rate limiting or bot challenges. It is the request that counts your page views.

These turn caching off (your site still works, just slower)

• Development Mode on (Caching → Configuration).
• A Cache Rule with Bypass cache, or a Page Rule with Cache Level: Bypass.

Recommended: a cache rule in your zone

Caching → Cache Rules → Create rule → Custom filter expression → Edit expression:

(ssl and http.request.method in {"GET" "HEAD"} and not http.cookie contains "ef_site_session" and not http.cookie contains "sessionid")

• Cache eligibility: Eligible for cache
• Edge TTL: Use cache-control header if present, bypass cache if not (never "Ignore cache-control header")
• Browser TTL: Respect origin TTL

Check your setup

# run twice: the second answer should say "cf-cache-status: HIT"
curl -sI https://example.com/ | grep -i cf-cache-status

# should answer 301 with "location: https://example.com/"
curl -sI http://example.com/ | grep -iE "^HTTP|location"

• HIT: cached. MISS/EXPIRED: fetched now, the next request is cached.
• DYNAMIC on a normal page: something in your Cloudflare zone turns caching off (see above).
• BYPASS: a personal page (cart, members' area…). This is expected.
• http:// answering 200: turn on Always Use HTTPS.
• No cf-cache-status header: the domain is not proxied by Cloudflare.

Español: dominios propios y Cloudflare

Conectar un dominio

Añade el dominio en Domains de tu web y crea en tu proveedor de DNS un registro CNAME hacia domains.escalateflow.com. El SSL se emite solo. EscalateFlow guarda en caché las páginas que se ven igual para todos y las sirve desde un servidor cercano a cada visitante. Las páginas personales nunca se cachean: tests A/B, zonas de miembros, visitantes con sesión, carrito, checkout y URLs con utm_*/fbclid. Las ediciones llegan a la caché en segundos.

Si el DNS de tu dominio está en tu propia cuenta de Cloudflare

Obligatorio:

• SSL/TLS → Edge Certificates → Always Use HTTPS: On. Sin esto, quien escribe http:// puede recibir una copia en caché en vez de la redirección a https://.
• El CNAME hacia domains.escalateflow.com en Proxied (nube naranja). En nube gris la web funciona, pero sin caché.

No uses:

• "Cache Everything" con un Edge TTL que ignore el cache-control del origen. Cachearía páginas personales y se las mostraría a otros visitantes.
• Un Browser Cache TTL fijo. Déjalo en Respect Existing Headers, o tus visitantes no verán tus cambios.
• Workers que reescriban tus páginas o sus cabeceras.
• Bloquear POST /_ef/pv con reglas WAF, rate limiting o desafíos anti-bots. Es la petición que cuenta tus visitas.

Desactivan la caché (la web funciona, pero más lenta): Development Mode activado, una Cache Rule con Bypass cache o una Page Rule con Cache Level: Bypass.

Recomendado: crea en tu zona una Cache Rule con la expresión de arriba, con Eligible for cache, Edge TTL Use cache-control header if present, bypass cache if not y Browser TTL Respect origin TTL.

Comprobar: los dos comandos curl de arriba. La segunda petición debe dar HIT, y http:// debe responder 301 hacia https://.