Edge Measurement

Edge Measurement runs a small Cloudflare Worker in front of your storefront, so Fond counts visits from answer engines at your own edge. It is under Settings → Integrations for the website, and it needs a Premium plan.

Edge Measurement is still rolling out, and Fond switches it on per account. Until then, your website has no Cloudflare card. No setting of yours turns it on.

It is separate from the Google Analytics connection. Analytics tells you what visitors did after they arrived. Edge Measurement tells you what arrived at all.

What it adds over Google AnalyticsCopy Anchor Link

Analytics runs as JavaScript in the browser, so an ad blocker or a consent banner can hide a visit from it. The Worker runs on Cloudflare's network and sees the request in both cases.

It also counts AI crawlers such as GPTBot, ClaudeBot and PerplexityBot. They run no JavaScript, so Analytics does not record them. Edge Measurement records which of your pages they crawl and how often.

Fond can check each crawler's address against published vendor ranges. That check is not live yet, and the page says so.

Fond reads the referrer at the edge, so referral counts do not depend on how Analytics grouped them.

Collection starts when you connect. The AI Traffic page shows which pages AI crawlers fetched and which bot fetched each one. It also shows referrals as your edge saw them, beside the Google Analytics figures.

Before you installCopy Anchor Link

Cloudflare's free plan allows 100,000 Worker requests per day across your whole Cloudflare account, and every storefront request counts. A busy store can go over this limit, so compare your plan with your traffic first.

Your domain must already be on Cloudflare, or you must move it there. Fond tells you which path you are on before you start. On Cloudflare already, setup is a token and a one-click install, with no DNS changes.

The certificate hazard, if you are moving DNS to CloudflareCopy Anchor Link

A failure here gives no warning, and it occurs weeks later.

Your store's TLS certificate renews when it answers a challenge at /.well-known/acme-challenge/. If Cloudflare's Always Use HTTPS setting redirects that path, the certificate does not renew. Your store becomes insecure about a month later, when the current certificate expires.

While Edge Measurement is connected, these settings must keep these values:

Fond records all three before it advises any change, then checks them again on a schedule. If one changes back, Fond tells you.

Permissions the API token needsCopy Anchor Link

Create a Custom token on Cloudflare's API Tokens page. Under Zone Resources, select Include → Specific zone → your store's domain.

Add the permission rows that Fond's setup screen lists, each with a copy button. Use that list and no other, including this page. Fond checks your token against the same list.

If a row does not match Cloudflare's dropdown, tell us. Do not pick the nearest match. A token that is missing one permission fails partway through setup.

What Fond collectsCopy Anchor Link

For each request, the Worker reports the timestamp, page path, query string, referring page, user agent and status code. Three limits apply inside your own Cloudflare account, before any data gets to Fond:

The Worker reduces query strings to an allowlistCopy Anchor Link

Only utm_*, ref and gclid stay, so an email address or an order id in a query string never leaves your infrastructure. A parameter that nobody expected is removed too.

The Worker collapses identifiers in the pathCopy Anchor Link

The Worker reports /account/reset/6789/9f8a... as /account/reset/:id/:token. Product paths such as /products/blue-linen-shirt stay as they are.

The Worker keeps network addresses only for crawlersCopy Anchor Link

The Worker keeps an IP only when the user agent matches a known AI crawler. Human visits carry no IP.

Fond deletes raw request rows after 30 days. It keeps the daily totals built from them, so your history stays.

What the Worker cannot seeCopy Anchor Link

The Worker cannot see orders or revenue. Cloudflare does not run Workers on /checkout, because Shopify excludes it. Revenue still comes from your Google Analytics connection.

It sees the request, not the session. It cannot tell you scroll depth, time on page, or which button a visitor clicked.

It cannot attribute visits from inside an assistant's mobile app. These arrive with no referrer, and no tool can attribute them unless the engine tags its own links. Your real figure is therefore higher than any tool shows.

It cannot see traffic that a service other than Cloudflare serves.

Removing itCopy Anchor Link

When you disconnect, Fond uses your token to delete the Worker route and script from your Cloudflare account, then discards the token. It then shows a restore checklist, built from the settings it recorded before it advised any change.

Read that checklist before you change settings back. If you turn Always Use HTTPS back on, certificate renewal breaks again, whether or not Fond is connected.

Fond keeps the data it already collected. If you connect the same domain again, collection continues from where it stopped.