Enhanced Conversions Setup | Consented Measurement
Enhanced conversions support Google Ads measurement with permitted first-party data. They do not create sales or guarantee recovery of every unmeasured conversion. I first review the existing conversion tag, source fields and consent flow. Deliverables include field mapping, implementation, diagnostics and a test record. Share your scope through the contact page.
Is hashing the same as encryption?
No. Eligible fields such as email addresses or phone numbers are normalised and hashed using SHA-256. Hashing produces a digest rather than reversible encrypted text. It does not make the sharing anonymous or remove consent requirements.
Checked on 15 October 2026: Google’s enhanced conversions overview. Depending on implementation, hashing can be handled by the tag or during data preparation; saying it always happens in the browser is inaccurate.
How do web and lead workflows differ?
Enhanced conversions for web support an existing online conversion. Enhanced conversions for leads require the enquiry to be connected with a later business outcome. A form submission is not a sale; the sales team’s outcome records need a separate design.
What checks are delivered?
| Check | Potential defect | Acceptance criterion |
|---|---|---|
| Data source | Empty field or wrong form | Correct field on the relevant successful action |
| Consent | Sending after rejection | Agreed consent conditions apply |
| Event identity | Reload or retry duplicates | Repeated transactions are handled |
| Diagnostics | Missing fields, format or tag warnings | Documented cause and test evidence |
Tests use sample data; reports do not contain customer details. A low match rate alone does not prove faulty implementation. Matchability, available data and user choices also affect the result.
Frequently Asked Questions
How many additional conversions will be reported?
I do not promise a percentage. Comparison periods, traffic and campaign changes must be recorded; increased reporting is not increased sales.
Can health-form information be used?
Sensitive health information is not an input for this setup. No fields are connected without checking data eligibility and platform policies.
Does this replace conversion tracking?
No. The underlying event must first fire at the correct time and count. Enhanced conversions add measurement support to it.
How do I work?
Work-hour packages
Tell me about your business and what you need on WhatsApp or by phone; we agree on a work block of somewhere between 5 and 40 hours and I start doing what is needed. What you get is not a calendar window — it is net working hours spent directly on your business. I can use 40 hours working three days straight, or deliberately spread it out and finish it over a year — whatever the work calls for. I do not spend my time estimating how long something will take, I spend it doing the work; every hour I spend leaves a lasting result in your business. We keep going for as long as you find it useful.
Why not monthly?
Is 40 hours a week?
On a fixed monthly fee both sides are watching the wrong thing: you watch a fixed cost, the other side watches how many more contracts like this they can line up. Working by the hour puts us both in front of the same thing — the real value of the work that got done. I know not having an upfront answer to "how much will this cost in total?" is the natural cost of this model. But instead of paying a fixed fee for months to a setup that is not producing results, you only pay for the qualified time spent on your work — and you see exactly where that time went, start to finish. That is why my clients keep coming back.