A simple example
A completed purchase has eligible customer information available. A supported setup can use it to supplement measurement of that purchase; it should not create another order.
What changes in the measurement flow
Instead of relying only on an advertising identifier, the supported implementation can send additional customer information associated with a conversion. Google distinguishes enhanced conversions for web from enhanced conversions for leads. Choose the route that matches how the business actually completes sales.
Questions to resolve before implementation
- Which completed action is the conversion?
- Which supported fields are available at that moment?
- Who controls collection and consent decisions?
- Which integration already handles the conversion?
- How will the team test successful processing without exposing customer details?
What a good rollout checks
Start with the existing conversion action and its diagnostics. Check that the additional information belongs to the same action, that overlapping integrations do not inflate purchases, and that consent settings are applied as designed. Record the version and test conditions so later changes can be compared.
How to judge the result
A healthier diagnostic signal is useful, but it is not a promise of higher revenue or a fixed recovery percentage. Review reporting changes alongside the store’s orders and the implementation timeline. Keep technical acceptance separate from commercial impact.
Assess the measurement gap before implementation
Suppose advertising reports appear to miss some purchases that the store records. Enhanced conversions may be relevant, but missing events, incorrect values or duplicate purchases still need investigation. Start with the basic conversion action and a sample of real order records inside the business’s controlled environment. Establish what is collected before adding another measurement method.
Implementation planning should include the permitted data, its origin, the approved processing path and the checks used to confirm correct handling. The technical team and the business’s privacy owner need a shared understanding of that scope. Hashing is a technical processing step; it does not decide whether the organisation may collect or use the information. Improved matching also does not establish that an ad caused the sale. Keep measurement improvement separate from claims about incremental growth.
- Verify the original conversion action, transaction identifiers and revenue values.
- Confirm the applicable platform requirements and the business’s approved data handling.
- Compare diagnostic signals after implementation without promising a fixed uplift.
Review conversion definitions →
Frequently asked questions
What are enhanced conversions?
Enhanced conversions supplements Google Ads conversion measurement with supported, hashed first-party customer information. It needs an eligible implementation and appropriate data handling; hashing does not make the process automatically compliant.
Do enhanced conversions replace ordinary conversion tracking?
They supplement a measurement implementation rather than replace the underlying conversion definition. Confirm the collection flow and current platform requirements.
Does hashing customer information settle permission questions?
No. Technical transformation is not a substitute for the appropriate permission and data-use review. The business must establish the permitted purpose and implementation requirements.
Sources and further reading
Primary material for the concepts discussed here. Our practical checklists and illustrative examples are editorial recommendations. Source links open in a new tab.