Verification and Constraints

Analit campaign launch · 21 September 2026

PARTIAL · CONTROLS BLOCK META LAUNCHEvidence updated 2026-09-22 01:13 Europe/Budapest

End goal

Activate the agreed Analit Meta and Google Search campaigns with correct enquiry tracking, enforceable spending controls, the approved creative library, and a weekly Monday email check.

End state

Meta account 1426693405990263 runs four destination allocations totalling 3,000 HUF/day: collection 1,200, autumn 600, New Year 600, spring 600. A separate account-wide ceiling prevents more than 5,000 HUF of Meta ad delivery spend per account-local day, irrespective of campaigns. The initial audience is restricted to the approved travel-interest categories. Google Search retains the prior-plan 3,000 HUF/day budget and routes paid traffic only to the collection page. Successful website enquiries are measured correctly. Every Monday at 17:00 Europe/Budapest, a scheduled Codex check emails Matt a verified report.

This target is not a claim that Meta exposes every requested control. Provider capability checks below must distinguish a supported implementation from an impossible combination. A blocked criterion remains blocked, and independent work continues.

3,000 Ft/dayMeta configured budget

5,000 Ft/dayRequired independent Meta ceiling

3,000 Ft/dayGoogle Search budget

Monday · 17:00Budapest time · email to Matt

One collection Meta ad set and ad are saved as an unpublished draft with both switches off; strict interest eligibility, Instagram access and the independent 5,000 Ft account-wide daily cap are unresolved, so no new Meta delivery was launched. Google Search remains paused until accepted conversion and duplicate-campaign cutover are verified. The live thank-you gate and GTM version 22 prevent the observed rejected-form false lead. Monday reporting is active and the initial report was emailed to Matt.

Settled settings

Confirmed requirement / verified factImplementation recommendationTechnical proof outstanding

Meta destination	Daily budget	Landing page
Collection	1,200 Ft	https://balionline.hu/csoportos-utak-gyujtooldal/
Autumn	600 Ft	https://balionline.hu/utazas/oszi-szunet-bali-gili/
New Year	600 Ft	https://balionline.hu/utazas/balinez-ujev-2027/
Spring	600 Ft	https://balionline.hu/utazas/tavaszi-nyaralas-bali/

Google Search: only the collection page. Conversion: accepted website enquiry, not field focus or form starts.

Creative: only the ten client images, best supported variants from the final review library, exact user corrections retained.

Initial audience: Hungary, all genders, inherited age 45–65, restricted to the three named travel-interest categories. Later targeting tests remain queued.

Implementation recommendation: one reusable Meta Leads campaign with four independently budgeted ad sets and two complementary ads per set. Interests use OR among the three allowed categories. This does not require one person to match all three.

Technical checks that must remain honest

Strict interests: a new off Leads draft exposed audience controls after Further limit reach, but the detailed-interest picker did not load and Advantage+ still appeared on. Strict eligibility is unproved.

5,000 Ft daily ceiling: the live billing UI shows a Meta-set 20,850 Ft daily limit. The editable account spending limit is cumulative. Neither enforces the required 5,000 Ft account-wide daily ceiling.

Monday schedule restored: a fresh check found the existing heartbeat paused. The app update restored it to active and saved-record readback confirmed the schedule and target. The initial email was sent once through agency Gmail with a Sent-folder receipt. Future delivery still depends on the local host running.

No new business questionnaire is needed. The executor investigates these capabilities and asks only if a genuine platform incompatibility or human-only authentication step remains.

End goal system

flowchart TD
 M["<b>Meta · 3,000 Ft/day</b><br/>Four fixed destination budgets"]:::confirmed
 C["<b>Account ceiling · 5,000 Ft/day</b><br/>Independent protection must be proved"]:::open
 T["<b>Strict travel interests</b><br/>Restricted to the three approved categories"]:::confirmed
 G["<b>Google Search · 3,000 Ft/day</b><br/>Collection destination only"]:::confirmed
 P["<b>Collection landing page</b><br/>Production offer facts are authoritative"]:::confirmed
 S["<b>Three named landing pages</b><br/>Autumn, New Year and spring"]:::confirmed
 L["<b>Accepted website enquiry</b><br/>Receipt and conversion proof required"]:::open
 R["<b>Monday · 17:00 Budapest</b><br/>Scheduled check and email to Matt"]:::confirmed
 C --> M
 T --> M
 M --> P
 M --> S
 G --> P
 P --> L
 S --> L
 M --> R
 G --> R
 L --> R
 classDef confirmed fill:#E8F5E9,stroke:#2E7D32,color:#173B25
 classDef assumption fill:#FCE4EC,stroke:#C2185B,color:#5B1430
 classDef open fill:#FFFFFF,stroke:#94A3B8,color:#475569,stroke-dasharray:5 5

Route to the end state

flowchart TD
 A["<b>Settled user decisions</b><br/>Scope, budgets, copy and activation"]:::confirmed
 B["<b>Existing partial setup</b><br/>One Meta ad set at 2,000 Ft/day"]:::confirmed
 V["<b>Executor authorized</b><br/>Copy edits imported and brief checked"]:::confirmed
 P["<b>Build and prove</b><br/>Content, forms, controls and email"]:::open
 Q{"<b>Applicable checks pass?</b><br/>Prove each platform independently"}:::open
 F["<b>Repair or isolate blocker</b><br/>Preserve strict requirements"]:::open
 E["<b>Activate and observe</b><br/>Read back delivery and publish evidence"]:::open
 A --> V
 B --> V
 V --> P --> Q
 Q -->|No| F --> P
 Q -->|Yes| E
 classDef confirmed fill:#E8F5E9,stroke:#2E7D32,color:#173B25
 classDef assumption fill:#FCE4EC,stroke:#C2185B,color:#5B1430
 classDef open fill:#FFFFFF,stroke:#94A3B8,color:#475569,stroke-dasharray:5 5

Verification checklist

Execution criteria begin unchecked. The executor adds evidence and updates this same board after meaningful progress. Black is the contract, blue is execution evidence, green is verified, red is failed or blocked.

Establish a baseline to prevent duplication

Record existing objects and recovery before changing live delivery.

1/4 passed · partial

Account routing/Users/agency/Documents/Agty/Analit/ACCESS_GOOGLE_META.md

before-state ledgerrollback recordsource-to-final settings ledger

Verification, constraints and evidence

Verification criteria

fresh provider reads identify Meta 1426693405990263, Google customer 1938291268 via manager 9494412337, actual currency/timezone, Page/Instagram, dataset, all active campaign/ad-set/ad IDs and budgets.
The final ledger accounts for every running object.
Retired Meta 211293306810753 receives no writes.
Existing object reuse/replacement and safe cutover are explicit.

Constraints

preserve unrelated client assets and work
never use routing documents as live-state proof
no duplicate active spend or permanent deletion.

Authenticated Meta All ads view on 22 September showed one active campaign 120254408012460450, one active ad set 120254408012470450 at 2,000 Ft/day, one active ad 120254408012450450, plus off unpublished collection draft ad set/ad 120254615430960450/120254615430950450. Fresh Google Ads API account readback identified customer 1938291268 via manager 9494412337, HUF/Europe/Budapest, 11 non-removed campaigns and only older Bali Search 23492984549 enabled at 1,500 Ft/day. The source-to-intended-state and safe cutover/rollback are explicit in campaign-object-ledger-20260922.json; Google rows in google-account-campaigns-20260922.json. Existing delivery unchanged. Meta account timezone and Instagram access, and final activated object ledger, remain open.

Build four allocations to preserve budgets

Preserve each destination budget, exact approved copy and image pairing.

0/5 passed · one unpublished draft

Four production pageshttps://balionline.hu/Final copy libraryhttps://review.clientsflow.hu/analit-bali-landing-oldalak-2026-08-28-v1/Ten approved images/Users/agency/Documents/Agty/Analit/outputs/analit-ads-ready-20260915/meta/drive-creatives-20260915

four correctly routed Meta allocationsexact ad/creative manifestplacement previews

Verification, constraints and evidence

Verification criteria

provider readback shows 1,200/600/600/600, total 3,000 HUF configured per day, no redistribution violating those amounts, correct objective/event and URLs/UTMs.
Every launched ad has exact primary text/headline/description/CTA, approved image number/hash, provider ID and live preview evidence.
Compare copies to selected library and live facts.
Record automatic text/artwork enhancements as disabled where they would change approved content.
Validate EU advertiser/payer details using the verified organization.

Constraints

only the ten supplied images
retain exact user corrections
no new Sumba allocation
no claims of a proven winning copy without comparative evidence.

Eight reviewed copy variants and ten permitted image hashes remain in run inputs. Meta ad set 120254615430960450 and ad 120254615430950450 stage the collection at 1,200 Ft/day with both switches off and unpublished. Website destination is the collection URL, COL-A copy and an existing visually matching 1.jpg_105 account image are selected, browser add-on none, optional/essential enhancements off, interactive reveal off. Exact media hash and placement crops are unverified; Instagram access error #1815199 persists. Other three allocations are unbuilt. See meta-draft-readback-20260922.json.

Required screenshot evidence slot: destination-matched ad and placement previews

Enforce targeting to preserve audience intent

Prove interests restrict eligibility before using website-lead optimization.

0/5 passed · blocked

Strict travel-interest requirementLive Meta audience controls

initial strict audience configurationfuture-test queue

Verification, constraints and evidence

Verification criteria

actual account UI/API readback demonstrates the three approved interest categories, explicit OR construction and disabled outside-interest expansion for the chosen website-lead optimization.
Save provider controls and a screenshot, not just an audience name.
Verify inherited geography/age/gender and distinguish any suggestions.
If no compatible website-lead setup supports strict interests, record the exact provider restriction and available alternative without silently adopting it.
Finish other independent configuration and report only the consequential choice needed.

Constraints

no broad fallback
no automatic retargeting/lookalike launch
no objective change to traffic/clicks to obtain interest controls
no made-up interest IDs.

In the new off draft, Further limit reach switched to audience controls. Hungary and minimum age 25 are shown. The detailed-targeting panel stayed loading and no approved interests were selected or proved. Advantage+ on still appears. Strict OR category eligibility and disabled expansion remain unproved. See meta-draft-readback-20260922.json and meta-capability-readback.json.

Required screenshot evidence slot: actual audience controls and expansion behavior

Enforce a ceiling to contain spend

Prove account-wide daily protection independently of campaign budgets.

0/6 passed · blocked

5,000 Ft independent daily ceilingLive account billing controls

independent 5,000 HUF daily account protectionaccount-wide coverage proofreset/failure behavior receipt

Verification, constraints and evidence

Verification criteria

verify the provider supports a user-configurable daily account cap or an equivalent provider-enforced mechanism covering all campaigns and future campaign additions.
Read back 5,000 HUF, day boundary/timezone, coverage and reset semantics.
Demonstrate protection without spending to the cap, using documented provider guarantees plus readbacks and safe boundary tests where available.
A cumulative account spending limit does not become a daily limit by naming it one.
A polling-based pause rule may overshoot and is not proof of an exact ceiling.
Campaign budgets do not independently enforce this requirement.

Constraints

keep configured Meta allocation at 3,000 HUF, not 5,000
do not reset cumulative limits or alter payment methods as a shortcut
no activation of the new Meta setup while required protection is unproven
do not claim a guarantee from delayed reporting. If technically unavailable, retain the exact requirement as blocked and prepare concrete alternatives for Matt rather than silently weakening it.

Live billing UI reads 'Daily spending limit (set by Meta): 20,850 Ft'. Its separate account spending limit explicitly controls total ad costs and does not reset daily without a change. No editable 5,000 Ft account-wide daily ceiling was shown. No cap was changed. See local meta-capability-readback.json.

Required screenshot evidence slot: account-wide cap and daily reset semantics

Verify enquiries to prove conversion tracking

Trace accepted enquiries from each form integration to business and platform receipts.

0/8 passed · partial

Production enquiry formshttps://balionline.hu/csoportos-utak-gyujtooldal/Historic tracking receipt/Users/agency/Documents/Agty/Analit/outputs/meta-consent-tracking-goal-20260917/GOAL_HANDOFF.md

form-route/event mapend-to-end receiptsnegative/dedup test results

Verification, constraints and evidence

Verification criteria

inspect the collection page's enquiry flow, collection-to-trip paths, and the three directly advertised trip forms.
Map each unique form integration to its success handler and business inbox/CRM route.
Test success through every materially distinct integration and negative validation on each advertised page.
Use the minimum clearly labelled synthetic submissions needed to prove genuinely different routes.
A completed accepted form must reach the business receipt, Meta Lead diagnostics, and the intended GA4/Google Ads conversion path where configured.
Verify correct pixel/dataset and Google action identity, existing conversion inclusion/primary settings, no duplicate primary Google actions, accepted-success-only firing, consent state, repeat-click/reload/retry behavior and browser/server deduplication where both are used.
Preserve permitted UTM/click attribution without putting personal form fields in analytics URLs or logs.
Compare platform-attributed leads separately from actual accepted enquiries.

Constraints

field focus, form starts, button clicks, scroll and page views are not lead conversions
no fabricated events/CRM receipts
do not bypass CAPTCHA or revive the historic one-day consent override
preserve the actual live consent configuration and report a stale bypass if present. Tracking repairs must be narrow and reversible, with before-state and rollback. A test event alone does not prove production bidding receives the same event path.

18 September real collection hero/widget submissions reached distinct CRM rows. On 22 September the live thank-you script was repaired to require the pending token created by an accepted form event and to send Google Ads action 7765606969 only inside that gate. GTM version 22 was published: seven CF7 enquiry triggers now require analit_form_success on the matching thank-you URL, eliminating button-press Meta Lead and GA4 form events. PHP lint, exact FTP readback, public page event order, local direct/forged/denied/accepted/reload gate tests passed. A fresh live collection submit returned acceptance_missing with zero Meta Lead and zero GA4 form-submit requests. GA4 Admin readback confirms generate_lead is a key event; Ads action 7765606969 is enabled, one per click and included in the task custom goal. GA4 and Ads had no rows for this new path during 18–22 September. Accepted live CRM/platform receipts, trip-form proof and CAPI dedup remain open. See local provider-conversion-readback-20260922.json, tracking-verification-20260922.json, live-thankyou-after-gtm.php, GTM-M29KW7WN_v21-backup.json.

Required screenshot evidence slot: genuine form outcome and event diagnostics

Align Search to the collection page

Keep Search traffic and conversion goals aligned with the collection page.

0/4 passed · partial

Google Ads routing/Users/agency/Documents/Agty/Analit/GOOGLE_API_ACCESS.md

enabled Google Search configurationURLconversion audit

Verification, constraints and evidence

Verification criteria

current readback shows the retained prior-plan 3,000 HUF/day Search budget, correct account, approved RSA text/keywords and conversion goal.
All paid final URLs, mobile URLs, sitelinks and other clickable assets within this launch route to the collection page.
Verify Search scope and network settings, approved geographic scope, tracking templates and absence of competing duplicates.
Preserve suitable existing settings and use actual search-term evidence for changes.

Constraints

no separate trip-page paid destinations, new channels or invented negatives
no budget transfer from Meta
no unrelated campaign cleanup.

Fresh Google Ads API confirms task Search 24253795852 PAUSED at 3,000 Ft/day, Search only, Search partners/display off, presence targeting to Hungary, both approved RSAs with collection final URLs and no mobile override or ad-level tracking template. Custom goal 6459059438 includes action 7765606969; its exact label is in the accepted-success gate. Target has no campaign/ad-group assets; sole account-level off-destination sitelink is PAUSED. Campaign final URL suffix carries UTMs. Older Bali Search 23492984549 remains ENABLED at 1,500 Ft/day; seven positive keyword texts overlap, so a cutover check is material. LAST_30_DAYS search-term-view readback: older campaign 260 rows/2,973 impressions/547 clicks/33,915.92 Ft; task campaign 32 rows/173 impressions/24 clicks/2,676.44 Ft, historical while currently paused. No new negatives or budget changes. Accepted provider receipt and duplicate cutover remain open. See google-final-audit.json.

Schedule checks to email weekly findings

Prove the Monday schedule and delivery of a report to Matt.

7/10 passed · scheduled; initial email sent

Monday 17:00 BudapestAuthenticated Matt email identity

one scheduled Codex checka verified email routeone clearly labelled initial reportsend receipt

Verification, constraints and evidence

One Monday 17:00 Europe/Budapest Codex heartbeat, analit-monday-campaign-verification, targets this executor task. Fresh 22 September saved-record readback found it PAUSED after an earlier active readback; the cause was not exposed. The existing automation was updated through the app to ACTIVE, and saved-record readback confirmed ACTIVE with the same schedule, prompt and target. Its exact next occurrence and DST handling lack provider readback. The initial verification report was sent once to Matt via authenticated agency Gmail API; provider message 1a0c5febdbeb3834 has SENT label and matched recipient/from, with local idempotency receipt. No claim that a sleeping Mac guarantees timely delivery.

Activate campaigns to verify live delivery

Verify effective delivery after the applicable checks pass.

0/7 passed · blocked

Verified contentVerified conversion pathsVerified applicable controls

activated eligible campaignsdelivery evidencefinal live boardconcise manual-checkrollback guide

Verification, constraints and evidence

Verification criteria

activate each independently ready platform after its applicable content, conversion and spend checks pass.
Read back effective status and policy eligibility at all levels.
Verify first real post-change impressions/spend without conflating a green switch with delivery.
Use an initial observation window up to 24 hours and a bounded scheduled follow-up if review or delivery is pending.
A timeout produces an honest pending/block diagnosis, not an invented pass or budget increase.
The board and final ledger agree on intended versus actual settings and every acceptance result.
Show only essential human steps, such as unavoidable account verification/CAPTCHA or inaccessible receipt confirmation.

Constraints

Meta activation requires both strict targeting and the account-wide ceiling, Google work continues independently if Meta is blocked
do not leave everything paused as the intended endpoint
no claim of profitability or booked-trip results at launch
no extra campaign executor for this run.

One collection Meta ad set/ad remain off and unpublished; no new Meta activation without strict interest eligibility, independent daily cap and provider validation. Google task campaign remains paused pending real conversion-path proof and overlap resolution. Existing active campaigns were not paused merely to simulate protection.

Required screenshot evidence slot: effective delivery and post-change status

Reviewed launch copies

Eight launch variants, two per destination. All nine saved HTML edits are incorporated verbatim. These edited fields supersede the earlier copies. Image pairings were selected from client images 1–10 for staging; no provider previews exist yet.

COL-A · Collection · Szervezett kiscsoportos Bali utak

Balira vágysz, de nem egyedül szerveznéd meg? Magyar idegenvezetéssel, gondosan összeállított programokkal és több fix indulással várnak csoportos útjaink.

Headline: Szervezett kiscsoportos Bali utak

Description: Magyar kísérettel, fix indulásokkal

CTA: További információ

User correction. Other fields: matching hosted library / factual draft. · Staging image pairing recorded in the private creative manifest; provider preview pending.

AUT-A · Autumn · Hosszabbítsd meg a nyarat Balin

Nyaralás novemberben Balin? 12 éjszaka, magyar idegenvezetés, tengerparttal, helyi kultúrával. 2026. Okt. 24.- Nov. 7.

Headline: Hosszabbítsd meg a nyarat Balin

Description: 1 250 000 Ft / főt

CTA: További információ

User correction. Other fields: matching hosted library / factual draft. · Staging image pairing recorded in the private creative manifest; provider preview pending.

NY-A · New Year · Balinéz újév, kész tervvel

Éld át a Balinéz Újévet ott, ahol a Nyepi hagyománya megszületett. ✈️ 12 éjszaka, 8 éj Ubud és 4 éj Nusa Dua, magyar kísérettel. 📆 2027. március 5–19

Headline: Balinéz újév, kész tervvel

Description: Bali, 12 éjszaka

CTA: További információ

User correction. Other fields: matching hosted library / factual draft. · Staging image pairing recorded in the private creative manifest; provider preview pending.

SPR-A · Spring · Tavaszi Bali út, leszervezve, idegenveztővel

🏝️ Tavaszi utazás Balira 🌛 12 éjszaka 📆 Április 5–19. 🇭🇺 Magyar kíséret végig

Headline: Tavaszi Bali út, leszervezve, idegenveztővel

Description: 2027. április 5-19.

CTA: További információ

User correction. Other fields: matching hosted library / factual draft. · Staging image pairing recorded in the private creative manifest; provider preview pending.

COL-B · Collection · Bali utak, előre leszervezve

Vízum, szállás, programok, transzferek és távolságok? Nem neked kell elintézned! A csoportos Bali utjainknál ezt levesszük a válladról. Az útvonalat, a szállást, a transzfereket és a programokat egy ajánlatban kapod meg, és a csoporttal végig ott van a magyar kísérő. Válassz egyet az előre szervezett utak közü!

Headline: Bali utak, előre leszervezve

Description: 12 éjszaka az Istenek Szigetén

CTA: További információ

gyujto/GY-2 · Staging image pairing recorded in the private creative manifest; provider preview pending.

AUT-B · Autumn · Őszi Bali út, kész tervvel

🏝️ Ha meghosszabbítanád még egy kicsit a nyarat Balin: a repülő, a szállás, a transzferek és a napi program már össze van rakva. 👉 A weboldalunkon látod a teljes árat, és hogy melyik nap mi vár rád a 12 éjszaka alatt.

Headline: Őszi Bali út, kész tervvel

Description: 2026. okt. 24. - nov. 07.

CTA: További információ

oszi/LP-2 · Staging image pairing recorded in the private creative manifest; provider preview pending.

NY-B · New Year · Balinéz újév, kész tervvel

🎊 Ha ott lennél a balinéz újévkor: a repülő, a szállás, a transzferek és a napi program már össze van rakva. Neked egy döntés marad. Jössz-e március 5. és március 19. között? 👉 A weboldalunkon látod a teljes árat, és hogy melyik nap mi vár rád a 12 éjszaka alatt.

Headline: Balinéz újév, kész tervvel

Description: 2027. március 5–19.

CTA: További információ

ujev/LP-2; date corrected to production page · Staging image pairing recorded in the private creative manifest; provider preview pending.

SPR-B · Spring · Tavaszi Bali út, kész tervvel

🏝️ Ha 2027 tavaszán mennél Balira: a repülő, a szállás, a transzferek és a napi program már össze van rakva. Neked csak a fürdőruhát kell elraknod, minden mást intézünk! 👉 A weboldalunkon látod a teljes árat, és hogy melyik nap mi vár rád a 12 éjszaka alatt.

Headline: Tavaszi Bali út, kész tervvel

Description: 2027. április 5-19.

CTA: További információ

lp/LP-2 · Staging image pairing recorded in the private creative manifest; provider preview pending.

Contract details and source precedence

Read authority, sources, recovery and completion

Settled intent and source precedence

Matt's latest written decisions in this task settle scope, budget, targeting, conversion purpose, activation and weekly email. Interpret “daily friends” as forints. Do not repeat questions about trip availability, budgets, sales economics or lead qualification as prerequisites.
The current production landing pages are authoritative for offer facts. Re-fetched on 21 September 2026: all four returned HTTP 200. New Year confirms 5–19 March 2027, 12 nights, eight Ubud plus four Nusa Dua, 1,200,000 Ft/person. Autumn confirms 24 October–7 November 2026, 12 nights, 1,250,000 Ft/person. Use the live spring price/options as displayed, not stale proposal facts.
Preserve Matt's original creative constraints plus the nine newer saved HTML edits, now imported verbatim into selected-copy.md and ad-candidates.json. The newer edits take precedence only for the affected fields. Preserve the eight reviewed launch variants, including line breaks and emoji, and the ten-image restriction. The before/after and comment IDs are in evidence/copy-edit-import.json. Production facts supersede stale review-package facts. If a correction and a later production fact genuinely conflict, isolate the specific conflicting claim and use a fact-neutral approved variant while resolving it. Do not rewrite a landing page to fit an old ad.
The final client-sent HTML is the copy library: https://review.clientsflow.hu/analit-bali-landing-oldalak-2026-08-28-v1/ and its lp, oszi, ujev, gyujto subpages. The complete recovered packages contain 43 distinct full ads across the four paid pages. Other packages are reference only.
Only the ten client-created images from the approved Drive folder may supply ad imagery. No Figma adaptations, stock replacements, generated images/video or automatically generated artistic variations.
Earlier broad-audience/50–20–30 audience allocations are superseded by the strict initial interest filter and fixed destination budgets. Later targeting experiments belong in the queue, not the initial launch. Sumba and other spring trips can remain discoverable through the collection page without new separately funded ad sets.
The transcript auto-dispatch heartbeat remains paused. The latest explicit create-and-pin instruction authorizes this one executor. Do not revive the obsolete watcher or create a duplicate executor.

Campaign configuration

Platform / unit	Daily budget	Final URL	Initial ads
Meta collection ad set	1,200 HUF	https://balionline.hu/csoportos-utak-gyujtooldal/	Exact corrected collection copy + selected GY organization variant
Meta autumn ad set	600 HUF	https://balionline.hu/utazas/oszi-szunet-bali-gili/	Exact corrected autumn copy + destination-matched organization variant
Meta New Year ad set	600 HUF	https://balionline.hu/utazas/balinez-ujev-2027/	Exact corrected New Year copy + date-corrected organization variant
Meta spring ad set	600 HUF	https://balionline.hu/utazas/tavaszi-nyaralas-bali/	Exact corrected spring copy + destination-matched organization variant
Google Search collection	3,000 HUF	https://balionline.hu/csoportos-utak-gyujtooldal/	Existing approved RSA assets, verified against this destination

Implementation recommendation: reuse the existing Website Leads campaign if suitable and give four ad sets their own budgets, with campaign budget redistribution/sharing disabled. The executor may choose an equivalent hierarchy if it preserves all four allocations. These are configured daily budgets, not promised actual daily spend or equal ad rotation. Do not add the current 2,000 HUF/day ad set on top. Reuse/update it where suitable or replace it with an audited cutover and pause the superseded hierarchy. New objects should be staged paused and activated after acceptance checks.

Meta: Website conversion location, maximize website leads, genuine successful form submission as the primary Lead event. Highest-volume bidding is the starting implementation choice unless existing verified constraints require another compatible approach. No invented target CPL, revenue target or booking-quality gate. CTA: További információ. Use the eight reviewed launch variants, two per destination. Do not substitute older library variants for Matt’s edited text. If a specific asset fails an actual platform requirement, record the exact issue and use another already reviewed compatible variant while preserving destination coverage. Do not perform stylistic rewrites of the edited copies. The executor chooses the best compatible images from the ten and records the actual pairings, reasons and previews.

Targeting: Hungary, all genders, inherited 45–65 age range subject to exact available controls. Initial eligible interest categories are organized/package/guided travel, luxury travel, and luxury cruises. The initial implementation interpretation is OR among provider-verified equivalents in those three categories: a person must match at least one. It is not a new three-way AND requirement. Generic Travel/Vacations, Luxury goods, unrestricted broad audiences and automatic expansion beyond the selected interests do not satisfy the strict filter. Record exact selectable labels, IDs, Boolean construction, reach estimate, and control-versus-suggestion status. “Luxury cruises” is a targeting category, not permission to claim these Bali trips include a luxury cruise. Use compatible approved-image placements, with actual preview checks. Do not equate Advantage+ placements with Advantage+ audience expansion.

Future tests: alternative interest combinations, a broader audience, 35–44, geographic splits, retargeting and lookalikes can be recommended in Monday reports. Do not activate them or redistribute budgets merely because they appear in historical suggestions.

Execution order

Run one native goal loop: establish the current state, implement an in-scope deliverable, read it back or test it, repair material failures, and update the same board with evidence. Use goal lifecycle tools according to their rules. Keep working through independent deliverables when one platform is blocked. Ask only for an irreducible missing permission, human-only action or consequential change to an explicit constraint. Do not request routine approval or ask the parent to supervise.

At execution start, first read the baseline and resolve the consequential Meta capabilities in D3 and D4 before activating or replacing its existing delivery. Current UI interest suggestions do not prove a strict filter, and a reported spending-limit label does not prove a daily hard ceiling. Preserve exact provider evidence if either combination is unavailable. Complete independent Search, creative selection, tracking verification and scheduled reporting work while the affected Meta criterion remains blocked. Do not pause unrelated existing campaigns merely to simulate account-wide protection. Apply the authorized audited cutover only to the superseded in-scope hierarchy.

Authority and bounded recovery

The authorized executor owns reversible campaign creation/update/activation, superseded-object pausing, narrow conversion-tracking repairs, required spend protection and weekly-report scheduling/sending within the stated accounts and amounts. Existing authorization already covers activation and the weekly email to Matt. Use the computer, APIs and bounded subagents as needed. Recover existing access before asking for credentials. Fresh provider capability/access failures are technical findings, not new business questions. Do not ask Matt to repeat settled decisions or to perform checks the agent can obtain.

No authority for wider budgets, unapproved interest expansion, relaxed cap semantics, new image generation, unrelated website redesign, altered offer facts, new outside recipients or permanent deletion. Keep any platform-incompatible requirement visible. Repair failures and reverify the affected criteria. When permitted alternatives are exhausted, block only the affected action with evidence and an exact resume point.

Current evidence and remaining technical checks

Fresh Meta UI: one active campaign 120254408012460450, one active ad set 120254408012470450 at 2,000 HUF/day, one ad 120254408012450450. Existing event: Website / Maximize number of leads / balionline.hu meta pixel / Lead. UI reports one attributed Website Lead at 7,051 HUF in 22 August–20 September, not independently reconciled to a real enquiry.
Audience UI currently says Advantage+ on and interests are suggestions. “Further limit the reach of your ads” exists, but its eventual enforcement was not changed/tested during Prepare. No campaign settings were saved.
Billing page connection failed. The requested adjustable daily account ceiling remains unverified. Meta help pages were login/throttle blocked, so no unsupported universal platform claim is treated as fact.
All four production destinations and the published review index returned HTTP 200 in evidence/source-fetch.json. Full pages and extracted text are local evidence, not copied into the public board.
The Gmail connector requires reauthentication, but existing local OAuth access was recovered: token refresh and Gmail profile both returned HTTP 200, with Gmail send/read scopes. Matt's recipient was verified as Matt’s verified agency inbox. No email was sent in Prepare. Reuse the authenticated Gmail API route without requesting connector reauthentication. The actual send and Sent-folder receipts remain D7 acceptance work; a scheduler receipt alone is not delivery proof.
The 17 September tracking report recorded missing genuine form/Turnstile and Meta API proof. Later 18 September evidence supersedes its form-only blocker: real collection and floating-widget submissions reached the thank-you page and distinct single CRM rows, with no duplicate on reload. See outputs/analit-collection-goals-20260918/hero-evidence/crm-two-form-followup.json and thankyou-copy-real-success-tabs.json. Those receipts do not include the actual Meta/Google conversion event trace, and do not prove the three directly advertised trip forms. Reuse valid evidence and recheck the current integrations. The earlier one-day consent override is historical authority, not permission for a new bypass.

Inputs, ownership and delivery

Project root: /Users/agency/Documents/Agty/Analit.
Run root: /Users/agency/Documents/Agty/Analit/outputs/analit-campaign-lll-20260921.
All relative resource references in this contract resolve against the canonical project root above, not a fresh worktree. If Codex provides an isolated worktree, read the current uncommitted access/source artifacts from the canonical root and write this run’s deliverables to the absolute run root. Preserve unrelated edits and do not commit credentials or raw private evidence.
Board URL: https://review.clientsflow.hu/analit-campaign-verification-2026-09-21-v1/.
Board source: verification.html in the run root. Publish with /Users/agency/.agents/skills/comment-html-review-host/scripts/publish_host.py, document analit-campaign-verification-20260921, name analit, about campaign verification, date 2026-09-21, version v1. Never deploy the private evidence/transcript directory as assets. Preserve comments and reuse this run URL.

Required input sources: PROJECT_STATE.md, the 18 September follow-up receipts above, ACCESS_GOOGLE_META.md, GOOGLE_API_ACCESS.md, ADS_ACCESS.md, current production URLs above, outputs/campaign-reconstruction-20260921/final-hosted-reconstruction/setup-list.md and the four complete copy packs, outputs/analit-ads-ready-20260915/meta/drive-creatives-20260915/1.jpg through 10.jpg, this run's selected-copy.md, ad-candidates.json, evidence/copy-edit-import.json, evidence/images.json, and historical tracking evidence at outputs/meta-consent-tracking-goal-20260917/GOAL_HANDOFF.md. Use the ads-budget, ads-creative, ads-attribution and ads-landing skills plus the cached claude-ads Meta/plan sources as methods, not higher authority than Matt's instructions.

Executor owns the agreed provider changes and run outputs, and meaningful changelog/state updates. Other workers' edits and unrelated project files are preserved. Base board text remains black, executor updates/evidence blue, verified checkboxes green, failures red. Check a criterion in source only after proof exists, and republish after meaningful progress. Missing proof remains unchecked. Keep private snapshots and personal information local. A local/hosted board mismatch or inability to maintain the board is a launch capability gap.

Return one evidence-complete final report at REPORT.md in the run root to parent task 01a0c2c4-4fa2-7531-8c2d-5b10ca9b06cb on local host using to-my-parent. The parent records the child task ID once in dispatch-receipt.json. Read it and do not create another executor. The parent goes idle after pinning: send only one evidence-complete completion or irreducible blocker return, no progress messages or supervision requests. Full completion requires every deliverable proved. If a criterion remains blocked after permitted recovery, return PARTIAL with the exact residual blocker and all independent deliverables finished; do not label the campaign goal complete. A created child, accepted mutation or active switch is not task completion.

Review and launch

Matt explicitly requested creation and pinning of one Sol Medium executor after the parent incorporates the copy edits and checks this brief. That latest instruction authorizes dispatch. Activation still requires the applicable targeting, spending and conversion proofs above. The parent will remain idle after dispatch.