Verification and Constraints

Analit live campaign correction and conversion proof · 22 September 2026 · autonomous Astra Low retry 2

RETRY 2 READY · PRIOR RUNS PARTIALMeta 1426693405990263Google 1938291268Evidence is required before green checks

End goal

Preserve the verified Meta and Google state, then obtain one real synthetic accepted lead trace through storage, GTM Preview, GA4 DebugView, Google Ads and Meta. The only permitted test exception is temporary removal of the exact Turnstile mu-plugin with cache invalidation, followed by immediate byte-exact restoration and a protected rejection check.

End state

Every live mutation has a before/after provider readback or code hash. Screenshots show the filled form, stored lead, GTM event, GA4 event and available ad-platform conversion receipts. The board and REPORT.md distinguish verified, pending, blocked and untested claims.

3,000 Ft/dayMeta four-destination total
0 Ft/dayOld 2,000 Ft/day ad set after pause
1 accepted leadRequired end-to-end proof
CAPTCHA restoredRequired after controlled test

Confirmed inputs and boundaries

Confirmed or verifiedExecutor evidenceFailure or residual blocker
SurfaceRequired settingProof route
MetaCollection 1,200; autumn 600; New Year 600; spring 600 HUF/day. Pause the old 2,000 HUF/day ad set.Ads Manager object readback and delivery screenshot
Google SearchCampaign 24253795852 enabled, collection page only, 3,000 HUF/day.Google Ads API/UI readback and eligibility screenshot
AudienceHungary, inherited 45–65, all genders, approved organized travel/luxury travel/luxury cruises restriction where provider supports it.Audience editor screenshot and saved object readback
TrackingAccepted website lead is the conversion. Preserve latest copy and ten client images.Form, CRM/Sheet, GTM Preview, GA4 DebugView, Ads/Meta event evidence
Controlled CAPTCHA exception: disable only for the shortest test window, back up the exact live file, record hashes and cache actions, then restore immediately. Never leave the site without CAPTCHA.
Account cap: do not claim Meta has an independent 5,000 HUF daily ceiling unless the provider readback proves it. The old 2,000 HUF/day object must be paused so configured campaign budgets remain 3,000 HUF/day.

End goal system

FORM ACCEPTED → CRM / SHEET → GTM analit_form_success → GA4 generate_lead → Google Ads + Meta Lead → REPORT + screenshots

META 1,200 + 600 + 600 + 600 HUF/day ──► four destinations live
old 2,000 HUF/day ad set ──► paused and read back
CAPTCHA off (test only) ──► accepted proof ──► CAPTCHA restored ──► rejection proof

Route to the end state

1. Snapshot identities and current states
   ↓
2. Pause old Meta 2,000 Ft/day object and verify delivery
   ↓
3. Back up code, temporarily disable CAPTCHA, submit labelled test
   ↓
4. Capture CRM/Sheet, GTM Preview and GA4 DebugView screenshots
   ↓
5. Reconcile Google Ads and Meta events, IDs and timestamps
   ↓
6. Restore CAPTCHA, purge narrowly, prove rejection and republish board
   ↓
7. Return REPORT.md with evidence and exact residual blockers

Operational handoff

Inputs
Live forms, accounts, code hashes
→
Controlled test
Generate one labelled accepted lead
→
System evidence
CRM/Sheet, GTM and GA4 screenshots
→
Ad evidence
Google Ads and Meta readbacks
→
Handoff
REPORT.md and rollback record

Each node exists to prove the next system boundary. The executor owns the handoff and keeps private screenshots local.

Deliverables and observable criteria

D1 · Meta budget correction and delivery

Pause the old 2,000 Ft/day ad set and prove the four intended allocations remain live.

0/5
Evidence slot: evidence/meta-budget-correction-readback.json and evidence/screenshots/meta-budget-after.png

D2 · Controlled CAPTCHA and form test

Use a reversible, time-bounded exception to obtain one genuine accepted lead trace.

0/6
Evidence slots: evidence/captcha-before.json, evidence/form-filled.png, evidence/crm-or-sheet-row.png, evidence/form-submit-response.json

D3 · Browser and analytics event proof

Show the accepted lead crossing each tracking boundary with the same event ID or traceable timestamp.

0/7
Evidence slots: evidence/screenshots/gtm-preview-event.png, ga4-debugview-event.png, google-ads-conversion.png, meta-lead-event.png, event-reconciliation.json

D4 · CAPTCHA restoration and protected-state proof

Restore production protection immediately after the accepted test.

0/5
Evidence slots: evidence/captcha-after.json, evidence/screenshots/captcha-restored.png, evidence/protected-rejection.json

D5 · Google delivery and destination

Confirm Search still sends only to the collection page and can spend.

0/4
Evidence slot: evidence/google-delivery-after.json and evidence/screenshots/google-delivery.png

D6 · Final report and truthful handoff

Make the result reviewable and recoverable.

0/4
Evidence slots: REPORT.md, deliverables.md, main-prompts.md, session-id.txt, board URL

Route-specific evidence gate

The accepted chain must use the same labelled QA identifier across all systems. Check every image by opening it and reject screenshots showing an unrelated site, stale tab, blank state, or unreadable crop. Required routes are: collection hero/contact form, floating widget, autumn detail, New Year detail and spring detail. Organic QA proves transport only; paid attribution is claimed only when the ad-platform receipt matches.

Cache/edge gate: after deleting the mu-plugin, the correct production collection URL must be HTTP 200 with no Turnstile markers before any accepted submit. A Cloudflare 403 or unchanged 17-marker source means the deletion did not reach the served page and the test is blocked.

Open facts and stop conditions

The executor may choose implementation details. It must stop only the affected criterion if an exact permission or provider capability cannot be recovered.

Read-set and provenance

Canonical project: /Users/agency/Documents/Agty/Analit. Prior launch report: analit-campaign-lll-20260921/REPORT.md. Access map: ACCESS_GOOGLE_META.md. Parent task: 01a0c2c4-4fa2-7531-8c2d-5b10ca9b06cb.