A website can attract visitors without generating suitable enquiries or profitable orders. To understand what works, you need to track actions that bring visitors closer to doing business with you. Website conversions provide that perspective when you define them clearly and interpret them in context.
Not every click means a new customer. Useful measurement connects website behaviour with enquiries and orders actually recorded by your business, while acknowledging what your tools cannot observe.
Choose website goals that reflect your business
Start with a question: which visitor action has value for your business? For a plumbing company, it might be a service request with enough information to contact the customer. For a shop, it could be an order placed, followed by payment confirmation. For a consultant, it might be an accepted appointment.
Separate primary outcomes from intermediate actions. Opening a form or viewing a service page shows interest, but does not establish that you have received an enquiry.
- Primary goal: a quote request successfully recorded.
- Intermediate action: clicking the „Request a quote” button.
- Quality indicator: the enquiry concerns a service you provide and your team can handle it.
For each goal, document what completion means, where you check the result and who validates it. For example, with quote requests, treat successful form submission as the initial conversion and confirmation that the enquiry is relevant in your sales records as a separate stage. This keeps enquiry volume distinct from enquiry value.
Measure completion, not just a button click
A click on „Submit enquiry” can be followed by a validation error, a connection problem or abandonment. If you record the conversion at the moment of the click, your report may include enquiries that never reached your business.
For conversion measurement, look for the signal closest to the actual outcome: confirmation from the application that the form submission was recorded or the order was created. The message „Your enquiry has been recorded” should appear after the operation succeeds, not beforehand.
Keep actions that are difficult to verify separate
Clicking a telephone link indicates an intention to call; it does not prove that a conversation took place. Similarly, opening an email application does not confirm that a message was sent. Give these events clear names, such as „Phone number click”, rather than „New customer”.
For orders, distinguish between order creation, payment confirmation and completion of the sale. A cash-on-delivery order is not paid simply because the visitor reached the confirmation page. Keep these stages separate so you can interpret the results correctly.
Avoid counting the same conversion twice
A confirmation page can be refreshed or opened again. An event might be sent by both the shop integration and a separately configured tracking setup. In either situation, the same action could appear more than once.
Where your application and measurement tool support it, use a unique identifier for each order or enquiry. Configure deduplication according to the tool’s documentation and check that it works with your integration. Having an identifier alone does not guarantee that duplicates will be removed.
- Check whether multiple integrations send the same event.
- Refresh the confirmation page and check for an additional conversion.
- Test returning to the confirmation page through browser history.
- Compare identifiers in reports with your actual records.
For example, if an order appears twice with the same identifier, investigate the event sources before interpreting the increase as business growth. Avoid adding together conversions attributed separately by different advertising platforms: they may claim credit for the same order.
Account for consent and measurement limitations
Reports do not always cover all activity. Refused consent, blocked scripts, browser restrictions and the use of multiple devices can interrupt your view of a visitor’s journey. Someone might discover your service on a phone and later place an order on a laptop.
In Romania, Law no. 506/2004 is relevant to storing information on a device and accessing it, including through cookies. For technologies that are not strictly necessary, obtain the prior consent required by law. The General Data Protection Regulation, or GDPR, also applies when you process personal data.
For example, if a visitor refuses analytics cookies, their order may exist in your shop without appearing as an observed event in your analytics tool. Do not try to close that gap by bypassing their choice.
Check what each integration collects and avoid sending names, email addresses or free-text form contents to analytics tools. Server-side measurement does not automatically remove legal obligations. If a tool displays estimated or modelled conversions, distinguish them from directly observed conversions, following the provider’s explanations.
Connect reports with actual enquiries and orders
Analytics reports help you understand journeys and traffic sources. Your business records show what you received and what happened afterwards. Compare them regularly, but do not expect an exact match: they may use different recording times, time zones and attribution rules.
For quote requests, distinguish valid enquiries from spam, duplicates and requests that do not match your services. A campaign generating many completed forms is not necessarily the most useful one if your business cannot handle most of the enquiries.
When analysing orders, separate the value of orders placed from money received, and account for cancellations and refunds. For example, a cancelled order may remain in the original purchase report if the integration does not send the corresponding update.
If you track conversion rates, specify the calculation: orders divided by sessions, or buyers divided by users. Compare periods using the same definition. Record configuration changes too, because an increase after fixing measurement does not automatically demonstrate an increase in sales.
Start with an end-to-end test and a simple routine
You do not need to track every interaction from the outset. Choose one primary outcome and check the whole journey before making decisions based on reports.
- Define the conversion, for example „Enquiry successfully recorded”.
- Submit a test form and check that it appears in the application and your team’s workflow.
- Test incomplete fields: an error should not trigger the final conversion.
- Repeat the check after refreshing the confirmation page and with different consent choices.
- Regularly compare measured events with actual enquiries or orders and investigate differences.
Also check that forms and confirmation pages work correctly on mobile devices, including after updates. For your website infrastructure, you can choose GazduireOnline.ro’s web hosting or WordPress hosting services, depending on your platform.
Keep a brief record of definitions, tests and changes. Start with one verifiable conversion, then expand measurement only when each additional indicator helps you make a specific decision.
