The Conversion Setup Errors That Break Smart Bidding — What to check first

# Why conversion setup matters for Smart Bidding

# 1. PII hashing and normalization errors

• Email addresses must be lowercased and trimmed of whitespace. " John@Example.com " hashes differently than "john@example.com."
• Phone numbers must use E.164 format with country code and no punctuation.

• Inspect the match rate in your conversion action diagnostics. If it's unusually low, normalization is a likely cause.
• Send a known test conversion using a signed-in address you control and confirm it matches.

# 2. Consent mode not configured for the match (or timing issues)

In the EEA, UK, and Switzerland, enhanced conversions flow through Consent Mode. The common failures are not tag absence but incorrect consent mapping and timing:

• ad_user_data and ad_personalization must be mapped to "granted" on acceptance. If they aren't, the Google tag withholds the match key even when a user consented.
• Consent status sometimes updates only on the next page load. If a user accepts and completes a purchase on the same page, the conversion may fire before the granted signal is recorded.

• Confirm whether you're using basic or advanced consent mode and that ad_user_data and ad_personalization map to granted upon acceptance.
• Test the acceptance-to-conversion flow in a single session: accept the banner and complete the conversion without navigating away, and verify the granted signal exists before the conversion request.

A note on tradeoffs: advanced consent mode can recover more data via aggregated modeling for non-consented hits, but it raises privacy considerations and accountability that should be decided with legal/privacy stakeholders.

# 3. Conversion value that doesn't match what transacted

• Static values hardcoded where transactions are variable.
• Mixed currencies being recorded in one column.
• Gross vs net confusion, or whether shipping is included in the value.

• Reconcile transaction values in Google Ads with actual payment records for a sample of conversions.
• Verify currency handling and whether shipping/taxes are included or excluded consistently.
• Replace hardcoded static values with dynamic transaction values where applicable.

# Practical next steps

# Bottom line

Before changing bid strategy or targets, audit the conversion pipeline. If conversions are technically present but corrupted at the input (bad PII hashing, consent mapping/timing, or wrong values), Smart Bidding will optimize toward misleading signals. The checks above are specific, testable, and can reveal silent failures that look invisible in surface reports.