Cookies, analytics and advertising
This site is built to run two measurement tools: Google Analytics 4 and the Meta pixel, alongside Meta’s Conversions API, which reports the same enquiry a second time from our own server. Each one is switched on by configuration, and a deployment with neither of them configured loads no analytics or advertising script of any kind.
Where they are switched on, nothing loads until you agree. A banner asks first, and until you press Accept no tag is fetched, no advertising cookie is written and no identifier leaves your browser. Your answer is kept in your own browser under the key oh:consent:v1 and mirrored into a first-party cookie named oh_consent, which is how our server knows whether an enquiry you send may be reported onward.
Accepting lets those tools set their own cookies on this domain — the familiar _ga, _ga_*, _fbp and _fbc — which count visits and show us which pages and adverts lead to an enquiry. With advertising measurement running, a submitted enquiry is also reported to Meta from our server: the event, the page, and a one-way-hashed form of your name, email address and phone number. The hashing happens here, before anything is sent, so Meta can match the event against an account it already holds without receiving those details in readable form.
Change your mind whenever you like through the “Cookie settings” link in the footer, which reopens the banner. Refusing, or withdrawing after accepting, clears those cookies from this domain and stops both the browser tags and the server-side report. The attribution entry in section 03 behaves the same either way: it stays in your browser’s session storage, it travels only with an enquiry you send us yourself, and closing the tab clears it.