Google Enhanced Conversions payload builder

Enter a conversion and get Google-ready normalized values, SHA-256 hashes, a pass/warn/fail checklist and a preview payload. Rules come only from Google docs we fetched: Google Ads API: Upload click conversions (enhanced conversions for leads) · Google Ads API: Enhanced conversions for web · Google Ads Help: Set up enhanced conversions for web using the Google tag.

Private by design: this page makes no network calls with your data. Everything stays in your browser (WebCrypto); no analytics run on this tool page. server-track-lab's Google forwarding is not live yet (coming soon); the API forwards to Meta CAPI today.

Customer data

Email Phone Default country calling code (only for phones without one) First name Last name Street address City Region / province / state Postal code Country (2-letter ISO code)

Conversion

order_id / transaction_id Value Currency Conversion time (local) Timezone offset gclid ad_user_data consent

Checklist

Normalized and hashed

Preview: ClickConversion (Google Ads API, enhanced conversions for leads)

Field names as they appear in Google's docs code samples. conversion_action, customer ID and authentication are placeholders: no tokens or keys are used here.

Preview: Google tag `user_data` (pre-hashed keys)

The rules we apply

Field	Rule	Status
All hashed fields	Trim leading/trailing whitespace, lowercase, hex SHA-256	confirmed
Email	gmail.com / googlemail.com: remove all periods and the first + and everything after it, before the @. Other domains: trim + lowercase only	confirmed
Phone	E.164: + then country code and digits, no spaces or dashes (11 to 15 digits incl. +, per the Google tag help)	confirmed
First / last name, street	Hashed after trim + lowercase	confirmed
City, region, postal code, country	Sent unhashed. Country is a 2-letter ISO 3166-1 alpha-2 code	confirmed (exact casing/spacing for these plain fields: unconfirmed; we trim and uppercase the country, as in Google's examples)
Address match	Needs first name, last name, postal code and country	confirmed
Identifiers	One identifier per UserIdentifier; up to five per conversion; email preferred; phone alongside email or name+address	confirmed
conversion_date_time	yyyy-mm-dd HH:mm:ss+\|-HH:mm	confirmed
gclid, order_id, consent	Recommended / strongly recommended / highly recommended	confirmed
currency_code	3-letter code (e.g. CAD)	unconfirmed (docs say "currency code of the conversion_value")

Skip this. server-track-lab hashes and sends for you. One POST /api/v1/track call: we normalize, hash, dedupe on event_id and forward to Meta CAPI. Free for 1,000 events a month, then CA$2 per 1,000. Get a free API key · Try the playground · API docs

FAQ

Does this page send my data anywhere?

No. This page makes no network calls with what you type: normalization and SHA-256 hashing run in your browser with WebCrypto, and this tool page does not load analytics. Nothing is uploaded to server-track-lab or Google.

Does server-track-lab forward conversions to Google yet?

Not yet. Google delivery in server-track-lab is coming soon; today the API forwards to Meta Conversions API only. This tool is a preview of what a Google payload looks like.

Why is my Gmail address hashed differently than for Meta?

Google's docs say that for gmail.com and googlemail.com addresses you remove all periods and any plus suffix from the part before the @, after trimming and lowercasing. Meta only trims and lowercases.

Which fields are hashed and which are plain text?

Per Google's docs: email, phone, first name, last name and street address are SHA-256 hashed. Country, state, city and postal code are sent unhashed.

What date format does Google expect?

yyyy-mm-dd HH:mm:ss+|-HH:mm with a timezone offset, for example 2026-10-14 19:32:45-04:00.