Billiard landing page — success screen + lead tracking

Two fixes on fusiontables.hu/billiardasztal/: a nicer confirmation screen, and a way to trace every lead back to the ad that brought it

Master summary — the gist in 30 seconds

TL;DRFixed the ugly form confirmation on all 3 forms, and made every lead traceable back to the exact ad/click that produced it — plus a plain brief for Norbi on the 2 account-side steps still needed.

Input: a screenshot of an ugly green confirmation box, and a request to track ad clicks. Output: a polished gold 'Köszönjük!' screen on every form, and hidden tracking data riding along on every submitted lead — visible in the email and the Google Sheet.

Why this mattersA lead form that looks broken after submission makes visitors doubt it worked — some will call instead, or not bother. And without click tracking, nobody can tell Norbi which ad, which platform, or which of the 3 forms actually produces customers — so ad spend gets allocated on guesswork instead of evidence.

flowchart LR
  A["Visitor clicks<br/>a Google/Meta ad"] --> B["Lands on<br/>billiardasztal page"]
  B --> C["Fills in one of<br/>3 forms"]
  C --> D["Gold 'Köszönjük!'<br/>screen"]
  C --> E["Lead email +<br/>Google Sheet row"]
  E --> F["...now carries<br/>which ad it came from"]

1 · The success screen fix

TL;DRAll 3 forms now show the intended gold checkmark card instead of WordPress's default plain green box.

Input: a form that already had a nice 'Köszönjük!' card designed and hidden in the code, but nothing ever told it to appear. Output: it now shows automatically the instant a submission succeeds, on the hero form, the bottom contact form, and the floating chat widget alike.

Why it mattersFirst impressions after a lead submits shape whether they trust it went through. A half-built success state (present in the code, but never switched on) is worse than not designing one at all — it looks like an oversight, not a feature. This was leftover from an earlier build pass and simply needed to be connected.

flowchart TD
  A["Form submitted"] --> B{"CF7 marks the<br/>form '.sent'"}
  B -->|before fix| C["Plain green<br/>WordPress box"]
  B -->|after fix| D["Gold checkmark<br/>'Köszönjük!' card"]

2 · Click-ID capture — every lead knows its source

TL;DREvery form submission now silently carries which ad platform and click brought that visitor in.

Input: a visitor arrives via a Google or Meta ad link (which quietly attaches an ID like gclid or fbclid to the URL). Output: that ID rides along invisibly, gets saved even if the visitor browses around first, and lands in the lead notification email and the Google Sheet the moment they submit any form.

Why it mattersWithout this, every lead in the Sheet looks identical — no way to know if it came from Google Search, a Meta ad, or organic traffic. That makes it impossible to tell which campaign is actually working. This closes that gap for all major ad platforms at once (Google, Meta, Bing, TikTok, LinkedIn), not just Google.

flowchart LR
  A["Ad click<br/>(?gclid=...)"] --> B["Saved in the<br/>visitor's browser"]
  B --> C["Visitor browses,<br/>maybe leaves and returns"]
  C --> D["Fills in a form"]
  D --> E["ID attached to<br/>the lead email + Sheet"]

3 · The lead signal for Google Ads — Norbi's part starts here

TL;DRA clean 'a lead just happened' signal now fires every time — Norbi just needs to connect it to Google Ads.

Input: someone successfully submits any of the 3 forms. Output: a tagged signal ('generate_lead', labeled hero/cta/chat) fires immediately, ready for Norbi to wire into a Google Ads conversion action inside the tag manager — no further code changes needed on the site.

Why it mattersRight now Google Ads sees clicks on the page, but has no idea any of them turned into a real lead — so it optimizes purely on traffic, not on results. This signal is the missing link; once Norbi attaches it to a conversion action, Google Ads can start optimizing toward actual leads instead of clicks.

flowchart TD
  A["Lead submitted"] --> B["'generate_lead' signal fires"]
  B --> C{"Norbi's job:<br/>connect in Tag Manager"}
  C --> D["Google Ads counts<br/>it as a conversion"]
  C --> E["Ads can now optimize<br/>for real leads"]

4 · What's left — a plain brief for Norbi

TL;DRTwo account-side steps remain that only Norbi can do — a written brief with exact steps is ready for him.

Input: the tracking now live on the site. Output: a plain-language document listing exactly what to click in Google Ads and Tag Manager — creating the lead conversion action, and setting up call-forwarding so phone calls to +36 30 914 9330 count as conversions too.

Why it mattersCreating conversion actions lives inside the ad accounts themselves — that's account access and campaign-strategy judgment, not a website change, so it has to be Norbi's hands on the keyboard. The brief exists so he doesn't have to reverse-engineer what changed on the site first.

flowchart LR
  A["Site tracking<br/>(done)"] --> B["Norbi: create Ads<br/>lead conversion action"]
  A --> C["Norbi: set up call<br/>forwarding number"]
  B --> D["Campaigns optimize<br/>on real leads"]
  C --> D

Norbi's tracking setup brief →CHANGELOG →Live page →