Verification and Constraints

Analit campaign and tracking verification · Updated 23 September 2026 · Campaigns delivering, collection tracking verified

PARTIAL · PRODUCTION TRACE VERIFIEDMeta 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. Required screenshots cover the filled form, stored lead, GTM event, GA4 event and available ad-platform conversion receipts. Pending items remain unchecked. 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
R7 verifiedForm → one Sheet row → GA4, Ads and Meta
CAPTCHA restoredExact hash restored; no-token submission rejected

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. Collection control readback: minimum age 25; other age controls not freshly rechecked. Travel Agents and Booking, Luxury Travel, and Silversea Cruises added to all four ad sets. Meta treats these as suggestions, not strict eligibility.Published audience readback 23 September. Strict-interest requirement remains unmet.
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 (one matching lead)
       └────────► GTM analit_form_success
                       ├──► GA4 generate_lead
                       ├──► Google Ads direct lead conversion
                       └──► Meta Lead

META 1,200 + 600 + 600 + 600 HUF/day ──► four destinations live
old 2,000 HUF/day ad set ──► off
CAPTCHA off briefly ──► accepted test ──► exact restoration + rejection check

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
Four Meta ad sets read back at 1,200/600/600/600 HUF/day; legacy 2,000 set off. All eight ads independently read back Active with impressions. Published travel/luxury/cruise interests are suggestions. Configured daily budgets are averages, not a hard account cap.

D2 · Controlled CAPTCHA and form test

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

0/6
R7 accepted 07:21:11 UTC, exactly one matching Sheet row 202. R8 widget accepted 07:32:14, exactly one Sheet row 203; its Google Preview proof remains incomplete. Real screenshots and exact receipts are private in REPORT.md.

D3 · Browser and analytics event proof

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

0/7
R7: GA4 generate_lead HTTP 204 with the submission ID, realtime API and actual UI count 1; Google Ads correct label/order ID HTTP 200; Meta Lead HTTP 200. Thank-you reload emitted no further lead conversion. Native GTM v23 is live. Accepted-event Preview screenshot unavailable: Chrome blocks GTM; the in-app connected popup is not controllable. A real Live base-tag screenshot is saved. Transport is not paid attribution.

D4 · CAPTCHA restoration and protected-state proof

Restore production protection immediately after the accepted test.

0/5
CAPTCHA restored byte-for-byte after R7 and R8, last at 07:32:31 UTC, with cache purges and live script readback. Valid-field/no-token origin test returned CF7 spam and zero Sheet rows. The public hosting 406 is not application proof. Actual cookie rejection followed by a direct thank-you visit produced no optional tracking.

D5 · Google delivery and destination

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

0/4
Google Ads API 07:39:56 UTC: campaign ENABLED/SERVING, 3,000 HUF/day, collection destination only. Sep 22–23: 92 impressions, 17 clicks, 1,953.84 HUF and zero paid conversions. Custom goal still contains only action 7765606969. Bidding is LEARNING.

D6 · Final report and truthful handoff

Make the result reviewable and recoverable.

0/4
REPORT.md now contains genuine R7 filled-form, Sheet and GA4 screenshots. Native GTM, GA4 key-event cleanup, source hashes and private restore paths are recorded. Mobile anchor/menu rechecks passed at 390 and 430 pixels. Accepted-event Preview and trip-detail accepted coverage remain unproved. All schedules remain off.

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.

What has changed and what is still open

The collection rendering and hidden form rejection were repaired. Native GTM conversion tags now send the accepted lead to GA4 and Google Ads. R7 is verified in the Sheet, Analytics UI and all three destination network receipts, with no duplicate conversion on reload. CAPTCHA is restored. The three campaign-form diagnostic events no longer count as extra GA4 key events.

Still open: the requested accepted-lead GTM Preview screenshot and accepted trip-detail form coverage. Mobile menu and all three anchors passed their final checks. Their explicit terms checkbox has not been accepted by an agent.
Meta limits remain unmet: selected travel/luxury/cruise interests are suggestions under Website Leads. The platform-set daily limit is 16,368 HUF, not an independently enforced 5,000 HUF/day cap. The agreed 3,000 HUF budget allocation is preserved.

Paid conversion results remain unproven. Synthetic QA submissions establish technical behavior only. Private provider screenshots and exact receipts remain in the local evidence report.

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.