apointoo.
Request access
Google Ads for Healthcare

Why Hashing Does Not Make Clinic Forms Eligible for Enhanced Conversions for Leads

cmsapointoo··8 min read

Hashing a clinic form does not make it eligible for enhanced conversions for leads. Google prohibits enhanced-conversion measurement for conversion information related to sensitive categories, including health or medical information. That policy decision comes before tag setup, identifiers, consent records, account terms, or API configuration.

Google also publishes a detailed implementation checklist for businesses that are eligible to use enhanced conversions for leads. It covers data capture, SHA-256 hashing, imports, and diagnostics. Clinics should not read that technical checklist as permission to upload a health-related form. When the conversion falls within the sensitive category, the correct implementation is to keep it out of Google.

What does Google’s customer data policy prohibit?

Google’s Customer data policies apply to enhanced conversions for web, enhanced conversions for leads, store sales uploads, and Google-engaged audiences. The policy says advertisers may not upload conversion information related to sensitive categories. It then states that conversions related to those categories cannot be used for measurement in enhanced conversions or store sales uploads.

Health or medical information appears in Google’s list of sensitive categories. The examples include purchases of medical services, prescription drugs, and medical devices. The wording focuses on what the conversion information relates to. It does not create an exception for a neutral event name, a short form, or a technically valid payload.

A clinic should therefore assess the real action and context. A label such as “lead” or “contact” may still represent a request for a medical service. Changing the label does not change the underlying conversion. The server-side clinic form architecture explains why collection and external delivery need separate decisions.

Why is hashing not an eligibility test?

Google’s implementation checklist tells eligible advertisers to hash personally identifiable information with SHA-256 before sending it. That step helps Google match submitted identifiers. It does not remove the event’s business context or turn health-related conversion information into an unrestricted category.

Hashing appears under data preparation in Google’s checklist, which can make the order seem less important than it is. Preparation explains how eligible data is formatted. Eligibility decides whether the advertiser may use the conversion information at all. Clinics need that answer first.

Condition What it establishes What it does not establish
SHA-256 hashing Technical representation for matching Permission to upload a health-related conversion
Consent record Evidence of a recorded choice under the clinic’s process An exception to Google policy
Legal basis A conclusion under the applicable legal review Eligibility for a Google advertising product
Customer Data Terms accepted An account prerequisite in Google’s checklist Approval of the clinic’s exact event
Generic conversion name A display label A change to the event’s sensitive meaning

How should a clinic classify a form conversion?

Start with a plain description of the action. State what the person is asking for, where the form appears, what service the page concerns, and what operational record the submission creates. Do this internally, before adding a tag or creating an import.

Next, compare that description with the current Customer data policies. If the conversion information relates to health or medical information, stop the enhanced-conversion review. Do not continue to identifier selection, hashing, testing, or activation. An accurate stop decision is more useful than a completed technical checklist for an ineligible event.

Date the classification and keep its scope narrow. A general newsletter form and a consultation request may sit on the same domain while representing different actions. Neither becomes eligible because of that example. The point is that a domain-wide assumption is unreliable, so each proposed conversion needs a current policy analysis.

The classification also needs an owner. Marketing can describe the campaign use, engineering can describe the transport, and a qualified reviewer can assess the applicable policy and legal context. None of those roles should infer approval from another team’s completed setup.

What do the Data Manager documents establish?

Google’s Data Manager API documentation says the service can send offline conversions, enhanced conversions for leads, and conversion events to Google Ads. The send-events guide describes a destination, event objects, formatted and hashed data, and a request that returns a request ID on success.

Those pages describe technical capability. They do not replace Customer data policies. Encryption, hashing, a supported destination, or a successful response cannot make prohibited health-related conversion information eligible. A request ID is evidence that Google accepted the request at the transport layer, not that the clinic passed a policy or legal review.

A test upload cannot answer whether policy permits the event. Even if the transport accepts it, the clinic still has no policy approval. Make the decision before constructing a payload, and keep Data Manager delivery disabled for healthcare forms that fall within the sensitive category.

Where does personalized advertising policy fit?

Google’s Personalized advertising policy classifies health as a sensitive interest category. Advertisers promoting sensitive products or services cannot use advertiser-curated audiences, including Customer Match and their own data segments. Predefined Google audiences follow a different rule because Google excludes sensitive user signals from them.

That policy governs targeting. It should not be used as the sole source for a measurement decision. The Customer data policies provide the direct restriction for enhanced-conversion measurement. A clinic must follow both boundaries where they apply and should never turn form submissions into an audience workaround.

This means a blocked conversion cannot be repurposed as remarketing, Customer Match, or another advertiser-curated segment. It remains inside the clinic’s approved systems. The policy names may sound related, but measurement and audience activation are separate uses.

What should remain inside the clinic?

The original form, its operational status, the clinic’s classification record, and any later appointment outcome should remain in the approved clinic environment. Internal systems may need those records to respond, schedule, reconcile, and report. Their operational need does not create permission to send them to Google.

Marketing can still use aggregate internal reporting. A clinic may count valid submissions, bookings, cancellations, and attendance under documented definitions, then compare totals by an approved campaign dimension inside its own reporting boundary. The clinic booking outcome taxonomy keeps those stages distinct.

Aggregate reporting must not become a disguised event export. Keep individual form content, identifiers, appointment details, treatment context, and free text outside advertising platforms. The guide to measuring show rate by campaign without appointment details describes an internal method for later outcomes.

A publication and implementation stop checklist

  • Write the exact conversion action in plain language.
  • Record whether it relates to health or medical information.
  • Use the current English Customer data policies as the controlling Google source.
  • Stop if the conversion falls within the sensitive category.
  • Do not treat hashing, consent, legal basis, or accepted terms as an exception.
  • Do not create a test upload to ask the API for a policy answer.
  • Keep advertiser-curated audiences outside the clinic-form flow.
  • Store the decision date, sources reviewed, scope, and owner.
  • Recheck when the form purpose, page context, service, or Google policy changes.

This stop checklist contains no tag instructions, identifier mappings, payload examples, or activation steps. None would change the controlling answer: technical preparation does not make a health-related clinic conversion eligible.

Frequently asked questions

No. Consent may be relevant to a clinic’s legal and operational duties, but it does not override Google’s prohibition on enhanced-conversion measurement for health or medical conversion information.

Can a clinic hash email or phone details and then upload them?

Hashing is part of Google’s technical process for eligible uses. It does not remove health context or establish eligibility. Do not upload identifiers for a conversion that falls within the sensitive category.

Does a successful Data Manager request prove compliance?

No. A successful response confirms transport processing. It does not confirm that the event complies with Customer data policies, personalized advertising rules, contracts, or applicable law.

Can the clinic rename the event to a generic lead?

No. Google policy concerns what the conversion information relates to. A generic label does not change a health-related consultation request into a non-sensitive event.

References

Related articles