Input
Meeting + latest choices
Six services; Google only; 10 km local maintenance.
LLL Unhinged · execution board · 26 September 2026
Kertújítók Google Ads: finish and prove it
● PAYMENT HOLDFresh exact-account reads show six Search campaigns paused. Billing has an unresolved provider-declined charge. Cloudflare Worker c6b1 is live; independent desktop/mobile review is pending. A labeled protected form test returned 403 with no Turnstile token. This board records evidence, not launch approval.
Owner: Luna Max executor
End goal and finish line
End goal: All six agreed Search campaigns serve the right services and destinations within the whole-account 200,000 Ft monthly ceiling, with protected lead paths and conversion evidence that can be trusted.
Done means: Correct public pages and menus; all 16 controlled form cases and relevant tracking proved; safe billing and policy status; provider-confirmed activation and real 24h/48h impressions for six campaigns and both maintenance groups. If Péter’s payment or an action-time CAPTCHA step still prevents this, show the precise blocker and keep the incomplete tests red.
6Search campaigns
7service groups
200kFt monthly ceiling
26 Sep verified state
- Exact-account Ads API: six Search campaigns PAUSED, seven groups enabled, seven active ads APPROVED, zero September impressions, clicks and served cost.
- Billing UI still shows a provider-declined overdue payment and a warning that service may be suspended. Péter owns payment.
- Cloudflare Worker c6b1 is live at 100%, with the prior version recorded as rollback. Independent desktop/mobile screenshots are being reviewed.
- The latest labeled form POST returned 403 with an empty Turnstile token; its production D1 transaction lookup returned zero rows. Google form-data events were not native conversions.
- No accepted lead, native Ads conversion, campaign activation or postactivation delivery is claimed.
Confirmed service map
Meeting + later chat: priority talajfúrás, betontörés, térkövezés. Smaller budgets for gyepszőnyegezés and standalone öntözőrendszer. One maintenance Search campaign covers short local mowing/leaf work and larger garden maintenance for Péter’s son. Google only. Maintenance uses the documented Szigetszentmiklós town point with exactly one 10 km radius. No Ads traffic to the newer /helyi-kertfenntartas page. Use the existing Kertfenntartás collection.
Proposed prior allocation: 1,800 + 1,700 + 1,300 + 450 + 450 + 800 Ft/day = 6,500 Ft/day. This is an operator choice, not a meeting quote. Recompute the actual account-wide monthly bound before activation.
26 September provider checkpoint
Configured, paused: six Search campaigns, seven groups and seven approved active ads read back in the exact account. The maintenance campaign has one positive 10 km Szigetszentmiklós radius, and both maintenance ads target the existing collection. Other campaigns remain paused.
Budget: 6,500 Ft in combined daily budgets. September 1–26 cost is 0 Ft. At 2× daily budget for each remaining September day, the conditional account-wide bound is 65,000 Ft, below 200,000 Ft. This is not an installed hard cap; recheck before any enablement.
Owner gate: Google Payments still identifies an overdue declined payment. All six remain paused. No payment action was taken. Site and protected form proof remain open.
Open facts to resolve from live systems
- Has Péter resolved the declined Ads payment?
- Does the dirty mobile-menu patch fix deep-scroll behavior without breaking cookie settings or forms?
- Will the protected widget issue a response token in a normal browser, or visibly present a challenge that can be completed with the required action-time confirmation?
- After a token is available, can the remaining labeled cases be reconciled to D1, GTM/GA4 and native Ads evidence without counting QA as paid demand?
- After activation, do all six campaigns and both maintenance groups actually receive impressions?
End goal system
Input
Ads + Cloudflare state
Fresh provider account, live site and existing patch.
Deliverable
Correct journeys
Collection and irrigation pages, usable forms/menu.
Deliverable
Measured campaigns
Six eligible Search campaigns under cap.
Result
Serving proof
Real impressions and evidence-based handoff.
Route to the end state
1 · reconcile
Read live state
Account, billing, site release, active writers.
2 · repair
Finish site UI
Preserve patch and prove mobile/desktop.
3 · verify
Forms and tags
16 real protected test cases and attribution.
4 · gate
Budget + eligibility
Fresh ledger; payment and policy readback.
5 · launch
Enable + observe
Only passing campaigns; 24h/48h impressions.
Constraints and stop conditions
- Cloudflare-only. Do not use or restore GAJA/GHL. Do not add a security layer. Preserve existing protection and unrelated work.
- Péter handles payment/card. No agent payment retry, self-clicks, fabricated leads, protection bypass or client message.
- Do not enable campaigns while billing, policy, budget, destination or measurement gate fails. Block only the affected action and preserve an exact resume point.
- Every site change requires a live release receipt, practical rollback and postdeployment screenshots independently described by Luna High.
Observable criteria and evidence
2 / 8 passed · proof required for every green checkSite destination and menu
When the production site is opened at 390×844 and 1280×900 and each menu is expanded, then maintenance Ads point only to /kertfenntartas, the newer local mowing page is absent from menus, the collection hero has no oversized gap, and the full mobile submenu remains scrollable and above both page content and the sticky CTA, including after deep scrolling.
Acceptance and evidence
Evidence slot: Live postrelease screenshots for hero, top and deep-scroll menu; blind Luna High descriptions; version and rollback receipt. Pending executor evidence.
Existing journeys preserved
When /kertfenntartas and /automata-ontozorendszerek are opened on mobile and desktop, then their enquiry forms and CTA controls remain visible and hit-testable, cookie settings reopens its existing panel, and the irrigation enquiry area explicitly welcomes standalone installation.
Acceptance and evidence
Evidence slot: Live screenshots, button interaction results, forms/anchor inventory, blind Luna High descriptions. Pending executor evidence.
Campaign structure
When the designated Google Ads account is freshly queried, then six Search campaigns and seven service groups reflect drilling, concrete breaking, paving, small-budget turf, small-budget standalone irrigation, and two maintenance intents in one maintenance campaign; the five exact destination pages and current policy/ad status appear in a provider readback.
Acceptance and evidence
Evidence slot: Sanitized campaign/group/asset report with query time; no old snapshot presented as current. 26 Sep exact-account API read: six paused Search campaigns, seven enabled groups, seven active approved RSAs, final URLs read back. All five destination paths returned HTTP 200. Private resource IDs and raw provider packet are in the executor handoff.
Targeting and budget
When all six settings and current-month costs are read back before any enablement, then Google Search only, the agreed service geography, one 10 km Szigetszentmiklós radius for maintenance, 6,500 Ft/day proposed allocation or a lower safe allocation, and a whole-account calendar-month exposure ≤200,000 Ft are shown in a dated ledger.
Acceptance and evidence
Evidence slot: Settings export plus monthly cost/exposure formula including prior cost and budget-change days. 26 Sep API read: one positive 10 km Szigetszentmiklós proximity for maintenance, with other service areas retained; 6,500 Ft/day, zero earlier September served cost and no other enabled campaigns. Conservative 26–30 Sep bound: 65,000 Ft. Recheck before launch.
Lead journey and measurement
When 16 labeled test cases across the 15 form paths and maintenance short/large selections are submitted through the actual protected site, then each accepted lead has its exact service/form/transaction ID in the application and D1, GTM/GA4 session evidence, and native Ads request evidence where applicable, without counting QA as genuine paid demand.
Acceptance and evidence
Evidence slot: Per-case matrix with input, accepted/rejected result, D1, browser network, GTM/GA4 and Ads evidence; unresolved cases unchecked. Two labeled attempts have not produced an accepted lead. The latest real POST returned 403 `verification_failed` with `cf-turnstile-response` length 0; the exact production D1 transaction read returned zero rows. Two isolated contexts showed no token, and the configured widget hostnames are valid. No visible challenge appeared, no CAPTCHA was solved or bypassed, and no native Ads conversion occurred. Remaining cases stay unverified.
Billing and eligibility gate
When Billing, policy and campaign diagnostics are freshly read, then any remaining declined payment, disapproval or account limitation is identified with exact owner and action. If payment remains outstanding, campaigns remain paused.
Acceptance and evidence
Evidence slot: Dated sanitized provider readback; Péter handles his own payment and card. 26 Sep authenticated Billing Summary and Google Payments dialog show a service-threshold warning and a provider-declined overdue payment. Péter owns payment. Ads API shows all six paused; seven active ads approved. Billing must be rechecked after Péter resolves it.
Conditional launch and serving
When C1–C6 pass and safe billing is confirmed, then only eligible campaigns are enabled, actual provider statuses are read back, and genuine non-self-generated impressions >0 appear for each of six campaigns and both maintenance groups at the 24h/48h checkpoints.
Acceptance and evidence
Evidence slot: Before/after campaign IDs/status, 24h and 48h provider metrics; zero means diagnose, not pass. Billing and protected measurement gates are unresolved. All six campaigns remain PAUSED, with zero September impressions, clicks and served cost. No 24h/48h postactivation window has begun. No self-clicks or forced spend.
Release and handoff
When the final version is released, then the canonical Cloudflare source contains the UI patch, live Worker version/rollback is recorded, this same board shows only evidenced passes, and a concise handoff distinguishes configured, tested, serving and blocked states.
Acceptance and evidence
Evidence slot: Commit, provider release, live URL, screenshot set, dated board and report. Cloudflare canonical merge `f3e6f722`; change record `a020b2b3`; Worker `c6b192e5` at 100%, rollback `f1fd07ea`. Same board URL and comment document preserved. Independent visual reports are pending before final handoff.
Sources and current surfaces
- Earlier Google Ads contract and execution receipt
- Maintenance collection · Irrigation destination
- Internal handoff contains the exact prior report, contract JSON, UI worktree, screenshot QA and rollback receipt.
Executor update rule: Add dated blue progress notes and proof links here; check a criterion only after the stated output is independently verified. Republish this same URL after meaningful changes.