Client asset pack
acceptance report

1

Symptom. A clean cache HIT on the billiard-table landing page serves one visitor's UTM parameters and gclid inside the three rendered CF7 form action URLs to the next visitor who hits the same cache entry.

2

Root cause. The production cache layer, owner not yet identified, caches query-derived personalization fields as part of the static HTML instead of stripping them before the page is cached.

3

Fix. Exclude query-derived click IDs and UTM values from cached HTML. Generate attribution fields per request after the cache layer. Never cache a personalized form action.

4

Who. Site or cache owner, currently unassigned.

1

Symptom. The Google Ads "Submit lead form" conversion action is a page-load trigger on a URL that returns 404. A separate "Purchase" action sits on a URL that returns 200 and is armed but silent.

2

Root cause. Form start stayed Primary and counted Every in Google Ads while the real submission-confirmation URL was never wired to a working conversion action, so both spend and bidding optimize on a page load, not a submission.

3

Fix. Generate one lead_id on server-accepted CF7 success, map it to one canonical GTM and GA4 event, then make the deduplicated submitted-lead action Primary, count once, and move form start and the dead Purchase action to Secondary or retire them.

4

Who. Site or GTM owner for the event, Google Ads account owner for the conversion action change. Both currently unassigned.

1

Symptom. crm.source_column is null on every enquiry row in the form register. No submitted enquiry can be traced back to Google or Meta spend.

2

Root cause. The form register headers never included source, campaign, click-ID or landing-page fields, so a submission lands with no attribution even where a click ID was technically available upstream.

3

Fix. Add lead_id, source, medium, campaign, content, term, landing URL and every click ID to the Sheet, populated from the fields the EDIT-02 payload already captures at submission time.

4

Who. Sales or CRM owner for the sheet schema, coordinated with the site owner who ships EDIT-02. Both currently unassigned.

1

Symptom. The Google Ads conversion_value field carries the raw conversion count tagged with unit "huf", producing a ROAS of 0.0005 that reads as a real return-on-spend figure.

2

Root cause. No verified revenue figure exists anywhere in the stack. The CRM schema has quote and payment fields, but no filled Fusion outcome value, so the count was left in the value field as a placeholder.

3

Fix. Remove the forint-labelled value from the conversion action now. Report spend, clicks and enquiries only, never a computed ROAS, until offline enhanced conversions import a real quote or purchase value from the CRM.

4

Who. Ads account owner for the immediate removal. Sales or CRM owner for the eventual real-value import. Both currently unassigned.

1

Symptom. One report run pulls Google Ads and Meta Ads on 2026-07-25 to 08-23, BigQuery on 2026-07-24 to 08-22, the CRM sheet on 2026-07-26 to 08-24, and work evidence on 2026-06-23 to 08-23.

2

Root cause. Each collector pulls its own trailing window independently, driven by per-source lag and API history limits, and the report assembler merges them without normalizing to one canonical window.

3

Fix. Pick one canonical window per report run. Have every collector clip or pad to it, or return UNAVAILABLE for that source. Treat source_health.range as a gate a report cannot pass with mismatched ranges.

4

Who. The reporting-pipeline owner, the same code line that writes report_data.json.

30 napos eredmények

• The 316 and 976 index values and the work counters are carried over from the accepted v2 report, not recomputed from raw platform logs.

Hirdetéskreatívok teljesítménye

• The CTR ranking excludes four ads below the stated minimum impression floor.
• The duplicate-upload pattern is stated as a correlation, not as a cause.

Versenytársak hirdetései

• biliardcentrum.hu Meta presence is not covered by the snapshot, so it is labelled not available rather than zero.
• 4Biliard.hu individual Google ad start dates are not in the snapshot, only the aggregate count of four.

Hirdetési és célzási stratégia

• The monthly baseline B is unverified because the Meta API token is dead, so every allocation is a percentage with one historical illustration.
• Interest targeting categories are proposals, no current audience size measurement was possible.
• Five non-billiard landing pages are proposed, not confirmed live.

Persona elemzés

• Persona 4 has no age or gender anchor, it is anchored on region and platform only.
• Budapest and Pest combined clicks and form starts are not available, only the verified spend share.

Belső anyagok és QA

• The five-ranges finding id was read from the audit's top-10 table, not from the full consolidated findings file.