Which ads bring enquiries your team can actually work with?
A report can show plenty of conversions while the sales team receives few useful enquiries. To understand the gap, connect each campaign to the contact received and its eventual outcome. Start by defining what meaningful progress looks like for your business.
1. Separate intent, contact and outcome
A click on a WhatsApp button shows intent, but does not confirm that a conversation happened. A form submission is not a sale either. Define separate stages and give events clear names so reporting does not mix different behaviours.
- Real estate: enquiry received, lead qualified, viewing arranged and deal completed.
- Hotel or holiday accommodation: enquiry received, offer sent and booking confirmed.
- Booking engine: process started and final confirmation recorded as separate events.
2. Confirm the enquiry was accepted
The submission event should happen after the server or form provider confirms that it accepted the request. A button click or premature success message can count failures as successes. Also check that the contact reaches its operational destination, such as the CRM. Test validation errors, network failures and repeated clicks; use a stable identifier to prevent duplicates.
3. Keep the source with the contact
Attach the landing page and campaign to the record when available and allowed by the consent setup. Document any handoff to external domains, booking engines or embedded forms. The team should be able to understand where an enquiry came from without reconstructing the visitor's session.
4. Bring qualification into the report
Choose a few CRM stages and assign responsibility for updating them. In real estate, qualification might involve confirming location, budget and intent. For a hotel, it may involve dates, availability and whether the request is suitable. Offline conversion integrations can return later outcomes to the advertising platform. Enhanced conversions can use customer-provided data, processed according to Google's requirements, to help match those outcomes.
5. Connect consent choices to tracking
Test behaviour before a choice, after acceptance, after rejection and after changing a choice. Consent Mode communicates choices to tags; it does not replace the mechanism that collects them. Define which data each system receives and how long it keeps it. Hashing an email address does not remove the need to respect consent or applicable customer data policies.
6. Reconcile real enquiries with events
Create a small set of identifiable test enquiries and follow each one through to the CRM and the report. Exclude them from commercial analysis. Then review cost per qualified lead, response time and outcomes by campaign. Attribution differences, delays and measurement gaps remain possible; adding tracking does not guarantee more sales.
Frequently asked questions
Do we need a new CRM?
Not necessarily. First assess the fields, stages and integrations already available. A simple structure that the team consistently uses may be enough to start.
Where does an ArqWeb review begin?
With the actual enquiry journey: ad, landing page, form or booking, destination of the request and sales follow-up. That map defines the fixes and measurement needed.
Reference documentation
A note from ArqWeb
This guide organises checks and decisions for a common situation. Implementation depends on the website, access and systems involved. We can assess your situation if you need help applying these steps.
Let's look at your situation.
Tell us what you need and what you have already. We will reply with next steps and a proposal suited to the work.
Discuss my requirements