CAPTCHA AND LEAD ACCEPTANCE REVIEW
Use internal record references; keep tokens, secrets and contact details private.
This worksheet does not test a live provider or change account settings.

Form / owner / environment / review date:
Business outcome counted by the campaign:
Browser widget and actual server acceptance endpoint:
Provider / widget configuration / server-side verification owner:
Expected hostname inventory and configured action:
Verified production/test key separation (do not paste keys here):

CONTROLLED ACCEPTANCE CHECKS
Missing token creates no lead, receipt or conversion job:
Client-only success flag creates no accepted record:
Provider rejection creates no accepted record:
Verification timeout or malformed result follows a deliberate recovery path:
Wrong hostname/action is rejected where those checks are configured:
Provider-reported expiry/duplicate is handled without a false success:
Invalid form payload is rejected independently of challenge success:
Valid submission reaches the business once with a stable internal reference:
Lost response and retry use a server-bound, idempotent acceptance strategy:
Legitimate customer can recover and complete the intended task:

OUTCOME AND MEASUREMENT
Received record / business receipt / reachability / qualification are distinct:
Campaign, network, period and timezone of the selected cohort:
Selected action, campaign goal and duplicate delivery paths:
Qualified business outcome and supported feedback result:
Remaining unknowns / next check / owner / review date:
Proposed change / acceptance criterion / rollback: