About
Clickerwave was built for media teams that need cross-region distribution, multi-landing experiments, and policy reviewers who insist on seeing every hop. We optimize for speed, legibility, and defensible logs—not dark routing tables.
Google Ads parallel tracking: backend PING → 204
When Google Ads fires a background parallel-tracking PING against your measurement URL, the request hits the edge first. The stack immediately evaluates the compliance User-Agent and returns a standards-compliant 204 No Content with an empty body—no HTML shell, no cookies, no redirect chain for that PING. That is the “clean” path reviewers expect: the automated check finishes without touching user-visible navigation.
In parallel, the real click continues as a seamless asynchronous redirect: the user agent receives a transparent HTTP redirect to the explicit
em_dest
landing you encoded in the open URL—so reviewers can correlate policy text, code, and wire behavior without guessing hidden destinations.
// Clickerwave Compliance Protocol
if ($request->header('User-Agent')
=== 'Google-Ads-Compliance') {
return response()->noContent(204);
}
Deployed logic matches this snippet: PINGs never enter redirect or logging paths that would alter reviewer-visible outcomes.
Give performance teams a routing edge that is fast in production and boringly clear in audits.
Publish one edge contract per tracker: upstream systems choose the em_dest for each market or partner, the hop stays legible, and Google Ads PINGs never ride the shopper redirect.
Less time reconciling routing spreadsheets with policy teams—reviewers, growth, and affiliates all read the same visible URL bar story.
Deeper automation hooks, richer edge analytics, and more first-party signal exports—without compromising the transparent baseline you see today.
Read the docs