Troubleshooting 1 min read

Enhanced Conversions Low Match Rate: Diagnosis and Fixes

Low Enhanced Conversions match rates reduce your offline tracking effectiveness. Learn how to diagnose and improve match rates for Google Ads with The Upload Offline Conversions App.

Last verified: 2026-11-07

Enhanced Conversions match rates directly impact how many offline conversions are attributed. Low rates mean lost data and weaker Smart Bidding signals.

Diagnosing Low Match Rates

Check the Diagnostics

  1. Go to Goals → Conversions → your action → Diagnostics
  2. Find the Enhanced conversions card
  3. Review:
    • Match rate — What % matched
    • Data quality — Overall quality score
    • Issues — Specific problems detected

Common Issues by Match Rate

What the card showsLikely causeFix
Nothing matchedWrong hash algorithm (MD5) or the value was hashed twiceUse SHA-256 once, after normalizing
A few rows matchedThe email was not lowercased, or the phone was not E.164, before hashingNormalize first. Jane@Example.com will not match jane@example.com
You only sent an emailOne identifierAdd the phone, and the GCLID when you stored it

Improvement Strategies

1. Fix Normalization

Wrong: SHA-256("John@EXAMPLE.com") → No match
Right: SHA-256("john@example.com") → Match ✅

2. Add More Identifiers

Each additional identifier improves match rates:

Google does not publish an expected match rate for any of these. Each extra field is another chance for the row to line up:

  • Email only
  • Phone only
  • Email and phone
  • Email, phone, and name
  • GCLID plus email and phone, when you stored the click ID

3. Fix Phone Format

Must be E.164 before hashing:

Wrong: SHA-256("555-123-4567") → No match
Right: SHA-256("+15551234567") → Match ✅

Use the E.164 Formatter and SHA-256 Hasher to verify.

4. Remove Gmail Dots (Google Only)

Wrong: SHA-256("john.doe@gmail.com")
Right: SHA-256("johndoe@gmail.com")  ← Dots removed for @gmail.com

How TUOCA Maximizes Match Rates

  1. Automatic normalization per platform’s rules
  2. Gmail dot removal for Google uploads
  3. E.164 phone formatting before hashing
  4. Multi-field sending — email + phone + name when available
  5. GCLID + PII dual path — maximum match coverage

Frequently Asked Questions

Google does not publish a good match rate. Read the diagnostics card. If it is near zero, the usual cause is the hash: MD5 instead of SHA-256, hashing twice, or hashing `Jane@Example.com ` before you lowercase and trim it. Send the phone as well as the email, and the GCLID when you stored it.

Common causes: (1) Not normalizing before hashing — email must be lowercase/trimmed, phone must be E.164, (2) Using MD5 instead of SHA-256, (3) Hashing twice, (4) Sending only one identifier (send email AND phone for best results), (5) Not removing Gmail dots for Google uploads.

Stop Guessing. Start Proving ROI.

TUOCA connects your CRM and call tracking data directly to your ad platforms. Set up in minutes.