GOOGLE ADS CLICKS / MISSING WEBSITE REQUESTS

1. REPORT SCOPE
Customer/campaign IDs, channel, network/device filters:
Metric name and reporting surface:
Click-type rows and their documented meanings:
Date range, account timezone, export time and processing indicators:
The click-type SELECT query is read-only. It is not an individual-click ledger.

2. DESTINATION AND CONTROLLED TEST
Configured final URL, expanded template/suffix and any alternate destination:
Device/browser, test timestamp with offset, expected hostname and path:
Open the destination directly; do not repeatedly click a live ad.
Keep synthetic test parameters and test leads separate from campaign reporting.
Initial URL, redirects, final URL and browser-visible network result:
DNS/TLS/loading error, challenge, cached response or successful page delivery:

3. OBSERVATION COVERAGE
Browser: network trace, cache/service-worker status and final response:
Edge: correct zone/hostname, dataset, filters, retention and sampling:
Origin: actual server/container/vhost, method/path, logging policy and rotation:
Record each observation layer; do not add matching edge/origin rows as visits.
Security event views are not automatically complete access logs.
No matching row means not observed in that selection, not proved absent.

4. RESPONSE EVIDENCE
Available request ID, status, content type and eventual destination:
CF-Cache-Status if present (HIT/MISS/etc.), interpreted for this response:
cf-mitigated: challenge if present, followed by the actual challenge outcome:
Do not infer user identity, ad billing or fraud from a response header alone.

5. DOWNSTREAM RESULTS
Analytics collection, consent state and campaign attribution:
Application acceptance, received/qualified/paid outcome and stable record ID:
If requests exist but analytics is missing, investigate that later checkpoint.
If origin rows exist, validate client-IP/proxy fields before exclusion review.

6. DECISION AND FOLLOW-UP
Supported finding, alternative explanations and collection gaps:
Next controlled test, owner, review date and success criterion:
Actual native filtering/billing evidence retained separately:
Do not label clicks minus requests as a bot percentage or guaranteed refund.
No IP exclusion can be justified from a click total with no client observation.

https://adprotektor.app/blog/google-ads-clicks-no-server-requests/