Website enquiries & usability
Can customers contact you after rejecting cookies?
Rejecting optional analytics should not, by itself, stop someone asking your business for a quote. The enquiry form and the tools measuring website activity do different jobs. Before assuming a quiet inbox means less interest, check the contact journey with analytics rejected as well as accepted. This is a useful check for service businesses in Stoke-on-Trent and across the UK, especially after changing a cookie banner, form or website host.
A contact request and an analytics event are different things
A contact form needs to get the information a visitor chooses to send to the right destination. Analytics measures activity such as a page visit, a button click or a successful submission. A business can receive an enquiry that is absent from its analytics reports. Equally, a recorded click does not prove that anyone sent a message.
The behaviour of tracking after rejection depends on its implementation. Google distinguishes basic consent mode, which blocks its tags until consent, from advanced mode, which can send cookieless pings when consent is denied. Do not judge your form by whether a graph changes. Ask your developer to explain what your own site sends and why.
Prepare one clearly labelled test
Choose a service page that matters to your business, then follow its actual quote or contact button. Start on a phone rather than going straight to a form address supplied by your developer. You are checking whether a customer can find and complete the journey.
Agree the test with whoever receives enquiries. Use contact details you control and a recognisable label such as WEBSITE TEST 25 OCT. Keep real customer information out of screenshots. If your developer has a preview with test responses, use that for repeated success and failure checks; arrange a separate, limited live delivery test with the receiving team.
Check these four consent states
Before choosing: open a fresh private browsing session and inspect the page. Can you read the service information and reach the form? Does the banner cover a button or make the page awkward to use on a small screen? Note any feature that waits for a choice instead of assuming it is broken.
Reject analytics: choose the option that declines optional measurement. Follow the enquiry route, check required-field errors and complete the agreed test. The important result is whether the request is accepted and reaches its intended destination, even if no analytics event is recorded.
Accept analytics: repeat with permission for the intended measurement. The contact journey should still work. If submissions are measured, ask the developer to check that one successful request is counted once and a failed request is not counted as a completed enquiry. Avoid sending repeated live tests just to populate a report.
Withdraw: reopen the settings and switch analytics off again. Check that the choice is respected on another page and that customers can still contact you. If changing a choice refreshes the page, check whether an unfinished message is lost and whether the site warns the visitor before that happens.
If the form only works after accepting
Record the exact symptom: a missing form, a loading spinner, an inactive button or a message about a blocked service. Ask which dependency needs the consent. It could be a third-party form, an embedded booking tool or a spam-protection service, rather than analytics itself.
Do not simply remove spam protection or relabel every script as necessary. Have the developer review the actual dependency and its purpose, separate it from optional measurement where appropriate, and provide a usable alternative contact route. The ICO explains that storage and access exceptions depend on the purpose and conditions of the technology. A functional test alone cannot establish legal compliance.
Platform behaviour varies. HubSpot, for example, documents that its forms can still display and collect submissions when visitors decline tracking cookies. That is evidence that contact and tracking can be separated in that platform, not a guarantee about every form or integration.
Keep a short record of what actually passed
Use one line per check: page and form; phone or desktop browser; consent choice; result on screen; receiving destination; person who confirmed receipt; date and time; issue and person responsible. Mark an untested step as not checked, rather than turning a reassuring screenshot into a complete pass.
For example, a hypothetical landscaping firm might record: patio page → quote form → analytics rejected → request accepted → mailbox receipt not checked. That is a useful partial result. It is not yet evidence that the team can read and reply to the enquiry. The next step is a delivery check, not another design change.
A WhatsApp button needs its own check too. Opening the intended conversation is different from sending a message or receiving a reply. Keep those outcomes separate from a website link-click count.
What we checked on Zero Labs
On 25 October 2026, we ran controlled browser checks of our own website at 320px, 390px and desktop widths. With analytics rejected, the enquiry form could still complete its tested submission journey. Failed test responses did not count as leads, and a repeated submit action produced one accepted test request. The settings control was also moved into the footer so a floating box did not stay over the page after a choice.
Those enquiry checks used simulated server responses. They did not send a real enquiry or establish inbox delivery. Separate live checks confirmed that Google accepted a consented page-view request and that withdrawing consent removed our analytics cookies without loading the tag on the rejected reload. These are implementation checks, not evidence of more customers, higher rankings or blanket compliance.
Agree the fix before considering a rebuild
A consent dependency, an obstructive mobile panel or a misleading success message may be a focused repair. Ask for the fault, proposed change and acceptance check in writing before committing to a larger website project. Retest the affected journey after changes to forms, consent tools, hosting or email routing.
If you would like Zero Labs to review the public journey, share the page address and what happens after rejection. Account-level consent settings, mail delivery and any live test submissions need their own agreed access and scope. A public-page review is a starting point, not a substitute for checking the receiving inbox.
Take the next step.
Explore the related services and guides to plan your next step.