Why Adobe Analytics and your CDN numbers don't match
Every retailer who compares the two asks the same question. The short answer: Adobe measures consenting browsers that ran a JavaScript tag. The CDN logs every request from every client. The gap between them is not an error. It is a population of traffic your analytics was never designed to see.
Three populations, three numbers
Each measurement layer sees a strict subset of the one below it. Comparing their totals without knowing that is how teams end up distrusting both tools.
Everything: the CDN logs
Sees: Every HTTP request that reached your storefront. Browsers, API clients, scrapers, vulnerability probes, fake crawlers, feed pulls, monitoring. If it made a request, it is a log line.
Misses: Nothing. This is the denominator.
Some of it: JavaScript-executing clients
Sees: Real browsers, plus the minority of sophisticated bots that run a full headless browser.
Misses: API and JSON scrapers, raw-HTML harvesters, vulnerability scanners, fake Googlebots, curl scripts. None of these execute your page’s JavaScript, so no tag ever fires for them.
What Adobe reports: tagged, consented hits that survive filtering
Sees: Visitors whose browser ran AppMeasurement or the Web SDK, passed consent, was not blocked by an ad blocker, and was not removed by bot rules.
Misses: Everything above, plus consent decliners and ad-blocked sessions. Adobe measures customers, and it is good at that. It was never designed to measure traffic.
What lives in the gap
Ranked roughly by volume on a typical retail storefront.
Scrapers and API clients
Price harvesters, catalogue crawlers and JSON scrapers request pages and endpoints directly. They never execute JavaScript, so they are invisible to any tag-based tool, Adobe included. On retail storefronts this is routinely the single largest slice of the gap.
Fake crawlers
Traffic claiming to be Googlebot or Bingbot to slip through WAF allowlists. Real search crawlers do not run your analytics tag, and neither do the impostors. Cloudflare’s verified-bot signal exposes them at the CDN layer: a claimed crawler without the verified tag is a scraper in costume.
Vulnerability probes
Requests hunting for exposed .env files, WordPress paths and admin panels. Thousands of requests a day on a typical storefront, none of them ever seen by analytics, all of them in the CDN logs.
Consent decliners and ad blockers
Real humans whose browsers never fired the tag: they declined the cookie banner, or an ad blocker stopped AppMeasurement loading. They appear in CDN logs as ordinary browser traffic with no matching analytics hit.
Feeds, monitors and integrations
Google Merchant Center pulls, uptime monitors, partner integrations and your own SEO tooling. Legitimate, expected, and tagless.
A scraping operation from a single Vietnamese ISP ran against a Salesforce B2C Commerce storefront for two months: 34 million requests, 16.5 million successful responses, almost all bypassing cache and hitting origin.
Its analytics footprint was close to zero, because the scraper never executed a tag. The CDN logs recorded every request. If your Adobe number and your CDN number ever drift apart sharply, this is the first explanation to rule out, and the one tag-based tooling structurally cannot rule out for you.
How to quantify your gap on SFCC
Salesforce B2C Commerce exposes full request logs from its Cloudflare-powered eCDN via Logpush. That stream is the denominator. Blankitt Edge ingests it and answers the composition question directly: a traffic-quality scorecard splits human, suspicious, automated and unscored shares using Cloudflare bot scoring, and a bots-and-agents view separates verified crawlers from impostors. No tag, no storefront code, and nothing added to the pages Adobe measures.
Fair questions
Why is Adobe Analytics traffic lower than my server or CDN logs?
Because they measure different populations. Adobe Analytics counts visits from browsers that executed its JavaScript tag, passed consent, and survived bot filtering. CDN logs count every HTTP request from every client. Scrapers, API clients, vulnerability probes and fake crawlers never run the tag, and consent decliners and ad-blocked sessions never send a hit, so the CDN number is always larger. The size of the gap is itself a useful signal: on retail storefronts a large or growing gap usually means automated traffic.
Does Adobe Analytics count bot traffic?
Only bots that execute the tag, and only until a filter catches them. Adobe’s bot removal uses the IAB International Spiders and Bots list, which matches on user agent, plus custom rules on user agent and IP (verified against Adobe’s documentation, 10 July 2026). Simple bots that declare themselves are removed. Bots that never run JavaScript are never collected in the first place, so Adobe cannot report on them, and sophisticated bots that run a real browser with a clean user agent sail through as visits.
Do scrapers execute JavaScript analytics tags?
Mostly no. Running a full browser is expensive at scraping scale, so the overwhelming majority of scrapers request HTML or JSON directly. That is exactly why tag-based measurement undercounts automation: the traffic that costs you origin bandwidth and pollutes your data is the traffic the tag cannot see. The minority that do run headless browsers show up in analytics as suspiciously shallow visits.
How do I see the traffic Adobe misses on Salesforce B2C Commerce?
SFCC ships storefront traffic through a Cloudflare-powered eCDN, and the eCDN exposes full request logs via Logpush. That log stream is the complete denominator: every request, JavaScript or not. Blankitt Edge ingests it and shows the composition directly, including a traffic-quality scorecard (human, suspicious, automated and unscored shares based on Cloudflare bot scoring) and a bots-and-agents view that separates verified crawlers from impostors.
Does Blankitt Edge replace Adobe Analytics?
No, and it does not try to. Adobe Analytics measures customer behaviour: journeys, conversion, merchandising performance. Edge measures the request layer underneath it: what actually hit the storefront, how much of it was automated, and what to do about the abusive part. They answer different questions, and Edge’s job in an Adobe stack is to keep the traffic feeding your analytics honest.
Adobe Analytics is a trademark of Adobe Inc. Blankitt is an independent product and is not affiliated with Adobe. Adobe bot-filtering behaviour verified against Adobe's public documentation on 10 July 2026; corrections welcome at [email protected].