TRACKING AND PROTECTION EVALUATION
Use this to compare a proposed workflow. Not an upload or automatic change.

DEFINE THE JOB
Business outcome: accepted enquiry / qualified lead / paid order / other:
Observed problem and baseline period:
Account, campaign, site and destination scope:
Control required: billing review / collection / delivery / website enforcement /
  future ad exclusion / CRM qualification:
Current native controls and existing delivery owner:

TRACE THE RECORDS
Original request or business-event reference (opaque; no customer fields here):
Actual consent state, event time, time zone and source:
Detection decision and reason; uncertainty and false-positive review:
Website action actually enforced and how it was verified:
Event owner, exact destination/action, stable transaction identity:
Delivery decision, attempted request, response and later diagnostics:
Google Ads exclusion target/scope and actual criterion/read-back status:
Billing charges/adjustments and business outcome checked separately:

CONTROLLED ACCEPTANCE TESTS
1. Known legitimate outcome reaches the intended destination once in the
   supported setup; repeated local sends and final reporting stay separate.
2. Deliberately withheld test event has a visible reason and no intended
   outgoing request through that route; inspect overlapping direct tags too.
3. Website enforcement test records the actual page/form response; a withheld
   event alone does not prove the visitor was blocked from the website.
4. Supported ad-exclusion test has the correct account/campaign target and
   confirmed application status; a generated list alone is insufficient.
5. Missing/unavailable risk signal follows the documented fallback without
   silently treating unknown as proven human or bot.
6. Shared-IP/legitimate-customer case and rollback are reviewed in an
   appropriate test environment before broad enforcement.
For every case: environment / expected result / observed evidence / owner /
  unresolved facts / change date / rollback. Do not change a live ad account
  merely to fill this worksheet.

COMPARE FULL COST AND OPERATIONS
Published plan and source date; billing unit and usage cap:
Sites/domains/accounts and included destinations:
Hosting/infrastructure, setup, maintenance and support:
Review time, data retention/export access and cancellation/renewal terms:
Effect of false positives and legitimate-customer friction:
Supported integration gaps; manual work still required:
Do not call flagged visits multiplied by average CPC realized savings.

DECIDE
Smallest control set that solves the verified problem:
Existing capability sufficient / implementation repair needed / new provider:
One accountable delivery owner for each business outcome:
Evidence supporting the choice; unresolved assumptions:
Post-change review period, business outcomes, verified costs and rollback: