Measure the right contact step with a tested implementation.
ImbaHub can help implement conversion tracking for a defined enquiry journey. We start with an approved event definition, review existing tags and connect measurement to a step that can be verified. A click should not accidentally be reported as a received enquiry.
- Contact click
- Accepted server response
- Verified receipt
- Enquiry assessed as relevant
Do not add these steps together as new customers.
An implementation with explicit checkpoints
Define
Agree the event, data source and consent setup.
Connect
Inventory tags and implement one defined signal.
Verify
Test success, failure and retries; retain evidence.
Commission a specific connection
We need the website address, measurement plan, form solution, relevant analytics and advertising accounts, and an owner for receipt. Before adding tags, we inventory installations in source code, CMS and tag management. Missing access is recorded as a dependency rather than a working integration.
An initial scope can cover one form, one defined event and one receiving measurement service. Additional language journeys, CRM feedback, server integrations and further advertising platforms need separate assessment. This makes both the change and its acceptance criteria concrete.
Connect the signal to what actually happened
In a fictional quotation journey, a visitor opens the form, corrects a field and submits. A contact click expresses a different step from an accepted server response. Actual receipt and subsequent qualification require their own sources; we do not treat these outcomes as interchangeable.
The trigger is checked against errors, reloads and retries. Measurement events should not contain message text or unnecessary personal information. The business's decision about permitted processing and sharing must be established before implementation.
| Deliverable | Check | Boundary |
|---|---|---|
| Event connection | The right condition triggers the signal | Not evidence of a later sale |
| Consent signals | Agreed states and changes | Technical behaviour does not replace policy decisions |
| Duplicate protection | Reloads and retries | Each platform assessed separately |
| Handover | Version and test record | Ongoing maintenance agreed separately |
Test consent choices and failure paths
We need your chosen consent and data-processing setup and access to an appropriate test environment. Consent Mode can communicate choices to Google tags; it does not obtain consent by itself or establish that every requirement has been met. Other tags must also follow the specification.
Tests use permitted fictional data. Denied, granted and changed choices are tested against the agreed design. We inspect failed submissions and reopened confirmations so an old step does not appear as a new enquiry. Production account use is limited to the authorised testing scope.
Receive an implementation you can maintain
The handover records event name, condition, source, receiving system, version and test results. A network request, a recorded platform event and a received email are different evidence. Anything not tested remains outstanding.
Scope and price follow the review. Advertising spend, campaign management, licences and larger system changes are specified separately. We do not promise complete measurement or that more recorded conversions mean more customers. Describe the journey so we can propose a first testable delivery.
Sources and further reading
Questions, answered
Do we need a new website?
Not necessarily. We review the existing journey, access and technology first. A rebuild needs its own justification.
Is Google Ads management included?
Not automatically. Measurement implementation, campaign work and media spend have separate scopes.
Can you guarantee complete measurement?
No. Consent, browsers, blockers, integrations and platform processing affect coverage.