Capture the Click Before the Browser Loses It

The problem

A user clicks your Meta ad. The URL contains fbclid=abc123 — the only string connecting that click to a future conversion. By the time your pixel fires, the browser has already started destroying it. Safari strips the parameter via ITP. Cookies expire in 7 days. Consent banners delay script execution. Ad blockers prevent the pixel from loading entirely. 20-40% of click identities are lost before your tracking code runs a single line.

Why this works

• Timing is everything. The raw HTTP request still contains fbclid, gclid, and ttclid before the browser processes the page. An edge worker intercepts this request at the CDN layer — before HTML renders, before JavaScript loads, before any consent banner appears.
• Server-set cookies survive ITP. Cookies set via Set-Cookie HTTP header from your own domain bypass Safari’s 7-day limit on JavaScript-set cookies. The identity persists for 90+ days, not 7.
• First-click filtering fixes prospecting learning. PPC strategist John Moran’s thesis: when the algorithm learns from retargeting clicks, it gets good at finding people already in your funnel. Filtering to first clicks only forces it to learn from genuine cold-audience conversions.

Results

Smars: “The transparency around channel and event level success rates is a huge plus. After deploying edge-level click capture, our Event Match Quality jumped from 3.2 to 8.7.” — Sahil Kanojiya, Head of Mediabuying

John Moran’s first-click thesis: Sending only first clicks to the algorithm is the single most impactful change you can make to new customer acquisition. When the algorithm receives retargeting conversions, it learns to find people already in your funnel. Filter to first clicks and it learns what a real new customer looks like.

How to set up your campaigns

On Meta

1. Campaign type: Any campaign using CAPI (Advantage+, manual prospecting, retargeting).
2. Conversion event: Use CAPI-only events from CustomerLabs. The edge-captured click ID is included in every server event, giving Meta deterministic matches instead of probabilistic modeling.
3. Settings: Check Event Match Quality in Events Manager. Target EMQ of 8+. Edge capture typically gets you there in the first week.

On Google

1. Campaign type: Performance Max, Search, or Shopping with enhanced conversions enabled.
2. Bidding strategy: Any value-based or conversion-based bidding. Better attribution data improves all strategies.
3. Conversion action: Use server-side conversion tags with the preserved gclid from edge capture. Enable enhanced conversions for redundancy.

Setup with CustomerLabs

• Week 1: Edge worker deploys on your CDN (Cloudflare Workers, CloudFront Functions, or equivalent). No code changes to your website. Click capture starts immediately.
• Week 2: Identity matching goes live. Every visitor with a click ID has their identity preserved server-side and matched to CRM records and order history.
• Week 3: First-click filtering activates. Prospecting campaigns receive only first-touch attribution data. Retargeting events route to retention campaigns.

The bottom line

Your click identity starts dying the moment the browser takes over. Edge capture grabs it at the infrastructure level — before ITP, before consent banners, before ad blockers — and stores it where the browser cannot touch it. Combined with first-click filtering, you give the algorithm the cleanest acquisition signal possible.