Define a valid enquiry
Opening a form signals interest, clicking signals an attempt, and a server-saved order is a different outcome. Combining them can give a misleading impression of advertising performance.
Start with a business rule: required information, the point of successful saving and failures that prevent success. Use the same definition across the website, CRM and advertising account.
Let the server confirm success
Do not send a success event immediately after a click. Validation, registration or database writing can fail. Return success only after the required operations complete.
If an account and order are created together, a transaction helps prevent a partial result. Distinguish a new order from a new registration when an account already exists.
Plan for retries and duplicates
Refreshing a page or double-clicking should not create another enquiry. Plan a request idempotency key, a unique result identifier and event-delivery state.
A browser-side marker is useful but does not alone guarantee one event across devices and network failures. Check the advertising platform’s acceptance and deduplication rules separately.
Compare debugging with stored orders
Test success, invalid input, server errors and page refresh separately. GA4 DebugView helps inspect event names and parameters. Avoid accidentally sending personal information to analytics.
Compare events with real orders. Consent, blockers and network conditions can cause differences. Keep the database as the primary business record.
FAQ: do clicks without enquiries prove the ads are bad?
Not necessarily. The offer, mobile form, speed, trust and errors also matter. When building a landing page, StarWeb checks saving, measurement and delivery to a manager as one workflow.
Sources and editorial note
Prepared on 1 October 2026. Facts are based on the sources below; practical recommendations are editorial analysis. Conditions may change. The cover is an AI-generated illustration, not a photograph of the reported event.