Audit evidence

Recent measurement decisions

Each row mirrors a request handled by /click. Use it to prove how production traffic behaved during your review window.

Total

Valid rate

100.00%

Last update

2026-08-28 03:19:38

Reviewer notes

Valid rows mean em_dest was present and passed HTTPS hostname validation (no IP, no deeplinks).
Invalid rows include missing destinations, blocked schemes, IP hosts, or malformed URLs.
Automated Google PINGs never appear here—they exit with 204 before logging.

Volume · last 7 days

Daily click events from click_events · last refresh 2026-08-28 03:19:38

Sat

Sun

Mon

Tue

Wed

Thu

Fri

Google Ads parallel tracking: backend PING → 204

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.

Browser — redirected to HTTPS em_dest and listed in this table.

Google-Ads-Compliance — 204 No Content; omitted from this table.

Last 50 click events

Time	Status	Reason	IP	Target URL
2026-08-28 03:19:38	valid	redirected	104.23.166.97	https://example.org/