Enhanced conversions: how to set up and validate without breaching GDPR

Abstract orange illustration on a dark background: a shield with a check mark. Article topic: “Enhanced conversions: how to set up and validate without breaching GDPR”
In brief

Enhanced conversions improve the match between an ad and a sale by sending customer data (such as an email) in hashed form. They can recover lost conversions, but should only be used with consent, transparency and a setup you can validate.

The essentials in a definition

Enhanced conversions send the platforms first-party data (for example email or phone, hashed) to improve conversion matching. Configured correctly, they increase measurement accuracy; they require a legal basis, transparency and minimisation under the GDPR. The enhanced conversions documentation describes the technical requirements.

What they do

When someone converts, the site sends the platform a hashed identifier (for example a hashed email or phone number). The platform compares it with its own data and, if there is a match, associates the conversion with an ad that was seen or clicked.

This helps when cookies fail, when the click and the purchase happen on different devices or when consent limits observation.

The legal framework

Sending personal data, even hashed, requires a legal basis and clear information. As a rule, consent for measurement and advertising must be recorded, and the privacy policy must describe the processing. Check with whoever handles data protection.

If consent is refused, do not send the data. Configure the site to respect that choice automatically.

Illustrative diagram with 4 numbered steps joined by an orange line, the last one marked as done. It represents: Enabling enhanced conversions safely

Enabling enhanced conversions safely

  1. Confirm consent and privacy policy
  2. Define and normalise the fields to send
  3. Validate with platform diagnostics
  4. Review after any site change

How to configure and validate

Define which fields will be sent, normalise them (lower case, no spaces) and confirm that hashing follows the platform’s instructions. Use the diagnostics offered to check the match rate and any errors.

Test in a controlled environment before switching on widely. Compare conversions before and after, bearing in mind that the increase may be recovery of conversions that already existed.

Large orange quotation marks on a dark background with abstract lines of text, illustrating the quote: “Recovering conversions does not justify collecting data without a legal basis.”
Recovering conversions does not justify collecting data without a legal basis.

Ongoing care

Review the setup whenever you change forms, payment system or e-commerce platform. Small changes can break the data feed.

Keep documentation of what is sent, why and on what legal basis. It is useful in audits and in responding to data-subject requests.

Decision table

StepActionLegal caution
1. Legal basisEnsure consent or another applicable basisDocument and inform in the privacy policy
2. Minimum dataSend only necessary fieldsMinimisation
3. ProcessingApply hashing as specifiedNever send data in clear text where not permitted
4. ValidationCheck diagnostic reportsFix formatting errors

Common mistakes to avoid

  • Sending data without consent. It is an infringement; set up consent first.
  • Incorrect formatting. Addresses with spaces or different capitalisation reduce matching.
  • Not updating the privacy policy. Users must know what data you use and why.

How to measure the result

Track the match rate in diagnostics, the variation of recorded conversions against real sales and the consent rate.

Limits and exceptions

Enhanced conversions do not fix consent gaps or data-quality problems: if collection is poor, matching will be low. There are also legal and platform requirements that vary by market and sector. In some cases, minimisation advises not sending certain data. Always make a legal assessment of your case, validate the platform diagnostic and switch off if the legal basis is not solid.

Illustrative example

Illustrative example: a shop enables enhanced conversions only for users who accepted analytics, sends the hashed email at purchase time and checks the diagnostic report. The match rate rises after correcting formatting, and recorded conversions better reflect real sales. The privacy policy was updated. EDPB guidelines help interpret minimisation.

Frequently asked questions

Do enhanced conversions breach GDPR?

Not in themselves, but they require a legal basis, transparency and respect for consent. Check with whoever handles data protection.

Do they always increase conversions?

They often recover conversions that already existed, but they do not create new sales.

Can I use them without consent?

It depends on the legal basis. For advertising, consent is generally required.

Are enhanced conversions lawful?

They can be, provided there is a legal basis, transparency and minimisation; consult the applicable framework and, if needed, a lawyer.

What data should I send?

Strictly necessary and permitted data, processed as the platform specifies, and only from users who consented where required.

Summary to quote

Enhanced conversions improve measurement with hashed first-party data, but should only be used with a legal basis, minimisation and transparency towards users.

Sources and recommended reading

Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.

Keep reading

Contacto rápido

Quer falar sobre as suas campanhas?

Deixe uma nota curta. Respondo em 1 dia útil.