FIG. 06 — Case study
Menkor
One fast B2B landing page with one job: turning a Google Ads click into a measurable HubSpot lead — with full attribution and data handling worthy of a compliance company.
- Client
- Menkor — EPR compliance services
- Year
- 2025
- Role
- B2B lead-gen landing + attribution
- Status
- Live Visit site ↗
- Stack
- HTML/CSS/JSHubSpotGTMConsent Mode v2
The challenge
In B2B, every click has to account for itself.
Extended producer responsibility (EPR) is a legal obligation most affected companies know only by name. Menkor delivers that compliance as a service — and for phase one it needed exactly one thing: a landing page that turns a decision-maker arriving from Google Ads into a quote request.
The scope was deliberately tight: one page, no CMS, no build step, instant load. The bar, however, was high — a company selling compliance can't be careless with data on its own site, and the ad budget had to be traceable from the first click to the contact record.
The system — 01 · Landing
Fast, because nothing in it is spare.
menkor.hu is plain HTML, CSS and JavaScript — no framework, no build step, the page loads instantly. The conversion toolkit is still complete: FAQ accordion, scroll-reveal, count-up stats, a process timeline and an inline SVG icon sprite, all hand-written.
The legal pages were produced from the client's own source PDFs, so the landing itself can focus on one thing: the quote-request form. One page, one goal — every section steers toward it.
The system — 02 · The lead's journey
From click to contact record.
Attribution here isn't an extra — it's the point: an ad budget can only be optimized if every lead carries where it came from. Measurement runs through GTM with Google Consent Mode v2 and a denied-by-default, per-category cookie banner — as you'd expect on a compliance company's own site.
-
GOOGLE ADS
A click arrives
The visitor lands from an ad. On arrival the page stores the UTM parameters and the gclid — the source never gets lost along the way.
✓ utm + gclid captured
-
FORM
Spam defense, invisibly
Two quiet gates work before submission: a honeypot field and a 2-second time trap. Bots get caught; humans never notice.
✓ time-trap OK — human submission
-
HUBSPOT
A lead on the contact record
The form submits via AJAX through the HubSpot Forms API — no page reload, inline success state. Attribution lands on the contact record: you can see which ad brought the lead.
✓ contact created — source attached
-
GTM → GOOGLE ADS
The conversion reports back
A successful submission fires a lead_form_success custom event, which triggers the Google Ads conversion through GTM. The loop closes: the campaign learns from its own leads.
✓ lead_form_success — conversion sent
Results
One page. One goal. Airtight attribution.
- page, with a single goal: the lead
- 1
- page reloads on submission
- 0
- time trap against spam
- 2 s
- attribution — UTM + gclid on the HubSpot contact
- 100%
- Consent Mode, denied-by-default banner
- v2
Lead counts and campaign spend are the client's business data — so this list is about the system built.