Access
Operator login
Dashboards expose the same metrics surfaced on Docs and Audit. Parallel-tracking PINGs never hit this route—they terminate on /click with 204.
Compliance snippet (reference)
When Google Ads fires a background parallel-tracking PING against your measurement URL, the request hits BluePoint Ads 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 shopper is sent to the Google Ads Final URL. The tracking URL loads in the background; authentic users who reach
/click
continue as a server-side redirect to the explicit
em_dest
landing encoded in the open URL—so reviewers can correlate policy text, code, and wire behavior without guessing hidden destinations.
// BluePoint Ads 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.