Clickerwave

Implementation guide

Multichannel edge templates

Clickerwave optimizes for distribution: partners, geos, and landing variants all resolve through one edge URL while each click still carries its own visible em_dest. Google Ads parallel-tracking probes stay on a 204 lane; shoppers get the transparent redirect reviewers expect.

Geo + partner 204 lane Live metrics

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.

Live instance metrics

Total requests

227

Valid redirect rate

100.00%

Last update

2026-06-04 22:45:39

Numbers refresh from the same database your Audit page reads—no static marketing counters.

Canonical template

Tracking URL

https://clickerwave.com/click?em_dest=https%3A%2F%2Fexample.org%2F

Decoded destination

https://example.org/

em_dest is the sole redirect instruction. Clickerwave never substitutes a secret landing—what you encode is what the browser receives after validation.

Interactive builder

Type any HTTPS landing to preview the exact tracking link for this host.

Generated tracking URL

Resolved final URL

Encoding preserves query strings and UTF-8 characters safely.

HTTP behavior

Production routing for this Laravel deployment.

Diagram of browser 302 redirect versus Google-Ads-Compliance 204 response on the same /click endpoint.
Use with the PHP snippet above when packaging reviewer evidence.

Request

GET /click?em_dest=https%3A%2F%2Fexample.org%2F

Browser response

302 Redirect → https://example.org/

Automated PING

204 No Content (empty body)

Malformed or missing destinations fall back to / after logging the reason.

Operational guardrails

  • Only absolute http:// or https:// URLs pass validation.
  • Avoid chained blind redirects after Clickerwave—reviewers will follow the full path.
  • Keep screenshots of this Docs page plus Audit evidence with every certification packet.

Reviewer readiness checklist

  • Confirm every live template exposes the final landing inside em_dest.
  • Demonstrate the 204 snippet above matches your deployed TrackingController.
  • Ensure Privacy, Terms, Cookie Policy, and Data Deletion routes stay public.
  • Provide sample click URLs plus the resolved destination pair for policy teams.