Analit live campaign correction and conversion proof · 22 September 2026 · autonomous Sol Medium run
Leave the four intended Meta destinations delivering at their approved 3,000 HUF/day total, pause the old 2,000 HUF/day ad set, and prove one accepted enquiry from form submission through CRM or Sheet, GTM, GA4, Google Ads and Meta. Temporarily remove CAPTCHA only for the controlled test, then restore it and prove the protected rejection path.
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.
| Surface | Required setting | Proof route |
|---|---|---|
| Meta | Collection 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 Search | Campaign 24253795852 enabled, collection page only, 3,000 HUF/day. | Google Ads API/UI readback and eligibility screenshot |
| Audience | Hungary, inherited 45–65, all genders, approved organized travel/luxury travel/luxury cruises restriction where provider supports it. | Audience editor screenshot and saved object readback |
| Tracking | Accepted website lead is the conversion. Preserve latest copy and ten client images. | Form, CRM/Sheet, GTM Preview, GA4 DebugView, Ads/Meta event evidence |
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
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
Each node exists to prove the next system boundary. The executor owns the handoff and keeps private screenshots local.
Pause the old 2,000 Ft/day ad set and prove the four intended allocations remain live.
evidence/meta-budget-correction-readback.json and evidence/screenshots/meta-budget-after.pngUse a reversible, time-bounded exception to obtain one genuine accepted lead trace.
evidence/captcha-before.json, evidence/form-filled.png, evidence/crm-or-sheet-row.png, evidence/form-submit-response.jsonShow the accepted lead crossing each tracking boundary with the same event ID or traceable timestamp.
evidence/screenshots/gtm-preview-event.png, ga4-debugview-event.png, google-ads-conversion.png, meta-lead-event.png, event-reconciliation.jsonRestore production protection immediately after the accepted test.
evidence/captcha-after.json, evidence/screenshots/captcha-restored.png, evidence/protected-rejection.jsonConfirm Search still sends only to the collection page and can spend.
evidence/google-delivery-after.json and evidence/screenshots/google-delivery.pngMake the result reviewable and recoverable.
REPORT.md, deliverables.md, main-prompts.md, session-id.txt, board URLThe executor may choose implementation details. It must stop only the affected criterion if an exact permission or provider capability cannot be recovered.
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.