In website analytics, teams encounter a persistent trade-off:
- Put heavy tracking pixels at the top of
<head>, and they delay DOM rendering, degrade Core Web Vitals (LCP, INP), and increase mobile bounce rates. - Defer tracking scripts (
async,defer), and 20–30% of mobile users leave before the script transmits its first payload.
Edge Click Tracking addresses this trade-off by handling initial request logging at the network edge.
1. Edge compute architecture
In traditional analytics setups, click payloads travel across the internet to an origin server located in a single datacenter.
Sply routes traffic through globally distributed edge nodes located close to the end user.
User taps paid ad link
│
▼ (15 ms ping)
[Nearest Sply Edge Node]
├── 1. Reads incoming request URL (?utm=..., ?gclid=...)
├── 2. Asynchronously logs click event (0 ms added page latency)
└── 3. Streams cached assets or proxies upstream request
Non-blocking async logging
Edge nodes leverage the event.waitUntil() execution lifecycle:
- The edge gateway builds and dispatches the HTML response to the user's browser immediately.
- In a background asynchronous thread, the gateway extracts headers, evaluates the IP address against known datacenter lists, and commits the visit record to the analytics database.
2. Response time comparison
TIME FROM AD TAP TO VERIFIED CLICK LOG:
Edge Click Tracking (Sply) [██] 30–50 ms
Server-Side sGTM (Cloud Run) [██████████████] 1,200–1,800 ms (depends on client tag)
Client-Side Browser JS [████████████████████████] 2,200–3,500 ms
Why standard sGTM misses early bounces
Google’s server-side container acts as a receiver for payloads sent by client-side gtm.js. If a mobile user closes their browser before gtm.js downloads, sGTM records nothing.
Sply captures the click before the browser parses the initial HTML.
3. Network-level bot and fraud filtering
Click fraud and automated scrapers account for 15–30% of paid ad traffic across major search and display networks.
Most automated bots make a rapid HTTP GET request but do not execute client-side JavaScript.
How edge filtering cleans your data:
- ASN and subnet inspection: the gateway identifies whether requests originate from residential mobile carriers or cloud hosting providers (AWS, Hetzner, DigitalOcean).
- Behavioral verification: comparing edge entry timestamps against downstream telemetry helps identify zero-second bot hits.
- Clean reporting: ad bidding algorithms receive accurate training data, avoiding wasted budget on bot traffic.
Next steps
- Technical benchmark: Latency Benchmarks of Browser Tags, sGTM, and Sply Edge Logging.
- Next in series: Architectural differences: Sply vs. sGTM, Stape, and legacy ad trackers.
Внедрите Server-Side Tracking без сложного кода
Sply восстанавливает до 30% потерянных конверсий, защищает от Safari ITP/AdBlock и ускоряет загрузку ваших лендингов.